Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Project Scope

Increasing interest in eSource keeps the issue of data integration between Research Systems (EDC, CTMS, CDMS, etc) and healthcare systems (EHR, etc) as a consistent want for Sponsors of Clinical Investigators and Regulators. Previous efforts to make this a repeatable, scalable solution have not met with

widescale

wide-scale adoption, for a variety of reasons.

Some common historical points of view have included:

  • That the quality of the data that can be retrieved from the Healthcare sites is insufficient to meet research needs.
  • That uptake of electronic systems at investigative sites has been slow, expensive, and not delivering real value to healthcare practises.
  • Types of data captured in healthcare have been more operational rather than clinical.
  • Enabling the Necessary interfaces is an expensive and process-heavy undertaking.
  • There is not a suitable, generally supported electronic exchange format, with a number of standard representations being supported in recent memory.

Many of these issues are on the path to being resolved;

both the HITECH ACT and Meaningful Use Programs have accelerated adoption of EHR systems across the US and is now continuing to incentivise sites to store more clinically relevant data in their EHR Systems. As an example the ONC Common Clinical Dataset is mandating the availability of many of the core domains of interest to the clinical trials industry. However, the solution to the lack of availability of a common exchange format has not been completely resolved; the HL7 Continuity of Care Document (CCD) is a mature standard, but is not used consistently across implementations or geographies.

government programs have pushed the adoption and accessibility of electronic health records.  In addition, there are a number of stakeholders in the Research Industry that are making the use of healthcare resources a priority for the future; examples include Transcelerate eSource initiative and HL7 Vulcan Accelerator.

Solution

Work with stakeholders to adopt the HL7 Fast Healthcare Interoperability Resources (FHIR)

Potential Solution

Review the HL7 FHIR

standard as a basis for future data integrations between Research Systems and Healthcare systems

. It will include looking at the existing FHIR based Research standards (including DAF and SDC)

.



Project LeadsEmail

Geoff Low

glow@mdsol.com

Wendy Dobson (PHUSE Project Manager)

wendy@phuse.global


Status
colourBlue
titleCurrent Status
 Q42020

Had

Following the breakout

sessions

session at CSS

and now looking at how to evolve the team. Will establish scope early Q12021 and then look to call

, the project has now updated it's scope and is looking to address their deliverables.

This project is calling for a Co-

lead

Lead and project members


Deliverables

Timelines

Review FHIR Specification for applicability as a Research Standard

Q12021

Identify 3-6 use cases which illustrate how FHIR Resources can enable effective data sharing between Healthcare and Research Systems

Q12021

Prepare White Paper

Q22021

Use of HL7 FHIR as eSource to Pre-populate CDASH Case Report Forms Using a CDISC ODM API

Published 2018


Stakeholders/Initiatives

Recommended Solutions

  • The FHIR

Other Initiatives

CDISC EHR to CDASH (E2C) Group

  • The PHUSE group is the why - it's taking a look at the standard (and the initiatives) around FHIR and applying them to a few scenarios within the research domain. The expected output will be a white paper with the conclusions of the group about how FHIR will (or will not, perhaps) change clinical research in the future. There will be subsequent projects that will dig into any of the use cases identified to show Pharma and other stakeholders the utility - these will utilise the rules and mappings put together in the E2C project

  • Follow on from the PHUSE Semantic Technologies key CRF Project

Recommended Solutions

HL7 have now published a standard; Fast Healthcare Interoperability Resources (FHIR). This is an entirely different paradigm, built around Resources and using REST as a architectural style. This
  • resource-based view of healthcare data is much more aligned to the research 'view' of data;
we consider studies
  • research considers study using CRFs,
typically
  • artificially aligned with clinical data element domains
- which some might describe as clinical data resources. The publication of the Federal Notice in 2015 and the updated Draft Guidance in 2016 have shown the FDA's commitment to increased adoption of eSource in Clinical Research. In particular, the Draft Guidance showed a renewed focus on bi-directional integration of data between Research and Healthcare systems; something that would not easily be achieved given current technology and processes. FHIR offers the possibility of making this a reality
  • . In the future these two views of the same data will be more closely aligned from capture through to submission. There is a need for external activities to assist in this alignment (such as mapping to or extending of submission formats, alternative data management processes, focus on the lifecycle of a datapoint, etc).  These tasks should be solved in a pre-competitive manner and shared with all stakeholders.
  • Increasing government engagement in personal healthcare data has focussed on the need for seamless exchange (including access, consent, format, understandability, etc). Most guidance has recognised that the technology is a key foundation and have chosen FHIR as their preferred format.  This is an initiative that the research industry can leverage to more closely engage with the participants in clinical research.

Specific Actions

  • Identify gaps and opportunities between the Healthcare and Research realms with a view to providing a shared vocabulary and platform to enable better collaboration
  • Prepare
a
  • white
paper
  • papers for Biopharmaceutical Companies providing sample use cases for where the adoption of FHIR will improve the experience of Sponsors, Technology Firms and most importantly sites and site users
  • Work with stakeholders to socialise and formalise (e.g. through HL7 FHIR Profiles/Implementation Guides) the technology/approach.



Project Members

Company

Aditya GadikoMMS 
Amy PalmerCDISC
Andrea FalcoOXONepi
Andy IversonMedtronic
Bess LeRoyCDISC
Bill Friggle4EStandards
Christine K DenneyEli Lilly
Dan KruggerIBM
Dave Iberson-HurstS-cubed
Greg JonesOracle
Ingeborg HoltIBM
Jeff AbolafiaPinnacle 21
Jozef AertsXML4Pharma
Manuel AnidoAllergan
Marc RoosenJanssen Research & Development
Mark McGilchristUniversity of Dundee
Mike HamidiCSG Inc
Nurcan CoskunIndustry
Paul KnowlesDativa
Ramachandran PrasadIndustry
Rebecca BakerCDISC
Sam HumeCDISC
Sebastiaan KnijnenburgIndustry
Shannon LaboutCDISC
Siddharth Arthi Zifornd
Terek PetersonYPrime
Rahul ThandavanRoche