API set up

[Amandine Carmagnac]

Dear all 

I would like to know if it would be possible to use API, and if yes, I would like to understand how easy/difficult it would be to set up in the case below.

We have participants that are recruited through a hospital. We collect some clinical information on a dedicated REDCap hospital database. 

Those same participants are also enrolled in a research program that is conducted at another institution (with the same record name). The research data is collected on a dedicated REDCap database at that institution which is different from the hospital database. 

Down the track we would like to correlate both the clinical and the research data from those same participants.

Currently we have to manually enter the participant ID in one of the databases. Although this is doable I'm not too comfortable with this system, as a typo could easily be made and this could have a big impact on the data analysis/interpretation. 

I have never used API, but I think this seems to be an appropriate way of minimising data entry error. Do you think this is what we should try to put in place? If so, would someone be able to give me some directions on how to set that up. 

Thank you so much for your help.

Amandine

                                                                                                                                                                                                                                                                                                                             

[Amit Tandon]

Hi,

When you refer separate REDCap databases, then are you referring to separate REDCap instances or different project on same REDCap Instance. In the latter case, there is External Module called Cross Piping project. See if that is helpful

[Peter Macisaac (POP)]

Hi 

You can create a new project  (reflecting your needs). Export format of new project  and then consolidate the data outside of redcap (dont use EXCEL - Open Office works well) then upload the new data - and archive the two original projects  This just needs good data management skills.

I dont see the API (although I have to admit to not using it) as the solution

Peter

--
You received this message because you are subscribed to the Google Groups "Redcap Open" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redcap_open...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/redcap_open/CAByum3BhpppNrB6177wkKttghD50uJQy21pEt5rOK7rcQNFicA%40mail.gmail.com.

[Amandine Carmagnac]

Thank you to both of you. 

The external module would definitively be useful if the 2 databases were located at the same site. 

By different, I mean that one database is located at site1, for collection of the clinical information (hospital) and the other database is located at site 2, for research data collection (research institute).

Both databases are accessed with a different login as they are not owned by the same institution. 

I cannot have the 2 databases on the same REDCap as 2 different projects because 1 set of data is owned by site 1 and the other one by site 2.

All I would like to achieve is to be able to have the record ID (in this case patient study ID) automatically transferred to site 2 REDCap to enable research data collection. 

Currently we are entering the record ID twice, once in site 1 database and once again in site 2 database, which I'm not too keen on as this could easily incur typo, which would become a big issue at the end of the study once we want to match the clinical data with the research data. 

I have never used API, but from my understanding it seems that could be the solution. I'm curious to know if this would be the best solution and would like to know if it would be easy to set up, or not.

Thank you so much for your help. 

Amandine

[Florence Breslin]

I think API would be the way to go here, but I am following this as well, I have the same situation here and would like to see if a solution can be recommended.