The Launch of the iCoDE Standard Project

Abstract

Introduction: The first meeting of the Integration of Continuous Glucose Monitor Data into the Electronic Health Record (iCoDE) project, organized by Diabetes Technology Society, took place virtually on January 27, 2022. Methods: Clinicians, government officials, data aggregators, attorneys, and standards experts spoke in panels and breakout groups. Three themes were covered: 1) why digital health data integration into the electronic health record (EHR) is needed, 2) what integrated continuously monitored glucose data will look like, and 3) how this process can be achieved in a way that will satisfy clinicians, healthcare organizations, and regulatory experts. Results: The meeting themes were addressed within eight sessions: 1) What Do Inpatient Clinicians Want to See With Integration of CGM Data into the EHR?, 2) What Do Outpatient Clinicians Want to See With Integration of CGM Data into the EHR?, 3) Why Are Data Standards and Guidances Useful?, 4) What Value Can Data Integration Services Add?, 5) What Are Examples of Successful Integration?, 6) Which Privacy, Security, and Regulatory Issues Must Be Addressed to Integrate CGM Data into the EHR?, 7) Breakout Group Discussions, and 8) Presentation of Breakout Group Ideas. Conclusions: Creation of data standards and workflow guidance are necessary components of the Integration of Continuous Glucose Monitor Data into the Electronic Health Record (iCoDE) standard project. This meeting, which launched iCoDE, will be followed by a set of working group meetings intended to create the needed standard.

Continuous Glucose Monitoring in the Intensive Care Unit

“…18 Recent efforts are focusing on the creation of data standards and workflow guidance for integration of CGM data in the electronic health record (EHR). 52…”

Hospital Diabetes Meeting 2022

“…Opportunities to adopt, adapt, or develop standards and best practices in the CGM data pipeline. Reproduced from Xu et al 9 Abbreviations: CCD, Continuity of Care Documents; CDA, Clinical Document Architecture; CGM, continuous glucose monitor; CPT, Current Procedural Terminology; EHR, electronic health record; EMPI, Enterprise Master Patient Index; FHIR, Fast Healthcare Interoperability Resources; HIPAA, Health Insurance Portability and Accountability Act; HITRUST, Health Information Trust Alliance; HL7, Health Level 7; ICD-10, International Classification of Diseases 10th Revision; IEEE, Institute of Electrical and Electronics Engineers; LOINC, Logical Observation Identifiers Names and Codes; mHealth, mobile health; NIST CSF, National Institute of Standards and Technology Cybersecurity Framework; NPI, National Provider Identifier; OAuth, open authorization; OMOP, Observational Medical Outcomes Partnership; RxNORM, a normalized naming system for generic and branded drugs, and a tool for supporting semantic interoperation between drug terminologies and pharmacy knowledge base systems; SMART, Substitutable Medical Applications, Reusable Technologies; SNOMED, Systemized Nomenclature of Medicine; SOC2, System and Organization Controls type 2—Trust Services Criteria; UDI, Unique Device Identifier.…”

E-health as a sine qua non for modern healthcare

“…Examples in real life and research setting exist though complete integration into the healthcare systems remain challenging and the apps often focus on one medical specialty. [21][22][23][24][25] Today the communication between healthcare specialists and back to the patient still works via conventional information channels, mostly email or phone. Involved healthcare professionals including doctors, physiotherapists or psychologists literally are not on the same page.…”

“…Similar to online banking, interoperable apps will likely become the point of connected care. Examples in real life and research setting exist though complete integration into the healthcare systems remain challenging and the apps often focus on one medical specialty 21–25…”