Difference between revisions of "201609ClinicalResearchTrack"
Wayne Kubick (talk | contribs) |
Wayne Kubick (talk | contribs) |
||
| Line 20: | Line 20: | ||
==Expected participants== | ==Expected participants== | ||
<!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track --> | <!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track --> | ||
| − | Transcelerate BioPharma, Inc. | + | EHR vendors supporting FHIR API; Transcelerate BioPharma, Inc. |
EDC Vendors TBD | EDC Vendors TBD | ||
Revision as of 02:48, 15 June 2016
Track Name
Clinical Research Track
Submitting WG/Project/Implementer Group
Clinical Interoperability Council
Justification
Clinical Research Studies currently require direct redundant entry of clinical data that should reside in EHR systems that conform to meaningful use. As data is managed in a pharmaceutical sponsor environment, the CRF data is updated, and may vary from the original source that presented by the EHR. This leads to difficulties for regulatory inspectors and reviewers in tracing back clinical data to source data, as well as redundant duplication of effort by site personnel, and general quality issues. Given the extreme cost and extended time required for randomized clinical trials, it would be substantially better to utilize EHR source data in clinical databases more efficiently.
Proposed Track Lead
See Connectathon_Track_Lead_Responsibilities
Mitra Rocca, acting; other TBD
Expected participants
EHR vendors supporting FHIR API; Transcelerate BioPharma, Inc. EDC Vendors TBD
Roles
Please include information here regarding how much advance preparation will be required if creating a client and/or server.
Role 1 Name
Scenarios
Scenario Step 1 Name
- Action:
- Precondition:
- Success Criteria:
- Bonus point:
