Index of HL7 International Realm Implementation Guides
| IG | Details | Published | Candidate |
| ae-research-backport-ig | Adverse Event Clinical Research R4 Backport The intent of this guide is to provide a profile on the FHIR AdverseEvent Resource suitable for Clinical Research, this is a convenience backport into FHIR R4. | 1.0.1 Jan-2024 v4.0.1 | |
| ae-research-ig | Adverse Event Clinical Research The intent of this guide is to provide a profile on the FHIR AdverseEvent Resource suitable for Clinical Research. | 1.0.1 Jan-2024 v5.0.0 | |
| application-feature | FHIR Application Feature Framework Implementation Guide CapabilityStatement is the largest/most complex of the infrastructure resources, yet there continues to be pressure to add yet more capabilities to describe additional nuances of how systems behave (or are desired to behave). As well, the things people want to say about systems often covers concepts that are outside FHIR proper (e.g. CDS Hooks, SMART) or even outside HL7. This IG defines a terminology-based approach to managing new assertions around system capabilities to support these needs and will also enable dynamic feature negotiation between various actors. | null vnull | 1.0.0-ballot Jan-2024 v4.0.1 |
| bulkdata | FHIR Bulk Data Access (Flat FHIR) null | 2.0.0 Jan-2021 v4.0.1 | |
| cardx-htn-mng | CardX Hypertension Management IG This implementation guide is intended to increase the quality of blood pressure data observed by the patient taken in a non-clinical setting or at home. | null vnull | 1.0.0-ballot Jan-2024 v4.0.1 |
| cdisc-lab | CDISC Lab Semantics in FHIR The CDISC Lab Semantics in FHIR Implementation Guide provides guidance on how to use FHIR resources to capture data. | 1.0.0 Jan-2020 v4.0.1 | |
| cdisc-mapping | CDISC Mapping FHIR IG This implementation guide defines authoritative mappings between the CDISC LAB, SDTM and CDASH standards and the corresponding HL7 FHIR resources to ease interoperability and data conversion between systems implementing these standards. | 1.0.0 Jan-2021 v4.0.1 | |
| cpg | Clinical Guidelines This implementation guide supports the development of standards-based computable representations of the content of clinical care guidelines. Its content pertains to technical aspects of digital guidelines implementation and is intended to be usable across multiple use cases across clinical domains as well as in the International Realm. | 1.0.0 Jan-2021 v4.0.1 | 2.0.0-ballot Jan-2023 v4.0.1 |
| cql | Using CQL with FHIR Implementation Guide The Using CQL with FHIR implementation guide defines profiles, operations and guidance for the use of CQL with FHIR, both as a mechanism for querying, as well as inline and integrated usage as part of knowledge artifacts. | 1.0.0 Jan-2024 v4.0.1 | |
| crmi | Canonical Resource Management Infrastructure Implementation Guide The Canonical Resource Management Infrastructure implementation guide defines profiles, operations, capability statements and guidance to facilitate the content management lifecycle for authoring, publishing, distribution, and implementation of FHIR knowledge artifacts such as value sets, profiles, libraries, rules, and measures. The guide is intended to be used by specification and content implementation guide authors as both a dependency for validation of published artifacts, and a guide for construction and publication of content. | 1.0.0 Jan-2024 v4.0.1 | |
| dicom-sr | DICOM® SR to FHIR Resource Mapping IG DICOM® SR is widely adopted by Imaging-based devices and IT systems. Non-imaging based Healthcare IT Systems, generally, do not support DICOM® SR. Non-imaging healthcare systems support HL7 standards, such as FHIR. Bridging the two standards for clinical imaging observations becomes necessary for interoperability between these type of systems. The outcome of this project will be one or more implementation guides with defined sets of mappings between SR content and FHIR resources. The mapping will not be bi-directional -- a complete DICOM® SR is not expected to be able to be re-constructed from a set of FHIR resources. The first phase will focus on mapping Imaging observations to FHIR Observations and related resources (Patient, Device, etc.) and the DICOM® SR template TID-1500 (Measurement Report). | null vnull | 1.0.0-ballot Jan-2024 v5.0.0 |
| ebm | Evidence Based Medicine on FHIR Implementation Guide This implementation guide covers the broad scope of representation of scientific knowledge, including (1) citations to represent identification, location, classification, and attribution for knowledge artifacts; (2) components of research study design including study eligibility criteria (cohort definitions) and endpoint analysis plans; (3) research results including the statistic findings, definition of variables for which those findings apply, and the certainty of these findings; (4) assessments of research results; (5) aggregation and synthesis of research results; (6) judgments regarding evidence syntheses and contextual factors related to recommendations; (7) recommendations; and (8) compositions of combinations of these types of knowledge. The types of interoperability covered include syntactic (Resource StructureDefinitions) and semantic (value sets). | null vnull | 1.0.0-ballot Jan-2023 v5.0.0 |
| ehrs-rle | EHRS Functional Model - Record Lifecycle Events Implementation Guide null | 1.1.0 Jan-2024 v5.0.0 | |
| emedicinal-product-info | Electronic Medicinal Product Information (ePI) FHIR Implementation Guide null | 1.0.0 Jan-2023 v5.0.0 | |
| eyecare | HL7 FHIR® Implementation Guide: Ophthalmology Retinal, Release 1 This overarching goal is to develop a suite of projects and comprehensive implementation guides to serve the interoperability requirements of the ophthalmic community. | null vnull | 0.1.0 Jan-2021 v4.0.1 |
| fhir-clinical-document | FHIR Clinical Documents This implementation guide defines a canonical representation of a clinical document in FHIR. It serves as a common universal starting point for those creating their own FHIR clinical document specifications, and supports CDA users who wish to migrate to a FHIR-based representation of clinical documents. The intent of the HL7 Structured Documents WG that this IG replace the current FHIR R4 and R5 Core Clinical Document guidance | null vnull | 1.0.0-ballot Jan-2024 v4.0.1 |
| fhir-for-fair | FHIR for FAIR - FHIR Implementation Guide null | 1.0.0 Jan-2022 v4.3.0 | |
| fhircast | FHIRcast FHIRcast synchronizes healthcare applications in real time to show the same clinical content to a common user. | 2.0.0 Jan-2021 v4.0.1 | 3.0.0-ballot Jan-2024 v4.0.1 |
| genomics-reporting | Genetic Reporting Implementation Guide Genomics is a rapidly evolving area of healthcare that involves complex data structures. There is significant value in sharing this information in a way that is consistent, computable and that can accommodate ongoing evolution of medical science and practice. The value comes from the ability to easily sort, filter and perform decision support on such information and the resulting improvements in care and reduction in costs such as the elimination of redundant testing. The implementation guide is also transmission protocol-independent - the data structures presented here could be used in RESTful, messaging, document or other paradigms. This guide covers all aspects of human genomic genomics-reporting, including:
At present, this implementation guide focuses solely on data structures - what data should be/might be present and how it should be organized. It does not address workflows around how reports are requested, created, approved, routed, delivered, amended, etc. The implementation guide is also paradigm-independent - the data structures presented here could be used in RESTful, messaging, documents or other mechanisms. | 2.0.0 Jan-2022 v4.0.1 | 3.0.0-ballot Jan-2023 v4.0.1 |
| ibcm | International Birth And Child Model Implementation Guide During a pregnancy clinical systems communicate data about the mother, the unborn fetus(es), the pregnancy, and child(ren). This includes information shared among EHR, ultrasound, radiology, lab and pharmacy systems. This IG explains how you model and communicate data and relate the fetus(es) to the mother using the FHIR resource Patient with extension indicating a distinct fetal record. Options for referencing information such as observation about the fetus as a body site within the maternal record will also be included. Examples and diagrams are provided to illustrate the use cases. | null vnull | 1.0.0-ballot2 Jan-2024 v5.0.0 |
| ichom-breast-cancer | ICHOM FHIR Implementation Guide: Breast Cancer null | 1.0.0 Jan-2023 v4.0.1 | |
| ihe-sdc-ecc | IHE SDC/eCC on FHIR null | 1.0.0 Jan-2023 v4.0.1 | |
| immds | Immunization Decision Support Forecast FHIR IG The scope of this project is to produce and ballot a Standard for Trial Use (STU) Fast Healthcare Interoperability Resources (FHIR) implementation guide (IG) for use in Immunization Decision Support Forecast. | null vnull | 0.2.0 Jan-2019 v4.0.0 |
| ipa | International Patient Access The International Patient Access implementation guide (IPA) defines a minimal, base set of FHIR profiles and FHIR RESTful interactions. In addition, IPA specifies the use of SMART on FHIR for authentication and authorization. It can be used as-is or as a foundation for developing national standards to enable patients access to their healthcare data via FHIR-enabled patient-facing apps. The IPA Profiles are informed by a range of national base FHIR specifications circa 2022. As a foundational guide with an international focus, its content will continue to grow to meet global needs. | 1.0.0 Jan-2023 v4.0.1 | |
| ips | International Patient Summary Implementation Guide The International Patient Summary (IPS) is a minimal and non-exhaustive patient summary, specialty-agnostic, condition-independent, but readily usable by clinicians for the cross-border unscheduled care of a patient. It supports:
| 1.1.0 Jan-2022 v4.0.1 | 2.0.0-ballot Jan-2024 v4.0.1 |
| lab-report | HL7 Laboratory Report This is a Universal realm FHIR Implementation Guide that facilitates global interoperability for laboratory reporting and harmonization among national and international (global) laboratory reporting initiatives. The reporting approach is based on a FHIR Bundle with included resources based on a Composition resource for structuring the result data and enabling validation as a FHIR clinical document, and a DiagnosticReport resource providing for consistent REST-based querying and data retrieval. The Bundle includes one or more Observation resources containing the laboratory result data, plus additional required resources (Patient, Specimen, etc.) for the complete representation of the laboratory report. The IG scope is a set of HL7 FHIR rules for defining the representation of a Laboratory Report in the universal context in the core domains of in-vitro diagnostics (for example clinical biochemistry, haematology, immunohematology, microbiology, immunology, while currently not including more specialised laboratory domains such as histopathology and medical genetics). The focus is on common rules that apply to all of the in-scope domains. The guide is not limited to the results of tests performed by clinical laboratories on human specimens (from a human subject), but it may also include the results of observations on non-human materials or living subjects, or non-human specimens paired with a human subject. | null vnull | 1.0.0-ballot Jan-2024 v4.0.1 |
| livd | Loinc/IVD Mapping FHIR IG The LIVD Implementation Guide provides a industry standard expression for an IVD device manufacturer As an LIS manager/analyst is configuring a device to be connected to the LIS, the suggested mappings can focus the manager/analyst on the most likely LOINC codes to consider, thus enabling a choice relevant to the specific context of the device`s use and purpose within the Laboratory that is more consistent across the industry. | null vnull | 1.0.0-ballot Jan-2023 v4.0.1 |
| mhealth-framework | Application Data Exchange Assessment Framework and Functional Requirements for Mobile Health Document the functional requirements that can be used to assess devices, applications, and FHIR profiles to ensure that the essential data needed for clinical, patient and research uses is present in communications between applications. | null vnull | 0.1.0 Jan-2020 v4.0.1 |
| order-catalog | Order Catalog Implementation Guide Order Catalog Implementation Guide | null vnull | 0.1.0 Jan-2020 v4.0.1 |
| patient-corrections | Patient Request for Corrections Implementation Guide The Patient Request for Corrections Implementation Guide provides a method for communicating a patient's request for corrections to their patient data, as well as a way for health care organizations to respond to those requests. | null vnull | 1.0.0-ballot Jan-2022 v4.0.1 |
| pddi | Potential Drug-Drug Interaction (PDDI) Clinical Decision Support (CDS) (FHIR IG) This implementation guide is targeted at drug-drug interaction CDS implementers who seek to increase the specificity and clinical relevance of potential drug-drug interaction (PDDI) alerts presented through the electronic health record. | null vnull | 1.0.0-ballot Jan-2022 v4.0.1 |
| pharm-quality | Pharmaceutical Quality (Industry) The FHIR resource profiles specified in this implementation guide represent data in the ICH Quality Guidelines (https://www.ich.org/page/quality-guidelines). This implementation guide defines universal realm structured data elements to support structured authoring (e.g., master data; advanced analysis) for the creation and exchange of Quality information internationally. | 1.0.0 Jan-2024 v5.0.0 | |
| phd | Personal Health Device FHIR IG The Personal Connected Health Alliance (PCHA) Continua implementation guide describes how information from Continua-certified personal health devices (PHDs) is represented in FHIR. PHDs are devices that are mostly used in home-care contexts and include Continua-certified devices such as glucose meters, blood pressure cuffs, weight scales, thermometer, etc. The purpose of this implementation guide is to specify the FHIR components and their mappings to the PHD information. This Implementation Guide was developed by the Continua Alliance Health and Fitness Server Working group with eventual participation in the Devices on FHIR (DoF) working group and the DoF initiative. This is a collaborative effort between the HL7 Health Care Devices Working Group, Integrating the Healthcare Enterprise (IHE), and Continua/Personal Connected Health Alliance (PCHAlliance). | 1.1.0 Jan-2024 v4.0.1 | |
| pocd | Point-of-care Device FHIR IG This Implementation Guide defines the use of FHIR resources to convey measurements and supporting data from acute care point-of-care medical devices (PoCD) to receiving systems for electronic medical records, clinical decision support, and medical data archiving for aggregate quality measurement and research purposes. The Point-of-Care Device (PoCD) Implementation Guide was developed by the Devices on FHIR (DoF) initiative. This is a collaborative effort between the HL7 Health Care Devices Working Group, Integrating the Healthcare Enterprise (IHE), and the Personal Connected Health Alliance (PCHAlliance) / Continua. The objective of the DoF group is to ensure a consistent use of FHIR for exchanging health device information, including:
| null vnull | 0.3.0 Jan-2021 v4.0.1 |
| radiation-dose-summary | Radiation Dose Summary for Diagnostic Procedures on FHIR Radiation Dose Summary for Diagnostic Procedures on FHIR standardizes the sharing of minimal radiation information following a performed exam. | null vnull | 0.1.0 Jan-2021 v4.0.1 |
| rtls | Real Time Location Services Implementation Guide This implementation guide defines the use of FHIR resources to exchange information that describes the location of patients, providers, staff, equipment, or other permanent assets within a hospital or other healthcare facility. This data is typically exchanged between a healthcare system (e.g. EHR software) and a Real Time Location System (RTLS) that captures, processes, and stores information about the location of tracking tags. The tracking tags are associated with an assigned subject (i.e. patients, providers, assets) and their location data is recorded as the associated subject moves throughout a healthcare facility. This location data has many applications in the healthcare context, such as workflow automation, staff/asset tracking, and patient monitoring. The communication workflows that this implementation guide enables includes tag location updates, association/disassociation from subjects, co-location notifications, status updates, availability updates, and other auxiliary functions (e.g. button presses) a tag may offer. Note that it only provides a communication model for notifying interested parties that these events occurred, and does not define the situational requirements for which each event is applicable. | null vnull | 1.0.0-ballot Jan-2023 v5.0.0 |
| saner | Situational Awareness for Novel Epidemic Response The goal of publishing this guide is to encourage the creation of a community interested in extremely rapid development of interfaces that can support communication Bed and other resources to Public Health in this time of crisis. It is the technical part of a multi-pronged effort to develop a workable, quickly deployable, national approach for situational awareness. The initial short-term goals of this are three fold:
| 1.0.0 Jan-2021 v4.0.1 | |
| sdc | Structured Data Capture FHIR IG The SDC (Structured Data Capture) specification is an Implementation Guide of the FHIR Specification that provides an infrastructure to standardize the capture and expanded use of patient-level data collected within an EHR. | 3.0.0 Jan-2022 v4.0.1 | 3.0.0-preview Jan-2022 v4.0.1 |
| security-label-ds4p | FHIR Data Segmentation for Privacy Application of FHIR meta.security to segment FHIR Bundles and Resources per applicable policy. | 1.0.0 Jan-2023 v4.0.1 | |
| shc-vaccination | SMART Health Cards Vaccination and Testing, Release 1 | STU 1 Defines the clinical and patient information contained within a SMART Health Card related to vaccination and lab results for an infectious disease. | null vnull | 0.6.2 Jan-2021 v4.0.1 |
| shorthand | FHIR Shorthand FHIR Shorthand (FSH) is a domain-specific language (DSL) for defining the content of FHIR Implementation Guides (IG). | 3.0.0 Jan-2024 v4.0.1 | |
| smart-app-launch | Smart App Launch Implementation Guide null | 2.0.0 Jan-2021 v4.0.1 | 2.1.0-ballot Jan-2022 v4.0.1 |
| smart-health-cards-and-links | SMART Health Cards and Links FHIR IG The SMART Health Cards and Links FHIR Implementation Guide defines secure, standards-based mechanisms for individuals to store, share, and manage their health data. | null vnull | 1.0.0-ballot Jan-2024 v4.0.1 |
| smart-web-messaging | SMART Web Messaging Implementation Guide: STU1 The SMART Web Messaging Implementation Guide enables SMART-launched apps a standard way to communicate with the fixture that launched the app. | 1.0.0 Jan-2022 v4.0.1 | |
| subscriptions-backport | Subscriptions R5 Backport This guide defines a standard method of back-porting the R5 subscriptions API to R4 implementations as to bridge for pre-adopting R5 Subscriptions prior to adoption of the R5 FHIR standard. | 1.1.0 Jan-2023 v4.3.0 | 1.2.0-ballot Jan-2023 v4.3.0 |
| termchangeset | Terminology Change Set Exchange This IG provides profiles and implementation guidance for exchanging terminology change sets that include full semantic detail from the source terminology utilizing the CodeSystem resource. It also addresses exchanging terminology change sets containing provisional concepts not yet incorporated in source terminologies, such as those requiring rapid distribution during a pandemic-response context. Analysis of semantic detail to include in a change set is informed by the Tinkar Standardized Terminology Knowledgebase (https://www.hl7.org/implement/standards/product_brief.cfm?product_id=573) Reference Model, and mappings from that architecture are included on CodeSystem profiles. It provides background and context for the Tinkar Standardized Terminology Knowledgebase Reference Model and its native representation to enable lossless knowledge assets in various formats. In 2021, HL7 published the HL7 Logical Model: Standardized Terminology Knowledgebase, Release 1—an informative document outlining the requirements for managing terminology across diverse healthcare organizations. This document emphasized the need for a robust terminology foundation, supporting extensions for various informatics systems. It introduced a self-describing logical model for terminology knowledge bases, specifically designed to represent standard terminology modules such as SNOMED CT Releases, value sets, coding systems, local terms, and equivalence mappings. The logical model comprehensively captured internal semantics, concept details, detailed relationships between terms, and hierarchies of standard terminology modules. The foundation for a standard-based Terminology Knowledge Architecture (Tinkar) specification was articulated to facilitate knowledge management for terminology among vendors, providers, and standards development organizations, including Health Level Seven International (HL7). | null vnull | 1.0.0-ballot Jan-2024 v4.0.1 |
| v2mappings | HL7 Version 2 to FHIR The HL7 V2 to FHIR Implementation Guide supports the mapping of HL7 Version 2 messages segments, datatypes and vocabulary to HL7 FHIR Release 4.0 Bundles, Resources, Data Types and Coding Systems. | null vnull | 1.0.0-ballot Jan-2023 v4.0.1 |
| vhdir | Validated Healthcare Directory FHIR IG The Validated Healthcare Directory (VHDir) Implementation Guide defines the minimum conformance requirements for accessing or exposing validated healthcare directory data. It provides a specification for the exchange of directory data between a source of validated provider data and local workflow environments (e.g. local directories). The specification is supports international stakeholders and also meet the specific needs of the US Realm. This implementation guide is developed in cooperation with the Office of the National Coordinator for Health Information Technology (ONC) and the HL7 International Patient Administration Work Group, and the HL7 US Realm Steering Committee. | null vnull | 0.2.0 Dec-2017 v3.5.0 |
| vulcan-rwd | Retrieval of Real World Data for Clinical Research null | 1.0.0 Jan-2023 v4.0.1 | |
| vulcan-schedule | Clinical Study Schedule of Activities null | 1.0.0 Jan-2023 v4.0.1 |
| IG | Name | Version | Type | Date | Age |
| cql | Using CQL with FHIR Implementation Guide | 1.0.0 | Publication | 2024-01-31 | 261 days |
| crmi | Canonical Resource Management Infrastructure Implementation Guide | 1.0.0 | Publication | 2024-01-31 | 261 days |
| ae-research-backport-ig | Adverse Event Clinical Research R4 Backport | 1.0.1 | Publication | 2024-01-30 | 262 days |
| ae-research-ig | Adverse Event Clinical Research | 1.0.1 | Publication | 2024-01-30 | 262 days |
| shorthand | FHIR Shorthand | 3.0.0 | Publication | 2024-01-19 | 273 days |
| phd | Personal Health Device FHIR IG | 1.1.0 | Publication | 2024-01-18 | 274 days |
| termchangeset | Terminology Change Set Exchange | 1.0.0-ballot | Candidate | 2024-01-14 | 278 days |
| lab-report | HL7 Laboratory Report | 1.0.0-ballot | Candidate | 2024-01-14 | 278 days |
| application-feature | FHIR Application Feature Framework Implementation Guide | 1.0.0-ballot | Candidate | 2024-01-13 | 279 days |
| ips | International Patient Summary Implementation Guide | 2.0.0-ballot | Candidate | 2024-01-12 | 280 days |
| fhircast | FHIRcast | 3.0.0-ballot | Candidate | 2024-01-10 | 282 days |
| dicom-sr | DICOM® SR to FHIR Resource Mapping IG | 1.0.0-ballot | Candidate | 2024-01-09 | 283 days |
| ibcm | International Birth And Child Model Implementation Guide | 1.0.0-ballot2 | Candidate | 2024-01-09 | 283 days |
| smart-health-cards-and-links | SMART Health Cards and Links FHIR IG | 1.0.0-ballot | Candidate | 2024-01-08 | 284 days |
| fhir-clinical-document | FHIR Clinical Documents | 1.0.0-ballot | Candidate | 2024-01-08 | 284 days |
| pharm-quality | Pharmaceutical Quality (Industry) | 1.0.0 | Publication | 2024-01-08 | 284 days |
| cardx-htn-mng | CardX Hypertension Management IG | 1.0.0-ballot | Candidate | 2024-01-05 | 287 days |
| ehrs-rle | EHRS Functional Model - Record Lifecycle Events Implementation Guide | 1.1.0 | Publication | 2024-01-02 | 290 days |
| rtls | Real Time Location Services Implementation Guide | 1.0.0-ballot | Candidate | 2023-01-30 | 627 days |
| emedicinal-product-info | Electronic Medicinal Product Information (ePI) FHIR Implementation Guide | 1.0.0 | Publication | 2023-01-26 | 631 days |
| ipa | International Patient Access | 1.0.0 | Publication | 2023-01-26 | 631 days |
| vulcan-rwd | Retrieval of Real World Data for Clinical Research | 1.0.0 | Publication | 2023-01-25 | 632 days |
| livd | Loinc/IVD Mapping FHIR IG | 1.0.0-ballot | Candidate | 2023-01-21 | 636 days |
| ichom-breast-cancer | ICHOM FHIR Implementation Guide: Breast Cancer | 1.0.0 | Publication | 2023-01-21 | 636 days |
| v2mappings | HL7 Version 2 to FHIR | 1.0.0-ballot | Candidate | 2023-01-20 | 637 days |
| cpg | Clinical Guidelines | 2.0.0-ballot | Candidate | 2023-01-19 | 638 days |
| genomics-reporting | Genetic Reporting Implementation Guide | 3.0.0-ballot | Candidate | 2023-01-18 | 639 days |
| subscriptions-backport | Subscriptions R5 Backport | 1.2.0-ballot | Candidate | 2023-01-18 | 639 days |
| vulcan-schedule | Clinical Study Schedule of Activities | 1.0.0 | Publication | 2023-01-18 | 639 days |
| ebm | Evidence Based Medicine on FHIR Implementation Guide | 1.0.0-ballot | Candidate | 2023-01-17 | 640 days |
| security-label-ds4p | FHIR Data Segmentation for Privacy | 1.0.0 | Publication | 2023-01-17 | 640 days |
| ihe-sdc-ecc | IHE SDC/eCC on FHIR | 1.0.0 | Publication | 2023-01-12 | 645 days |
| patient-corrections | Patient Request for Corrections Implementation Guide | 1.0.0-ballot | Candidate | 2022-01-28 | 994 days |
| fhir-for-fair | FHIR for FAIR - FHIR Implementation Guide | 1.0.0 | Publication | 2022-01-27 | 995 days |
| sdc | Structured Data Capture FHIR IG | 3.0.0-preview | Candidate | 2022-01-15 | 1007 days |
| pddi | Potential Drug-Drug Interaction (PDDI) Clinical Decision Support (CDS) (FHIR IG) | 1.0.0-ballot | Candidate | 2022-01-06 | 1016 days |
| smart-web-messaging | SMART Web Messaging Implementation Guide: STU1 | 1.0.0 | Publication | 2022-01-05 | 1017 days |
| smart-app-launch | Smart App Launch Implementation Guide | 2.1.0-ballot | Candidate | 2022-01-03 | 1019 days |
| cdisc-mapping | CDISC Mapping FHIR IG | 1.0.0 | Publication | 2021-01-30 | 1357 days |
| bulkdata | FHIR Bulk Data Access (Flat FHIR) | 2.0.0 | Publication | 2021-01-25 | 1362 days |
| pocd | Point-of-care Device FHIR IG | 0.3.0 | Candidate | 2021-01-13 | 1374 days |
| shc-vaccination | SMART Health Cards Vaccination and Testing, Release 1 | STU 1 | 0.6.2 | Candidate | 2021-01-12 | 1375 days |
| eyecare | HL7 FHIR® Implementation Guide: Ophthalmology Retinal, Release 1 | 0.1.0 | Candidate | 2021-01-11 | 1376 days |
| radiation-dose-summary | Radiation Dose Summary for Diagnostic Procedures on FHIR | 0.1.0 | Candidate | 2021-01-07 | 1380 days |
| saner | Situational Awareness for Novel Epidemic Response | 1.0.0 | Publication | 2021-01-06 | 1381 days |
| cdisc-lab | CDISC Lab Semantics in FHIR | 1.0.0 | Publication | 2020-01-26 | 1727 days |
| mhealth-framework | Application Data Exchange Assessment Framework and Functional Requirements for Mobile Health | 0.1.0 | Candidate | 2020-01-15 | 1738 days |
| order-catalog | Order Catalog Implementation Guide | 0.1.0 | Candidate | 2020-01-04 | 1749 days |
| immds | Immunization Decision Support Forecast FHIR IG | 0.2.0 | Candidate | 2019-01-28 | 2090 days |
| vhdir | Validated Healthcare Directory FHIR IG | 0.2.0 | Candidate | 2017-12-31 | 2483 days |
®© HL7 |
