Clinical Research Track at the 14th FHIR Connectathon

Last weekend was the 2nd HL7 FHIR Connectathon (Jan. 14 & 15) that included a Clinical Research Track and the 14th overall FHIR Connectathon. This event was hosted on the Riverwalk in San Antonio and featured over 200 attendees for a weekends worth of hacking. The primary purpose of the Connectathon events is to provide a forum for participants to develop and test software in an informal way.

During the previous, inaugural Clinical Research Track < http://wiki.hl7.org/index.php?title=FHIR_Connectathon_13> only two of us participated.  By the end of the weekend we were able to use FHIR resources to demonstrate the pre-populate Medidata Rave-based demographics and concomitant medications CRFs.

The Clinical Research Track at the 14th Connectathon generated quite a bit more participation interest with 8 attendees. Representatives from vendors, sponsors, and standards organizations participated. Beyond the pre-population of CRFs using EHR data retrieved using FHIR, several additional use cases where proposed for development and testing. When the weekend arrived, we decided to develop a EHR / FHIR readiness site assessment tool. Essentially, this tool would attempt to pre-populate CDASH-based CRF content using FHIR resources and score the site based on data coverage and quality.  Such a service could help identify sites with FHIR-enabled EHR systems and adequate EHR data to support the pre-population of CRFs for clinical research.

This tool leveraged the same basic capabilities as the CRF pre-population application, and we were able to build on some of the work completed during the previous Connectathon. We expanded the FHIR resources used beyond Patient and MedicationStatement to include Observations for vital signs and lab results, and AllergyIntolerance for medical history. Historically, interoperability between HL7 CDA and ODM has been most effective for lab, demographic, medication, and vital signs data. As this tool was a bit ambitious for what amounts to 1 full day of development, we plan to continue to build on our prototype in advance of future Connectathons.

The next Connectathon is in Madrid, and I believe the next one in the US will be in San Diego in the fall. This gives us a bit of time to make some progress before the next US-based Connectathon. I, for one, plan to learn a bit more Python as we work towards this next event.

Comments

  1. GeoffJanuary 28, 2017 at 1:59 AM

    Yes indeed! We should add a TODO.md or similar to list the features we should add (and maybe look at deployment as well). I'll organise a call in the next couple of weeks.

    ReplyDelete
    Replies
    1. Sam Hume, DScJanuary 28, 2017 at 7:58 AM

      Look forward to it. In the mean time, I'll allocate a little play-time to python ;-)

      Delete
  2. UnknownAugust 31, 2017 at 2:37 AM

    This comment has been removed by a blog administrator.

    ReplyDelete
  3. UnknownMarch 9, 2018 at 9:30 PM

    This comment has been removed by a blog administrator.

    ReplyDelete
  4. UnknownMarch 9, 2018 at 9:38 PM

    This comment has been removed by a blog administrator.

    ReplyDelete

Post a Comment

Popular posts from this blog

Value Level Metadata, Vertically Structured Datasets, and Normalizaton

Image
As part of the work to implement Value Level Metadata in SHARE, as well as to author a Define-XML Implementation Guide article, this will be the first of a series of posts on the topic of Value Level Metadata. These posts target a more technical audience, however the Define-XML IG article will include less technical jargon. Future posts will cover additional Value Level Metadata topics and examples. Value Level Metadata (VLM) is metadata that constrains a variable definition based on the value of another variable(s). VLM was originally specified in Define-XML v1.0 as a mechanism for providing the additional metadata needed for software to more accurately interpret these constrained variables.  For example, VSORRES is a variable with structural metadata of  DataType=”Text” and Length=”200”. However, when VSTESTCD=”DIABP” that definition is constrained by VLM to use DataType=”integer” and Length="3". In this case, the value of DIABP in VSTESTCD has triggered the application o
Read more

ODMv2: Renovating the ODM Standard

  ODM, CDISC's Operational Data Model , version 1.x will be 17 years old in October, making it a mature standard. ODM has come of age , and it's time for ODM to take on a bit more responsibility around here. Toward this end, a new XML Technologies development team has recently started work on ODMv2, a substantially updated version of ODM that breaks backwards compatibility with version 1.3.x to add a number of significant new features. This post highlights some areas of new development for ODMv2. As ODMv2 is still in the early stages of development, the scope of the project and specific features are subject to change. Among the more important new ODMv2 features will be a RESTful API that specifies standard methods of data and metadata exchange. The RESTful architecture uses specific URLs and the HTTP protocol to leverage pervasive, scalable web technologies to simplify data interchange. Lack of a common API for data exchange in clinical research has limited the available
Read more

What’s the difference between iSHARE and eSHARE?

Image
CDISC SHARE is a metadata repository (MDR) that supports the development, governance, publishing, and consumption of the CDISC standards in human and machine-readable formats. For more information about SHARE see the   CDISC Website . eSHARE and iSHARE are parts of the overall SHARE system. They represent two separate ways to access SHARE content, as shown in the diagram below. Interactive SHARE, or iSHARE , is the tool used by the CDISC standards development community for developing, governing, and publishing the standards. iSHARE is a cloud-based MDR configured for the CDISC standards that includes a number of standards management and development tools. Prior to accessing the tool, CDISC standards team members receive both on-line and interactive iSHARE training. Each standards development project works with the SHARE Metadata Curators to create and publish new CDISC standards. As new standards, and new versions of existing standards, are created iSHARE provid
Read more