Enabling Better Interoperability for HealthCare

Lessons in Developing a Standards Based Application Programing Interface for Electronic Medical Record Systems

Suranga N. Kasthurirathne, Burke Mamlin, Harsha Kumara, Grahame Grieve, Paul Biondich

Research output: Contribution to journalArticle

16 Citations (Scopus)

Abstract

We sought to enable better interoperability and easy adoption of healthcare applications by developing a standardized domain independent Application Programming Interface (API) for an Electronic Medical Record (EMR) system. We leveraged the modular architecture of the Open Medical Record System (OpenMRS) to build a Fast Healthcare Interoperability Resources (FHIR) based add-on module that could consume FHIR resources and requests made on OpenMRS. The OpenMRS FHIR module supports a subset of FHIR resources that could be used to interact with clinical data persisted in OpenMRS. We demonstrate the ease of connecting healthcare applications using the FHIR API by integrating a third party Substitutable Medical Apps & Reusable Technology (SMART) application with OpenMRS via FHIR. The OpenMRS FHIR module is an optional component of the OpenMRS platform. The FHIR API significantly reduces the effort required to implement OpenMRS by preventing developers from having to learn or work with a domain specific OpenMRS API. We propose an integration pathway where the domain specific legacy OpenMRS API is gradually retired in favor of the new FHIR API, which would be integrated into the core OpenMRS platform. Our efforts indicate that a domain independent API is a reality for any EMR system. These efforts demonstrate the adoption of an emerging FHIR standard that is seen as a replacement for both Health Level 7 (HL7) Version 2 and Version 3. We propose a gradual integration approach where our FHIR API becomes the preferred method for communicating with the OpenMRS platform.

Original languageEnglish (US)
Article number182
JournalJournal of Medical Systems
Volume39
Issue number11
DOIs
StatePublished - Nov 1 2015

Fingerprint

Electronic medical equipment
Electronic Health Records
Interoperability
Medical Records
Delivery of Health Care
Application programming interfaces (API)
Health Level Seven
Application programs

Keywords

  • Emerging economies
  • Fhir
  • HL7
  • Interoperability
  • Smart
  • Standards

ASJC Scopus subject areas

  • Medicine (miscellaneous)
  • Health Informatics
  • Health Information Management
  • Information Systems

Cite this

Enabling Better Interoperability for HealthCare : Lessons in Developing a Standards Based Application Programing Interface for Electronic Medical Record Systems. / Kasthurirathne, Suranga N.; Mamlin, Burke; Kumara, Harsha; Grieve, Grahame; Biondich, Paul.

In: Journal of Medical Systems, Vol. 39, No. 11, 182, 01.11.2015.

Research output: Contribution to journalArticle

@article{89db243f54fc424a9dbd8f8ff45813e7,
title = "Enabling Better Interoperability for HealthCare: Lessons in Developing a Standards Based Application Programing Interface for Electronic Medical Record Systems",
abstract = "We sought to enable better interoperability and easy adoption of healthcare applications by developing a standardized domain independent Application Programming Interface (API) for an Electronic Medical Record (EMR) system. We leveraged the modular architecture of the Open Medical Record System (OpenMRS) to build a Fast Healthcare Interoperability Resources (FHIR) based add-on module that could consume FHIR resources and requests made on OpenMRS. The OpenMRS FHIR module supports a subset of FHIR resources that could be used to interact with clinical data persisted in OpenMRS. We demonstrate the ease of connecting healthcare applications using the FHIR API by integrating a third party Substitutable Medical Apps & Reusable Technology (SMART) application with OpenMRS via FHIR. The OpenMRS FHIR module is an optional component of the OpenMRS platform. The FHIR API significantly reduces the effort required to implement OpenMRS by preventing developers from having to learn or work with a domain specific OpenMRS API. We propose an integration pathway where the domain specific legacy OpenMRS API is gradually retired in favor of the new FHIR API, which would be integrated into the core OpenMRS platform. Our efforts indicate that a domain independent API is a reality for any EMR system. These efforts demonstrate the adoption of an emerging FHIR standard that is seen as a replacement for both Health Level 7 (HL7) Version 2 and Version 3. We propose a gradual integration approach where our FHIR API becomes the preferred method for communicating with the OpenMRS platform.",
keywords = "Emerging economies, Fhir, HL7, Interoperability, Smart, Standards",
author = "Kasthurirathne, {Suranga N.} and Burke Mamlin and Harsha Kumara and Grahame Grieve and Paul Biondich",
year = "2015",
month = "11",
day = "1",
doi = "10.1007/s10916-015-0356-6",
language = "English (US)",
volume = "39",
journal = "Journal of Medical Systems",
issn = "0148-5598",
publisher = "Springer New York",
number = "11",

}

TY - JOUR

T1 - Enabling Better Interoperability for HealthCare

T2 - Lessons in Developing a Standards Based Application Programing Interface for Electronic Medical Record Systems

AU - Kasthurirathne, Suranga N.

AU - Mamlin, Burke

AU - Kumara, Harsha

AU - Grieve, Grahame

AU - Biondich, Paul

PY - 2015/11/1

Y1 - 2015/11/1

N2 - We sought to enable better interoperability and easy adoption of healthcare applications by developing a standardized domain independent Application Programming Interface (API) for an Electronic Medical Record (EMR) system. We leveraged the modular architecture of the Open Medical Record System (OpenMRS) to build a Fast Healthcare Interoperability Resources (FHIR) based add-on module that could consume FHIR resources and requests made on OpenMRS. The OpenMRS FHIR module supports a subset of FHIR resources that could be used to interact with clinical data persisted in OpenMRS. We demonstrate the ease of connecting healthcare applications using the FHIR API by integrating a third party Substitutable Medical Apps & Reusable Technology (SMART) application with OpenMRS via FHIR. The OpenMRS FHIR module is an optional component of the OpenMRS platform. The FHIR API significantly reduces the effort required to implement OpenMRS by preventing developers from having to learn or work with a domain specific OpenMRS API. We propose an integration pathway where the domain specific legacy OpenMRS API is gradually retired in favor of the new FHIR API, which would be integrated into the core OpenMRS platform. Our efforts indicate that a domain independent API is a reality for any EMR system. These efforts demonstrate the adoption of an emerging FHIR standard that is seen as a replacement for both Health Level 7 (HL7) Version 2 and Version 3. We propose a gradual integration approach where our FHIR API becomes the preferred method for communicating with the OpenMRS platform.

AB - We sought to enable better interoperability and easy adoption of healthcare applications by developing a standardized domain independent Application Programming Interface (API) for an Electronic Medical Record (EMR) system. We leveraged the modular architecture of the Open Medical Record System (OpenMRS) to build a Fast Healthcare Interoperability Resources (FHIR) based add-on module that could consume FHIR resources and requests made on OpenMRS. The OpenMRS FHIR module supports a subset of FHIR resources that could be used to interact with clinical data persisted in OpenMRS. We demonstrate the ease of connecting healthcare applications using the FHIR API by integrating a third party Substitutable Medical Apps & Reusable Technology (SMART) application with OpenMRS via FHIR. The OpenMRS FHIR module is an optional component of the OpenMRS platform. The FHIR API significantly reduces the effort required to implement OpenMRS by preventing developers from having to learn or work with a domain specific OpenMRS API. We propose an integration pathway where the domain specific legacy OpenMRS API is gradually retired in favor of the new FHIR API, which would be integrated into the core OpenMRS platform. Our efforts indicate that a domain independent API is a reality for any EMR system. These efforts demonstrate the adoption of an emerging FHIR standard that is seen as a replacement for both Health Level 7 (HL7) Version 2 and Version 3. We propose a gradual integration approach where our FHIR API becomes the preferred method for communicating with the OpenMRS platform.

KW - Emerging economies

KW - Fhir

KW - HL7

KW - Interoperability

KW - Smart

KW - Standards

UR - http://www.scopus.com/inward/record.url?scp=84943399693&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=84943399693&partnerID=8YFLogxK

U2 - 10.1007/s10916-015-0356-6

DO - 10.1007/s10916-015-0356-6

M3 - Article

VL - 39

JO - Journal of Medical Systems

JF - Journal of Medical Systems

SN - 0148-5598

IS - 11

M1 - 182

ER -