This wiki has undergone a migration to Confluence found Here

201801 Clinical Research

From HL7Wiki
Jump to navigation Jump to search

Track Name

Clinical Research

Submitting WG/Project/Implementer Group

Biopharma FHIR project group


This track will continue to further explore the benefits of FHIR for clinical research of new biopharmaceutical experimental treatments, and to increase visibility of FHIR within the biopharmaceutical community. This track advances the use of FHIR resources as eSource data used to pre-populate clinical research case report forms for both regulated and non-regulated clinical research. This builds on previous explorations in Connectathon 13-16. Plans for this connection include participation from at least 5 Pharmaceutical companies, Members of TransCelerate Biopharma, Inc. and technology implementers will simulate using FHIR to populate and manage clinical study databases. A set of 2-3 detailed use case scenarios will be proposed. This work will inform development of profiles and IGs to support clinical research using FHIR.

Clinical Research studies currently require the redundant entry of clinical data that already typically reside in Meaningful Use conformant EHR systems. EHR data represents original records in electronic format that can be used as eSource and directly imported into clinical research EDC databases so as to improve the quality and consistency of data between EHR and EDC systems and eliminate the need for redundant data entry. Establishing interoperability between EHR and EDC systems to streamline and modernize clinical investigations should improve data accuracy, patient safety, and clinical research efficiency. Given the extreme cost and extended time required for randomized clinical trials, it would be substantially better to utilize EHR source data to directly populate clinical trial databases wherever feasible. As stated in its May 2016 FDA draft guidance titled “Use of Electronic Health Record Data in Clinical Investigations” FDA “encourages sponsors and clinical investigators to work with the entities that control the EHRs, such as health care organizations, to use EHRs and EDC systems that are interoperable. . . Establishing interoperability between EHR and EDC systems to streamline and modernize clinical investigations should improve data accuracy, patient safety, and clinical research efficiency.”

Proposed Track Lead

See Connectathon_Track_Lead_Responsibilities Responsibilities Geoff Low (; Trisha Simpson (

Expected participants

TransCelerate Biopharma, Inc., UCB, Pfizer, GSK, Merck, Lilly, Medidata, Oracle Health Sciences, Clinical Ink, others


Please include information here regarding how much advance preparation will be required if creating a client and/or server.

Role 1 Name

FHIR Client: Support the sending from an EHR or patient device of clinical research study data: create, read, search and update to a clinical study database system.

Role 2 Name

Clinical Trial Designer: Identifies data relevant to research studies that may be collected from EHRs or SMART-on-FHIR devices. Sets up patient matching criteria and identifiers for ResearchStudy and ResearchSubject for a synthetic test study. Creates study database, mappings/interfaces, EDC case report forms with variable mappings to FHIR that will receive EHR patient data for clinical trial subjects. Generate updates from EDC to apply to the EHR. Data Collector[edit] Queries API to identify patients by Study and Subject identifiers to pull EHR data for demographics, medications and lab data that maps directly to variables on eCRF. Provides data generated by patients to add to study databases or EHRs.

Role 3 Name

Subject Matter Expert SME: Creates and tests queries to identify patients who match eligibility criteria for a study or review data.


Scenario Step 1 Name

Success Criteria:
Bonus point:


Security and Privacy Considerations