Limits...
SMART-on-FHIR implemented over i2b2

View Article: PubMed Central - PubMed

ABSTRACT

We have developed an interface to serve patient data from Informatics for Integrating Biology and the Bedside (i2b2) repositories in the Fast Healthcare Interoperability Resources (FHIR) format, referred to as a SMART-on-FHIR cell. The cell serves FHIR resources on a per-patient basis, and supports the “substitutable” modular third-party applications (SMART) OAuth2 specification for authorization of client applications. It is implemented as an i2b2 server plug-in, consisting of 6 modules: authentication, REST, i2b2-to-FHIR converter, resource enrichment, query engine, and cache. The source code is freely available as open source. We tested the cell by accessing resources from a test i2b2 installation, demonstrating that a SMART app can be launched from the cell that accesses patient data stored in i2b2. We successfully retrieved demographics, medications, labs, and diagnoses for test patients. The SMART-on-FHIR cell will enable i2b2 sites to provide simplified but secure data access in FHIR format, and will spur innovation and interoperability. Further, it transforms i2b2 into an apps platform.

No MeSH data available.


XQuery-based mapping of i2b2 XML to FHIR resource, elucidating an example translation of i2b2 medication facts into medication prescription and medication resources in FHIR. Steps 1–4 show mapping of the i2b2 model to the FHIR model, and 5 denotes linking of medication to prescription; 6 is enrichment by adding RXNORM translation of the NDC code.
© Copyright Policy - cc-by-nc
Related In: Results  -  Collection

License
getmorefigures.php?uid=PMC5391721&req=5

ocw079-F2: XQuery-based mapping of i2b2 XML to FHIR resource, elucidating an example translation of i2b2 medication facts into medication prescription and medication resources in FHIR. Steps 1–4 show mapping of the i2b2 model to the FHIR model, and 5 denotes linking of medication to prescription; 6 is enrichment by adding RXNORM translation of the NDC code.

Mentions: Finally, if the client request is a FHIR query, the Representational state transfer-Application Programming interface (REST-API) module invokes the query engine to execute the query for selection of a subset of FHIR resources, and sends them back to the client. The i2b2-to-FHIR converter translates the i2b2 observation facts to FHIR resources in EXtensible Markup Language (XML) format, using XQuery (Figure 2). The query engine implements the FHIR search specification. Its output is a set of FHIR resources in the form of a FHIR bundle. The cache persists FHIR resources between RESTful calls, thereby reducing redundant data retrieval requests to the i2b2 instance.Figure 2.


SMART-on-FHIR implemented over i2b2
XQuery-based mapping of i2b2 XML to FHIR resource, elucidating an example translation of i2b2 medication facts into medication prescription and medication resources in FHIR. Steps 1–4 show mapping of the i2b2 model to the FHIR model, and 5 denotes linking of medication to prescription; 6 is enrichment by adding RXNORM translation of the NDC code.
© Copyright Policy - cc-by-nc
Related In: Results  -  Collection

License
Show All Figures
getmorefigures.php?uid=PMC5391721&req=5

ocw079-F2: XQuery-based mapping of i2b2 XML to FHIR resource, elucidating an example translation of i2b2 medication facts into medication prescription and medication resources in FHIR. Steps 1–4 show mapping of the i2b2 model to the FHIR model, and 5 denotes linking of medication to prescription; 6 is enrichment by adding RXNORM translation of the NDC code.
Mentions: Finally, if the client request is a FHIR query, the Representational state transfer-Application Programming interface (REST-API) module invokes the query engine to execute the query for selection of a subset of FHIR resources, and sends them back to the client. The i2b2-to-FHIR converter translates the i2b2 observation facts to FHIR resources in EXtensible Markup Language (XML) format, using XQuery (Figure 2). The query engine implements the FHIR search specification. Its output is a set of FHIR resources in the form of a FHIR bundle. The cache persists FHIR resources between RESTful calls, thereby reducing redundant data retrieval requests to the i2b2 instance.Figure 2.

View Article: PubMed Central - PubMed

ABSTRACT

We have developed an interface to serve patient data from Informatics for Integrating Biology and the Bedside (i2b2) repositories in the Fast Healthcare Interoperability Resources (FHIR) format, referred to as a SMART-on-FHIR cell. The cell serves FHIR resources on a per-patient basis, and supports the “substitutable” modular third-party applications (SMART) OAuth2 specification for authorization of client applications. It is implemented as an i2b2 server plug-in, consisting of 6 modules: authentication, REST, i2b2-to-FHIR converter, resource enrichment, query engine, and cache. The source code is freely available as open source. We tested the cell by accessing resources from a test i2b2 installation, demonstrating that a SMART app can be launched from the cell that accesses patient data stored in i2b2. We successfully retrieved demographics, medications, labs, and diagnoses for test patients. The SMART-on-FHIR cell will enable i2b2 sites to provide simplified but secure data access in FHIR format, and will spur innovation and interoperability. Further, it transforms i2b2 into an apps platform.

No MeSH data available.