This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "201705 Clinical Research"

From HL7Wiki
Jump to navigation Jump to search
Line 12: Line 12:
 
==Justification==
 
==Justification==
 
<!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. -->
 
<!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. -->
 +
This track is intended to 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.  advance 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 and 14.
 +
 +
Clinical Research studies currently require the redundant entry of clinical data that already typically resides 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. The May 2016 FDA draft guidance titled “Use of Electronic Health Record Data in Clinical Investigations” encourages the sponsors of clinical research to use EHR data as noted in the statement below.
 +
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. EHRs may be interoperable with EDC systems in a variety of ways depending on supportive technologies and standards. Interoperable technology may involve automated electronic transmission of relevant EHR data to the EDC system. For example, data elements originating in an EHR (e.g., demographics, vital signs, past medical history, past surgical history, social history, medications, adverse reactions) may automatically populate the eCRFs within an EDC system.
 +
 +
TransCelerate Biopharma, a consortium of 18 of the largest global pharmaceuticals, has engaged an eSource project team that will be sending representatives to the Madrid Connectathon seeking to further assess the readiness of FHIR toward the goal of creating a FHIR IG for Clinical Resource.
  
 
==Proposed Track Lead==
 
==Proposed Track Lead==

Revision as of 18:29, 29 March 2017


Track Name

Clinical Research Track

Submitting WG/Project/Implementer Group

Biopharma FHIR project group TransCelerate Biopharma eSource Work Stream

Justification

This track is intended to 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. advance 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 and 14.

Clinical Research studies currently require the redundant entry of clinical data that already typically resides 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. The May 2016 FDA draft guidance titled “Use of Electronic Health Record Data in Clinical Investigations” encourages the sponsors of clinical research to use EHR data as noted in the statement below. 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. EHRs may be interoperable with EDC systems in a variety of ways depending on supportive technologies and standards. Interoperable technology may involve automated electronic transmission of relevant EHR data to the EDC system. For example, data elements originating in an EHR (e.g., demographics, vital signs, past medical history, past surgical history, social history, medications, adverse reactions) may automatically populate the eCRFs within an EDC system.

TransCelerate Biopharma, a consortium of 18 of the largest global pharmaceuticals, has engaged an eSource project team that will be sending representatives to the Madrid Connectathon seeking to further assess the readiness of FHIR toward the goal of creating a FHIR IG for Clinical Resource.

Proposed Track Lead

See Connectathon_Track_Lead_Responsibilities Wayne Kubick (wkubick@hl7.org), Sam Hume (swhume@gmail.com); Geoff Low (glow@mdsol.com)

Expected participants

Medidata Solutions, TransCelerate member companies (contact: kenneth.milstead@kinapse.com), Oracle, Other EDC and EHR 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:


TestScript(s)