[{"name":"hl7.fhir.r2.core","version":"1.0.2","fhirVersion":"1.0.2","canonical":"http://hl7.org/fhir","kind":"fhir.core","url":"https://packages2.fhir.org/web/hl7.fhir.r2.core-1.0.2.tgz","date":"2015-10-24T12:00:00.000Z","description":"Definitions (API, structures and terminologies) for the R2 version of the FHIR standard"},{"name":"hl7.fhir.r2.corexml","version":"1.0.2","fhirVersion":"1.0.2","canonical":"http://hl7.org/fhir","kind":"fhir.core","url":"https://packages2.fhir.org/web/hl7.fhir.r2.corexml-1.0.2.tgz","date":"2015-10-24T12:00:00.000Z","description":"Definitions (API, structures and terminologies) for the R2 version of the FHIR standard"},{"name":"hl7.fhir.r2.examples","version":"1.0.2","fhirVersion":"1.0.2","canonical":"http://hl7.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.r2.examples-1.0.2.tgz","date":"2015-10-24T12:00:00.000Z","description":"Example resources in the R2 version of the FHIR standard"},{"name":"hl7.fhir.r2.expansions","version":"1.0.2","fhirVersion":"1.0.2","canonical":"http://hl7.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.r2.expansions-1.0.2.tgz","date":"2015-10-24T12:00:00.000Z","description":"Expansions for the R2 version of the FHIR standard"},{"name":"hl7.fhir.r2.elements","version":"1.0.2","fhirVersion":"1.0.2","canonical":"http://hl7.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.r2.elements-1.0.2.tgz","date":"2015-10-24T12:00:00.000Z","description":"Element Definitions for types defined in the R2 version of the FHIR standard"},{"name":"hl7.fhir.r2b.core","version":"1.4.0","fhirVersion":"1.4.0","canonical":"http://hl7.org/fhir","kind":"fhir.core","url":"https://packages2.fhir.org/web/hl7.fhir.r2b.core-1.4.0.tgz","date":"2016-03-30T12:00:00.000Z","description":"Definitions (API, structures and terminologies) for the R2b version of the FHIR standard"},{"name":"hl7.fhir.r2b.corexml","version":"1.4.0","fhirVersion":"1.4.0","canonical":"http://hl7.org/fhir","kind":"fhir.core","url":"https://packages2.fhir.org/web/hl7.fhir.r2b.corexml-1.4.0.tgz","date":"2016-03-30T12:00:00.000Z","description":"Definitions (API, structures and terminologies) for the R2b version of the FHIR standard"},{"name":"hl7.fhir.r2b.examples","version":"1.4.0","fhirVersion":"1.4.0","canonical":"http://hl7.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.r2b.examples-1.4.0.tgz","date":"2016-03-30T12:00:00.000Z","description":"Example resources in the R2b version of the FHIR standard"},{"name":"hl7.fhir.r2b.expansions","version":"1.4.0","fhirVersion":"1.4.0","canonical":"http://hl7.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.r2b.expansions-1.4.0.tgz","date":"2016-03-30T12:00:00.000Z","description":"Expansions for the R2b version of the FHIR standard"},{"name":"fhir.argonaut.r2","version":"1.0.0","fhirVersion":"1.0.2","canonical":"http://fhir.org/guides/argonaut/r2","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.argonaut.r2-1.0.0.tgz","date":"2016-12-23T12:00:00.000Z"},{"name":"fhir.hspc.core","version":"0.1.0","fhirVersion":"1.9.0","canonical":"http://fhir.org/guides/hspc/core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.hspc.core-0.1.0.tgz","date":"2016-12-23T12:00:00.000Z"},{"name":"hl7.fhir.us.daf","version":"2.0.0","fhirVersion":"3.0.1","canonical":"http://hl7.org/fhir/us/daf","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.daf-2.0.0.tgz","date":"2017-04-21T12:00:00.000Z"},{"name":"fhir.argonaut.pd","version":"1.0.0","fhirVersion":"3.0.1","canonical":"http://fhir.org/guides/argonaut/pd","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.argonaut.pd-1.0.0.tgz","date":"2017-06-15T12:00:00.000Z"},{"name":"fhir.argonaut.scheduling","version":"1.0.0","fhirVersion":"3.0.1","canonical":"http://fhir.org/guides/argonaut/scheduling","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.argonaut.scheduling-1.0.0.tgz","date":"2018-04-23T12:00:00.000Z"},{"name":"hl7.fhir.us.breastcancer","version":"0.2.0","fhirVersion":"3.0.1","canonical":"http://hl7.org/fhir/us/breastcancer","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.breastcancer-0.2.0.tgz","date":"2018-08-31T12:00:00.000Z"},{"name":"hl7.fhir.au.rcpa","version":"0.1.0","fhirVersion":"3.0.1","canonical":"http://hl7.org.au/fhir/rcpa","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.au.rcpa-0.1.0.tgz","date":"2019-02-20T12:00:00.000Z"},{"name":"hl7.fhir.us.bulkdata","version":"0.1.0","fhirVersion":"4.0.0","canonical":"http://hl7.org/fhir/us/bulkdata","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.bulkdata-0.1.0.tgz","date":"2019-03-27T12:00:00.000Z"},{"name":"hl7.fhir.us.patient-reported-outcomes","version":"0.2.0","fhirVersion":"4.0.0","canonical":"http://hl7.org/fhir/us/patient-reported-outcomes","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.patient-reported-outcomes-0.2.0.tgz","date":"2019-03-27T12:00:00.000Z"},{"name":"fhir.argonaut.clinicalnotes","version":"1.0.0","fhirVersion":"3.0.1","canonical":"http://fhir.org/guides/argonaut/clinicalnotes","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.argonaut.clinicalnotes-1.0.0.tgz","date":"2019-04-18T12:00:00.000Z"},{"name":"fhir.argonaut.questionnaire","version":"1.0.0","fhirVersion":"3.0.1","canonical":"http://fhir.org/guides/argonaut/questionnaire","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.argonaut.questionnaire-1.0.0.tgz","date":"2019-04-18T12:00:00.000Z"},{"name":"hl7.fhir.uv.immds","version":"0.2.0","fhirVersion":"4.0.0","canonical":"http://hl7.org/fhir/uv/immds","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.immds-0.2.0.tgz","date":"2019-07-29T12:00:00.000Z"},{"name":"hl7.fhir.au.pd","version":"2.0.1","fhirVersion":"4.0.0","canonical":"http://hl7.org.au/fhir/pd","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.au.pd-2.0.1.tgz","date":"2019-08-15T12:00:00.000Z"},{"name":"hl7.fhir.r3.core","version":"3.0.2","fhirVersion":"3.0.2","canonical":"http://hl7.org/fhir","kind":"fhir.core","url":"https://packages2.fhir.org/web/hl7.fhir.r3.core-3.0.2.tgz","date":"2019-10-24T12:00:00.000Z","description":"Definitions (API, structures and terminologies) for the R3 version of the FHIR standard"},{"name":"hl7.fhir.r3.corexml","version":"3.0.2","fhirVersion":"3.0.2","canonical":"http://hl7.org/fhir","kind":"fhir.core","url":"https://packages2.fhir.org/web/hl7.fhir.r3.corexml-3.0.2.tgz","date":"2019-10-24T12:00:00.000Z","description":"Definitions (API, structures and terminologies) for the R3 version of the FHIR standard"},{"name":"hl7.fhir.r3.examples","version":"3.0.2","fhirVersion":"3.0.2","canonical":"http://hl7.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.r3.examples-3.0.2.tgz","date":"2019-10-24T12:00:00.000Z","description":"Example resources in the R3 version of the FHIR standard"},{"name":"hl7.fhir.r3.expansions","version":"3.0.2","fhirVersion":"3.0.2","canonical":"http://hl7.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.r3.expansions-3.0.2.tgz","date":"2019-10-24T12:00:00.000Z","description":"Expansions for the R3 version of the FHIR standard"},{"name":"hl7.fhir.r3.elements","version":"3.0.2","fhirVersion":"3.0.2","canonical":"http://hl7.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.r3.elements-3.0.2.tgz","date":"2019-10-24T12:00:00.000Z","description":"Element Definitions for types defined in the R3 version of the FHIR standard"},{"name":"hl7.fhir.r4.core","version":"4.0.1","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir","kind":"fhir.core","url":"https://packages2.fhir.org/web/hl7.fhir.r4.core-4.0.1.tgz","date":"2019-10-30T12:00:00.000Z","description":"Definitions (API, structures and terminologies) for the R4 version of the FHIR standard"},{"name":"hl7.fhir.r4.corexml","version":"4.0.1","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir","kind":"fhir.core","url":"https://packages2.fhir.org/web/hl7.fhir.r4.corexml-4.0.1.tgz","date":"2019-10-30T12:00:00.000Z","description":"Definitions (API, structures and terminologies) for the R4 version of the FHIR standard"},{"name":"hl7.fhir.r4.examples","version":"4.0.1","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.r4.examples-4.0.1.tgz","date":"2019-10-30T12:00:00.000Z","description":"Example resources in the R4 version of the FHIR standard"},{"name":"hl7.fhir.r4.expansions","version":"4.0.1","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.r4.expansions-4.0.1.tgz","date":"2019-10-30T12:00:00.000Z","description":"Expansions for the R4 version of the FHIR standard"},{"name":"hl7.fhir.r4.elements","version":"4.0.1","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.r4.elements-4.0.1.tgz","date":"2019-10-30T12:00:00.000Z","description":"Element Definitions for types defined in the R4 version of the FHIR standard"},{"name":"hl7.fhir.xver.r4","version":"1.2.0","fhirVersion":"4.0","canonical":"http://fhir.org/packages/hl7.fhir.xver.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.xver.r4-1.2.0.tgz","date":"2020-03-13T10:01:11.000Z"},{"name":"hl7.fhir.uv.mhealth-framework","version":"0.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/mhealth-framework","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.mhealth-framework-0.1.0.tgz","date":"2020-04-16T12:00:00.000Z","description":"aDocument 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. (built Thu, Apr 16, 2020 18:23+0000+00:00)"},{"name":"hl7.fhir.xver.r3","version":"1.2.1","fhirVersion":"3.0","canonical":"http://fhir.org/packages/hl7.fhir.xver.r3","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.xver.r3-1.2.1.tgz","date":"2020-05-13T04:35:00.000Z"},{"name":"fhir.test.data.r2","version":"0.2.1","fhirVersion":"1.0.2","canonical":"http://fhir.org/test-data","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.test.data.r2-0.2.1.tgz","date":"2020-05-13T06:10:45.000Z","description":"Useful test data for working with FHIR"},{"name":"fhir.test.data.r4","version":"0.2.1","fhirVersion":"4.0.1","canonical":"http://fhir.org/test-data","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.test.data.r4-0.2.1.tgz","date":"2020-05-13T06:10:46.000Z","description":"Useful test data for working with FHIR"},{"name":"fhir.test.data.r3","version":"0.2.1","fhirVersion":"3.0.2","canonical":"http://fhir.org/test-data","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.test.data.r3-0.2.1.tgz","date":"2020-05-13T06:10:46.000Z","description":"Useful test data for working with FHIR"},{"name":"hl7.fhir.uv.order-catalog","version":"0.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/order-catalog","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.order-catalog-0.1.0.tgz","date":"2020-08-05T12:00:00.000Z","description":"An Order Catalog is an administered homogeneous collection of items such as medication products, laboratory tests, procedures, medical devices or knowledge artifacts such as order sets, which support the ordering process, or more generally healthcare processes. (built Sun, Aug 9, 2020 15:18+0000+00:00)"},{"name":"hl7.fhir.us.vitalsigns","version":"0.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/vitals","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.vitalsigns-0.1.0.tgz","date":"2020-08-07T12:00:00.000Z"},{"name":"hl7.fhir.us.dme-orders","version":"0.2.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/dme-orders","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.dme-orders-0.2.0.tgz","date":"2020-08-10T12:00:00.000Z","description":"# General\nThis is a FHIR R4 Implementation Guide (IG) to support the electronic exchange of post-acute orders and referrals, along with the exchange of supporting documentation between the ordering provider and the specific rendering provider.\n* The initial version of the implementation guide (IG) will focus on orders and documentation for Durable Medical Equipment (DME) and Home Health Services. It is important to note that supporting DME also requires the support for medications associated with specific devices such as nebulizers and infusion pumps. It is the goal of future versions of this implementation guide to support orders for all post-acute services. \n* This specification is currently undergoing connectathon testing. It is expected to evolve, possibly significantly, as part of that process.\n\nThis implementation guide is focused on enabling ordering providers to create, communicate and track orders and referrals in the post-acute setting. By enabling ordering providers to communicate supporting documentation in real-time to rendering providers, patients can receive appropriate treatment more rapidly and reduce the burden on rendering providers to comply with payer documentation requirements.\n\n# Change log\n* **0.2.* :**QA versions for the September 2020 ballot cycle (minor version 0.2.x) include QA feedback\n* **0.3.0 :** Final version for the September 2020 ballot cycle\n \n \n# Known issues and to-dos\n* Example of message bundle for message based ordering\n (built Mon, Aug 10, 2020 18:26+0000+00:00)"},{"name":"hl7.fhir.in","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://nrces.in/ndhm/fhir/r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.in-1.0.0.tgz","date":"2020-08-17T04:53:21.000Z"},{"name":"ch.fhir.ig.ch-ems","version":"1.9.0","fhirVersion":"4.0.1","canonical":"http://fhir.ch/ig/ch-ems","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ch.fhir.ig.ch-ems-1.9.0.tgz","date":"2020-08-25T12:00:00.000Z"},{"name":"hl7.fhir.uv.cdisc-lab","version":"1.0.0","fhirVersion":"4.5.0","canonical":"http://hl7.org/fhir/uv/cdisc-lab","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.cdisc-lab-1.0.0.tgz","date":"2020-08-27T12:00:00.000Z"},{"name":"fhir.tx.support.r2","version":"0.3.0","fhirVersion":"1.0.2","canonical":"http://fhir.org/terminology-support","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.tx.support.r2-0.3.0.tgz","date":"2020-09-24T03:09:24.000Z","description":"Various supporting code systems for tx.fhir.org (R2)"},{"name":"hl7.fhir.us.davinci-pcde","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-pcde","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-pcde-1.0.0.tgz","date":"2020-12-23T12:00:00.000Z","description":"Guidelines for conveying coverage information from one payer to another when a patient changes insurance (built Wed, Dec 23, 2020 03:18+0000+00:00)"},{"name":"hl7.fhir.us.phcp","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/phcp","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.phcp-1.0.0.tgz","date":"2021-02-11T12:00:00.000Z","description":"This document describes constraints on the the FHIR Composition resource for a Pharmacist Care Plan, which are derived from requirements set forth by the Pharmacy Health Information Technology (HIT) Collaborative1 and the National Council for Prescription Drug Programs (NCPDP) WG10 Professional Pharmacy Services,2 vendors, and Health Level Seven (HL7) stakeholder workgroups. Templates in this US Realm implementation guide are specific to pharmacy management treatment and interventions that will promote interoperability and will create information suitable for reuse in quality measurement, public health reporting, research, and reimbursement.\n\nThis guide contains a library of Fast Health Interoperability Resources (FHIR) profiles, and is compliant with the C-CDA on FHIR specification.\n\n### Content and Organization\n\n* [Background](background.html): describes the purpose, audience, general background, and use cases for this guide\n* [Specification](specification.html): covers the detailed implementation requirements and conformance expectation\n* [Acknowledgments](acknowledgments.html): identifies the individuals and organizations involved in developing this implementation guide\n* [Downloads](downloads.html): allows download of this and other specifications as well as other useful files\n* [Artifacts Summary](artifacts.html): introduces and provides links to the FHIR STU3 and R4 profiles, search parameters and other FHIR artifacts used in this implementation guide\n (built Thu, Feb 11, 2021 17:05+0000+00:00)"},{"name":"ch.fhir.ig.template","version":"0.6.0","fhirVersion":"4.0.1","canonical":"http://fhir.ch/ig/template","kind":"fhir.template","url":"https://packages2.fhir.org/web/ch.fhir.ig.template-0.6.0.tgz","date":"2021-06-10T12:00:00.000Z","description":"FHIR HL7 Swiss IG Template"},{"name":"hl7.fhir.us.immds","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/immds","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.immds-1.0.0.tgz","date":"2021-06-25T12:00:00.000Z","description":"An IG for querying a decision support engine for a personalized immunization forecast. (built Fri, Jun 25, 2021 15:56+1000+10:00)"},{"name":"hl7.fhir.uv.eyecare","version":"0.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/eyecare","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.eyecare-0.1.0.tgz","date":"2021-08-12T12:00:00.000Z","description":"The overarching goal is to define and standardize the means through which all types of eye care and general medical providers can communicate (built Thu, Aug 12, 2021 15:08+0000+00:00)"},{"name":"hl7.fhir.uv.shc-vaccination","version":"0.6.2","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/shc-vaccination","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.shc-vaccination-0.6.2.tgz","date":"2021-08-13T12:00:00.000Z","description":"Defines the clinical and patient information contained within a SMART Health Card (SHC) related to vaccination and lab results related to an infectious disease like COVID-19. (built Fri, Aug 13, 2021 13:26+0000+00:00)"},{"name":"hl7.fhir.uv.pocd","version":"0.3.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/pocd","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.pocd-0.3.0.tgz","date":"2021-08-14T12:00:00.000Z","description":"ImplementationGuide for Point-of-Care Devices (PoCD), such as those typically found in a hospital care setting (e.g., physiological monitors, infusion pumps, ventilators, pulse-oximeters, etc.). (built Sat, Aug 14, 2021 20:37+0000+00:00)"},{"name":"hl7.fhir.uv.cdisc-mapping","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/cdisc-mapping","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.cdisc-mapping-1.0.0.tgz","date":"2021-08-31T12:00:00.000Z","description":"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. (built Tue, Aug 31, 2021 16:21+0000+00:00)"},{"name":"hl7.fhir.uv.saner","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/saner","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.saner-1.0.0.tgz","date":"2021-09-07T12:00:00.000Z","description":"The Situational Awareness for Novel Epidemic Response Implementation Guide enables transmission of high level situational awareness information from healthcare facilities to centralized data repositories to support the treatment of the novel coronavirus illness. (built Tue, Sep 7, 2021 19:01+0000+00:00)"},{"name":"hl7.fhir.us.nhsn-ade","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/nhsn-ade","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.nhsn-ade-1.0.0.tgz","date":"2021-10-12T12:00:00.000Z","description":"Adverse drug events (ADEs) are among the most common causes of iatrogenic harm in U.S. hospitals. An effort to establish an EHR- and vendor-neutral standard for submitting ADE data to NHSN is being sought to improve patient safety and facilitate quality improvement effort. This promising initiative seeks to enable EHRs of acute care facilities to serve as source systems for reporting ADE data to the National Healthcare Safety Network (NHSN) via industry electronic messages. This initiative leverages NHSN’s longstanding experience working closely with the Health Level Seven (HL7) standards development organization and HL7 consultants in developing and maintaining electronic healthcare-associated and antibiotic use and resistance reporting implementation guidance for EHRs and infection surveillance system vendors in the acute care arena. That experience, and the working relationships developed over a 10-year partnership, are an important foundation for a collaborative effort in which NHSN, HL7, HL7 consultants, and EHR vendors join forces to advance the field of electronic ADE reporting.\n\nThis first module, Hypoglycemia, planned for the NHSN Medication Safety Component, would enable hospitals to track and benchmark inpatient medication-related hypoglycemia (low blood sugar). Inpatient hypoglycemia can be severe and life-threatening and is associated with longer hospital stays and increased medical costs. Severe hypoglycemia (<40 mg/dL) occurs in 2%-5% of hospitalized patients with diabetes mellitus (DM). Medication-related hypoglycemic events are common causes of adverse drug events (ADEs) occurring in inpatient settings, with rates of severe hypoglycemia varying across hospitals, suggesting opportunities for improvement in the quality of care. Measurement of medication-related hypoglycemia in a meaningful and standardized way may improve glycemic management. The NHSN ADE – Hypoglycemia Module provides a mechanism for facilities to report and analyze medication-related hypoglycemia as part of patient safety and glycemic management quality improvement efforts.\n\nThe measures planned for used in this module are based on quality reporting metrics previously- or currently-endorsed by the National Quality Forum (NQF): NQF #2363 Glycemic Control - Hypoglycemia and NQF #3503 Hospital Harm – Severe Hypoglycemia. The metrics reported in this module would be primarily based on linked eMAR (antidiabetic medication administration) and laboratory (blood glucose) data. These long-standing linkages links between public health and vendors can be leveraged in ways that yield benefits for surveillance and prevention that are tightly coupled to business models and growth. (built Tue, Oct 12, 2021 13:32+0000+00:00)"},{"name":"hl7.fhir.us.nhsn-med-admin","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/nhsn-med-admin","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.nhsn-med-admin-1.0.0.tgz","date":"2021-10-12T12:00:00.000Z","description":"This IG will support electronic submission of patient/line-level medication administration data to the National Healthcare Safety Network (NHSN). The intent of this project is to establish an electronic submission standard that is vendor-neutral that leverages existing workflows and eliminates duplicate documentation. This project will work with EHR vendors to identify data elements that can be used to describe medications administered (name, formulation, route, dose, duration) to hospitalized patients (inpatients) diagnosed with COVID-19 as part of NHSN COVID-19 reporting pathways. Medication administration events would be reported irrespective of whether or not medication administration was linked to an adverse event, refer to clinician-administered events (e.g., nurse giving a patient their medication dose), and only those occurring in inpatient settings; this excludes: emergency department, observation/short stay, inpatient rehabilitation, outpatient surgical centers, and other outpatient (including physician office) settings.\n\nMedication data are integral to informing the quality, safety, and costs of U.S. healthcare, supporting federal, state, and local public health, and guiding clinical decision-making in patient care. In inpatient workflows, medication administration—as captured by electronic medication administration (eMAR) records—is considered the gold standard for accurately measuring in-hospital medication exposure, including identifying the exact medications patients have received, in what formulations, doses, and for what duration of time. The need for medication administration information has never been clearer as during the COVID-19 pandemic, where identification of the medications that acutely ill hospitalized patients with COVID-19 had received was integral to understanding clinical management of this new public health threat and directing public health resources, including scarce medications. The continued reliance on the \"medication list\" resource instead of the \"medication administration\" resource is a severe limitation in achieving accurate representation of medication exposure in U.S. healthcare data through FHIR resources.\n\n### IG\n\nThis implementation guide provides HL7 FHIR resources to define standards for exchange between a hospital and NHSN. \n\nThis publication provides the data model, defined data items, and their corresponding code and value sets, for reporting inpatient medication administration data for inpatients diagnosed with COVID-19. This guide describes constraints on the US Core and base FHIR resources for reporting, which are derived from requirements developed by the NHSN in consultation with the Health Level Seven (HL7) Pharmacy Work Group. Resources in this US Realm implementation guide are specific to reporting medication administration data to NHSN.\n\nThis guide contains a library of FHIR profiles and is compliant with FHIR Release 4. At a minimum, a Document Bundle and Composition will be exchanged along with a Patient, and associated COVID-19 Condition and laboratory results.\n\nThis guide defines 4 new Profiles:\n\n* [Composition - Inpatient Medication Administration](StructureDefinition-Composition-inpatient-med-admin.html)\n* [Condition - Lab Confirmed COVID-19](StructureDefinition-Condition-lab-confirmed-covid.html)\n* [Condition - Suspected COVID-19](StructureDefinition-Condition-suspected-covid.html)\n* [Observation - Laboratory SARS COVID-19](StructureDefinition-Observation-lab-sars-cov.html) (built Tue, Oct 12, 2021 13:08+0000+00:00)"},{"name":"hl7.fhir.us.dental-data-exchange","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/dental-data-exchange","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.dental-data-exchange-1.0.0.tgz","date":"2021-11-02T12:00:00.000Z","description":"This implementation guide provides HL7 FHIR resources to define standards for bi-directional information exchange between a medical and a dental provider or between dental providers. This publication provides the data model, defined data items and their corresponding code and value sets specific to a dental referral note and dental consultation note. This guide describes constraints on the [C-CDA on FHIR](http://www.hl7.org/fhir/us/ccda/) header and body elements for dental information, which are derived from requirements developed by the Dental Summary Exchange Project of the Health Level Seven (HL7) Payer/Provider Information Exchange Work Group (PIE WG). Resources in this US Realm implementation guide are specific to dental referral and consultation notes for exchange and interoperability among dental providers and with medical providers.\n\nThis guide contains a library of FHIR profiles and is compliant with FHIR Release 4. At a minimum, a document bundle (C-CDA on FHIR Referral Note or Consultation Note) will be exchanged along with a ServiceRequest, Patient, and associated medical and dental information. This guide specifies how and where these resources are included within the C-CDA on FHIR profiles. \n\nThis guide defines 7 new profiles:\n* Dental Bundle\n* Dental Referral Note\n* Dental Service Request\n* Dental Consult Note\n* Dental Condition\n* Dental Finding\n* Dental Communication \n\nAll proprietary documents, guides, guidance, standards, codes, and values contained herein remain the property of their respective Standards Developing Organization (SDO). HL7 does not make any claim to ownership herein.\n\nThis HL7 FHIR® R4 Implementation Guide: Dental Data Exchange is developed in parallel to the HL7 CDA® R2 Implementation Guide: Dental Data Exchange.\n (built Tue, Nov 2, 2021 16:19+0000+00:00)"},{"name":"hl7.fhir.us.pacio-cs","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/pacio-cs","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.pacio-cs-1.0.0.tgz","date":"2021-11-03T12:00:00.000Z","description":"To advance interoperable health data exchange between post-acute care (PAC) and other providers, patients, and key stakeholders (built Wed, Nov 3, 2021 21:43+0000+00:00)"},{"name":"hl7.fhir.us.pacio-fs","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/pacio-fs","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.pacio-fs-1.0.0.tgz","date":"2021-11-03T12:00:00.000Z","description":"To advance interoperable health data exchange between post-acute care (PAC) and other providers, patients, and key stakeholders (built Wed, Nov 3, 2021 21:35+0000+00:00)"},{"name":"ihe.mhd.fhir","version":"4.0.2","fhirVersion":"4.0.1","canonical":"http://profiles.ihe.net/ITI/MHD","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.mhd.fhir-4.0.2.tgz","date":"2021-11-08T12:00:00.000Z","description":"ImplementationGuide for IHE IT Infrastructure Technical Framework Supplement Mobile access to Health Documents (MHD) Rev. 4.0.1 normative (built Mon, Nov 8, 2021 19:09-0600-06:00)"},{"name":"fhir.cqf.common","version":"4.0.1","fhirVersion":"4.0.1","canonical":"http://fhir.org/guides/cqf/common","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.cqf.common-4.0.1.tgz","date":"2021-11-12T12:00:00.000Z","description":"This implementation guide contains common FHIR assets for use in CQFramework content IGs, including FHIRHelpers and the FHIR-ModelInfo libraries. (built Fri, Nov 12, 2021 16:25+1100+11:00)"},{"name":"fhir.cdc.opioid-mme-r4","version":"3.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.org/guides/cdc/opioid-mme-r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.cdc.opioid-mme-r4-3.0.0.tgz","date":"2021-11-25T12:00:00.000Z","description":"Opioid Morphine Milligram Equivalent (MME) calculation logic in FHIR and Clinical Quality Language (CQL) (built Thu, Nov 25, 2021 15:13+1100+11:00)"},{"name":"hl7.fhir.us.cdmh","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/cdmh","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.cdmh-1.0.0.tgz","date":"2021-12-06T12:00:00.000Z","description":"CDMH Maps data elements and classes between FHIR and Sentinel, i2b2, PCORnet CDM, OMOP research models. (built Mon, Dec 6, 2021 18:52+0000+00:00)"},{"name":"hl7.fhir.uv.radiation-dose-summary","version":"0.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/radiation-dose-summary","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.radiation-dose-summary-0.1.0.tgz","date":"2021-12-08T12:00:00.000Z","description":"This IG standardizes the sharing of minimal radiation information following a performed exam. Minimal radiation information is required by multiple stakeholders including RIS, EHR, and national/regional stakeholders and their associated regulations. This IG standardizes data sharing from dose management systems to third parties. The IG exposes radiation information related to (and coming from) imaging procedures, but not medications. (built Wed, Dec 8, 2021 15:50+0000+00:00)"},{"name":"hl7.fhir.us.medmorph-research-dex","version":"0.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/medmorph-research-dex","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.medmorph-research-dex-0.1.0.tgz","date":"2021-12-09T12:00:00.000Z","description":"MedMorph Research Content IG enables researchers to access data from EHRs leveraging the MedMorph Reference Architecture. (built Thu, Dec 9, 2021 14:36+0000+00:00)"},{"name":"ch.fhir.ig.ch-crl","version":"0.9.0","fhirVersion":"4.0.1","canonical":"http://fhir.ch/ig/ch-crl","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ch.fhir.ig.ch-crl-0.9.0.tgz","date":"2022-02-04T12:00:00.000Z","description":"Implementation Guide CH CRL (R4) (built Fri, Feb 4, 2022 14:13+0100+01:00)"},{"name":"ch.fhir.ig.cda-fhir-maps","version":"0.3.0","fhirVersion":"4.0.1","canonical":"http://fhir.ch/ig/cda-fhir-maps","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ch.fhir.ig.cda-fhir-maps-0.3.0.tgz","date":"2022-02-11T10:00:00.000Z"},{"name":"hl7.fhir.uv.smart-web-messaging","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/smart-web-messaging","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.smart-web-messaging-1.0.0.tgz","date":"2022-05-06T12:00:00.000Z","description":"The SMART Web Messaging Implementation Guide enables SMART-launched apps a standard way to communicate with the fixture that launched the app. (built Fri, May 6, 2022 17:41+0000+00:00)"},{"name":"ch.fhir.ig.swissnoso","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.ch/ig/swissnoso","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ch.fhir.ig.swissnoso-1.0.0.tgz","date":"2022-06-14T10:00:00.000Z","description":"Implementation guide to specify the exchange format for data transmission to Swissnoso in the context of monitoring and prevention of healthcare-associated infections. (built Tue, Jun 14, 2022 13:09+0200+02:00)"},{"name":"hl7.fhir.us.covid19library","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/covid19library","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.covid19library-1.0.0.tgz","date":"2022-07-25T12:00:00.000Z","description":"The COVID-19 IG describes structured data to be collected and communicated between providers and aggregators. (built Mon, Jul 25, 2022 13:21+0000+00:00)"},{"name":"us.cdc.phinvads","version":"0.12.0","fhirVersion":"4.0.1","canonical":"http://fhir.org/packages/us.cdc.phinvads","kind":"fhir.ig","url":"https://packages2.fhir.org/web/us.cdc.phinvads-0.12.0.tgz","date":"2022-07-27T06:40:52.000Z"},{"name":"hl7.fhir.us.directory-attestation","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/directory-attestation","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.directory-attestation-1.0.0-ballot.tgz","date":"2022-08-09T12:00:00.000Z","description":"National Directory (built Tue, Aug 9, 2022 12:51+0000+00:00)"},{"name":"hl7.fhir.us.directory-exchange","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/directory-exchange","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.directory-exchange-1.0.0-ballot.tgz","date":"2022-08-09T12:00:00.000Z","description":"National Directory (built Tue, Aug 9, 2022 16:36+0000+00:00)"},{"name":"hl7.fhir.us.directory-query","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/directory-query","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.directory-query-1.0.0-ballot.tgz","date":"2022-08-09T12:00:00.000Z","description":"National Directory Query (built Tue, Aug 9, 2022 18:48+0000+00:00)"},{"name":"fhirtools.ig.template","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhirtools.ig.template","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhirtools.ig.template-1.0.0.tgz","date":"2022-08-25T05:08:47.000Z","description":"FHIR profiles, IG used in the digital health training series "},{"name":"dips.fhir.ig.template","version":"1.0.0-beta","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/dips.fhir.ig.template","kind":"fhir.template","url":"https://packages2.fhir.org/web/dips.fhir.ig.template-1.0.0-beta.tgz","date":"2022-08-26T04:45:23.000Z","description":"DIPS IG Template"},{"name":"vzvz.covid-vaccinations","version":"0.5.1-beta","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/vzvz.covid-vaccinations","kind":"fhir.ig","url":"https://packages2.fhir.org/web/vzvz.covid-vaccinations-0.5.1-beta.tgz","date":"2022-08-29T07:00:21.000Z","description":"Exchange of (COVID-19) immunication information"},{"name":"de.transfer-abrechnungsdaten.r4","version":"1.1.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.transfer-abrechnungsdaten.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.transfer-abrechnungsdaten.r4-1.1.2.tgz","date":"2022-08-29T20:47:18.000Z","description":"Transfer von Abrechnungsdaten - Generisches Format für Abrechnungsdaten im deutschen Gesundheitswesen"},{"name":"resource.versioning","version":"0.2.0-beta","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/resource.versioning","kind":"fhir.ig","url":"https://packages2.fhir.org/web/resource.versioning-0.2.0-beta.tgz","date":"2022-08-30T03:12:30.000Z","description":"For demonstrating purposes only"},{"name":"uk.adsv2.r4","version":"1.6.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/uk.adsv2.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/uk.adsv2.r4-1.6.1.tgz","date":"2022-09-02T08:59:28.000Z","description":"Put a description here"},{"name":"hl7-france-fhir.administrative-2022","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/hl7-france-fhir.administrative-2022","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7-france-fhir.administrative-2022-1.0.0.tgz","date":"2022-09-05T09:30:50.000Z","description":"Package HL7 France FHIR R4 (Administrative)\r\n\r\n__Release 2022__ "},{"name":"duwel.nl.r4.sandbox.dev","version":"0.0.1-dev.4","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/duwel.nl.r4.sandbox.dev","kind":"fhir.ig","url":"https://packages2.fhir.org/web/duwel.nl.r4.sandbox.dev-0.0.1-dev.4.tgz","date":"2022-09-08T11:51:03.000Z","description":"Jorn Duwel sandbox"},{"name":"hl7.fhir.be.lab","version":"1.0.0","fhirVersion":"4.0.1","canonical":"https://www.ehealth.fgov.be/standards/fhir/lab","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.be.lab-1.0.0.tgz","date":"2022-09-09T18:01:08.000Z","description":"HL7 BE Laboratory WG Implementation Guide (built Thu, Sep 8, 2022 14:30+0200+02:00)"},{"name":"fhir.ca.template","version":"0.2.0","fhirVersion":"4.0.1","canonical":"http://fhir.org/templates/fhir.ca.template","kind":"fhir.template","url":"https://packages2.fhir.org/web/fhir.ca.template-0.2.0.tgz","date":"2022-09-16T18:00:59.000Z","description":"HL7 Canada Template - for use with HL7 Canada-published FHIR IGs"},{"name":"nictiz.fhir.nl.stu3.images","version":"1.0.3","fhirVersion":"3.0.1","canonical":"http://simplifier.net/packages/nictiz.fhir.nl.stu3.images","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nictiz.fhir.nl.stu3.images-1.0.3.tgz","date":"2022-09-26T14:48:24.000Z","description":"Nictiz NL package of FHIR STU3 conformance resources for Images."},{"name":"nictiz.fhir.nl.stu3.eafspraak","version":"1.0.6","fhirVersion":"3.0.1","canonical":"http://simplifier.net/packages/nictiz.fhir.nl.stu3.eafspraak","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nictiz.fhir.nl.stu3.eafspraak-1.0.6.tgz","date":"2022-09-26T14:50:25.000Z","description":"Nictiz NL package of FHIR STU3 conformance resources for eAfspraak."},{"name":"nictiz.fhir.nl.stu3.questionnaires","version":"2.0.8","fhirVersion":"3.0.1","canonical":"http://simplifier.net/packages/nictiz.fhir.nl.stu3.questionnaires","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nictiz.fhir.nl.stu3.questionnaires-2.0.8.tgz","date":"2022-09-26T14:53:21.000Z","description":"Nictiz NL package of FHIR STU3 conformance resources for MedMij information standard Questionnaires. Includes dependency on Zib2017 and SDC.\\n\\nHCIMs: https://zibs.nl/wiki/HCIM_Release_2017(EN)"},{"name":"hl7.fhir.us.exchange-routing","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/exchange-routing","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.exchange-routing-1.0.0.tgz","date":"2022-09-26T18:00:10.000Z","description":"This FHIR implementation Guide describes the health care standard for HTTP exchange in a hybrid model of both point to point communication and intermediary. (built Mon, Sep 26, 2022 17:04+0000+00:00)"},{"name":"hl7.fhir.us.vitals","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/vitals","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.vitals-1.0.0.tgz","date":"2022-09-26T18:00:14.000Z","description":"This IG describes vital signs observations that include qualifying information such as cuff size for blood pressure, or an associated situation of \"during exercise\" for blood pressure or heart rate, etc. (built Mon, Sep 12, 2022 00:44+0000+00:00)"},{"name":"hl7.fhir.us.pacio-rt","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/pacio-rt","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.pacio-rt-1.0.0.tgz","date":"2022-09-28T18:00:11.000Z","description":"PACIO Re-Assessment Timepoints Implementation Guide (built Wed, Sep 28, 2022 16:27+0000+00:00)"},{"name":"star.rhecord.beta","version":"0.0.3-beta","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/star.rhecord.beta","kind":"fhir.ig","url":"https://packages2.fhir.org/web/star.rhecord.beta-0.0.3-beta.tgz","date":"2022-09-29T14:10:39.000Z","description":"Medizinische Inofmrationsobjekte (MIO) Rhecord"},{"name":"colonoscopyreport.no","version":"0.7.23","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/colonoscopyreport.no","kind":"fhir.ig","url":"https://packages2.fhir.org/web/colonoscopyreport.no-0.7.23.tgz","date":"2022-10-11T20:35:28.000Z","description":"Sending colonoscopy data for cancer screening to a central registry in Norway"},{"name":"ishmed.i14y.r4.de","version":"3.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ishmed.i14y.r4.de","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ishmed.i14y.r4.de-3.0.0.tgz","date":"2022-10-17T09:10:28.000Z","description":"i.s.h.med FHIR R4 Germany API Endpoint"},{"name":"ishmed.i14y.r4.de","version":"3.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ishmed.i14y.r4.de","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ishmed.i14y.r4.de-3.0.0.tgz","date":"2022-10-17T09:10:28.000Z","description":"i.s.h.med FHIR R4 Germany API Endpoint"},{"name":"duwel.nl.stu3.sandbox.dev","version":"0.0.1-dev.5","fhirVersion":"3.0.1","canonical":"http://simplifier.net/packages/duwel.nl.stu3.sandbox.dev","kind":"fhir.ig","url":"https://packages2.fhir.org/web/duwel.nl.stu3.sandbox.dev-0.0.1-dev.5.tgz","date":"2022-10-24T15:03:16.000Z","description":"Jorn Duwel sandbox"},{"name":"duwel.nl.stu3.sandbox.dev","version":"0.0.1-dev.5","fhirVersion":"3.0.1","canonical":"http://simplifier.net/packages/duwel.nl.stu3.sandbox.dev","kind":"fhir.ig","url":"https://packages2.fhir.org/web/duwel.nl.stu3.sandbox.dev-0.0.1-dev.5.tgz","date":"2022-10-24T15:03:16.000Z","description":"Jorn Duwel sandbox"},{"name":"ntt.healthgenig","version":"0.0.4","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ntt.healthgenig","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ntt.healthgenig-0.0.4.tgz","date":"2022-11-01T05:31:28.000Z","description":"Healthgen IG"},{"name":"jp-core.r4","version":"1.1.1-rc","fhirVersion":"4.0.1","canonical":"http://jpfhir.jp/fhir/core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/jp-core.r4-1.1.1-rc.tgz","date":"2022-11-03T20:39:47.000Z","description":"JP-CORE V1.1.1-rc for release candidate of V1.1.1 2022/11/03\r\n"},{"name":"jp-core.r4","version":"1.1.1-rc","fhirVersion":"4.0.1","canonical":"http://jpfhir.jp/fhir/core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/jp-core.r4-1.1.1-rc.tgz","date":"2022-11-03T20:39:47.000Z","description":"JP-CORE V1.1.1-rc for release candidate of V1.1.1 2022/11/03\r\n"},{"name":"nictiz.fhir.nl.stu3.iwlz","version":"1.0.0-poc8","fhirVersion":"3.0.1","canonical":"http://simplifier.net/packages/nictiz.fhir.nl.stu3.iwlz","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nictiz.fhir.nl.stu3.iwlz-1.0.0-poc8.tgz","date":"2022-11-04T16:06:41.000Z","description":"NL package of FHIR STU3 conformance resources for iWlz."},{"name":"nictiz.fhir.nl.stu3.iwlz","version":"1.0.0-poc8","fhirVersion":"3.0.1","canonical":"http://simplifier.net/packages/nictiz.fhir.nl.stu3.iwlz","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nictiz.fhir.nl.stu3.iwlz-1.0.0-poc8.tgz","date":"2022-11-04T16:06:41.000Z","description":"NL package of FHIR STU3 conformance resources for iWlz."},{"name":"dvmd.kdl.r4.2022","version":"2022.1.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/dvmd.kdl.r4.2022","kind":"fhir.ig","url":"https://packages2.fhir.org/web/dvmd.kdl.r4.2022-2022.1.2.tgz","date":"2022-11-09T09:52:41.000Z","description":"Publikation der Terminologie-Ressourcen für die Nutzung der Klinische Dokumentenklassen-Liste (KDL) des DVMD\r\nVersion 2022"},{"name":"rki.demis.statistic","version":"1.0.0","fhirVersion":"4.0.1","canonical":"https://demis.rki.de/fhir/statistic","kind":"fhir.ig","url":"https://packages2.fhir.org/web/rki.demis.statistic-1.0.0.tgz","date":"2022-11-10T10:15:40.000Z","description":"Beinhaltet die in DEMIS für die Umsetzung verschiedener statistischer Erhebungen genutzten Informationsmodellartefakte"},{"name":"kbv.ita.aws","version":"1.2.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/kbv.ita.aws","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kbv.ita.aws-1.2.0.tgz","date":"2022-11-10T13:04:59.000Z","description":"PVS-Archivierungs- und Wechsel-Schnittstelle Gemäß § 371 Absatz 1"},{"name":"de.gevko.emdaf","version":"1.3.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gevko.emdaf","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gevko.emdaf-1.3.0.tgz","date":"2022-11-17T14:18:35.000Z","description":"elektronisches Medikations-Datenaustauschformat"},{"name":"hl7.fhir.cl.corecl","version":"1.7.0","fhirVersion":"4.0.1","canonical":"https://hl7chile.cl/fhir/ig/CoreCL","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.cl.corecl-1.7.0.tgz","date":"2022-11-18T00:00:27.000Z","description":"Guía de Implementación Versión de Desarrollo Sobre STU 1, para los perfiles Core que se van a requerir a nivel de desarrollo Nacional para Sistemas que Intercambien datos en estandar FHIR-R4 (built Tue, Sep 6, 2022 11:46-0300-03:00)"},{"name":"hl7.fhir.us.breast-radiology","version":"0.2.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/breast-radiology","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.breast-radiology-0.2.0.tgz","date":"2022-11-22T00:00:08.000Z","description":"Breast Radiology Reporting Implementation Guide (built Tue, Apr 7, 2020 16:39+0000+00:00)"},{"name":"nat.testproject","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/nat.testproject","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nat.testproject-1.0.0.tgz","date":"2022-11-22T04:12:47.000Z","description":"nat_testproject"},{"name":"ca.learning-forge-v3.r4","version":"3.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.learning-forge-v3.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.learning-forge-v3.r4-3.0.0.tgz","date":"2022-11-28T21:35:41.000Z","description":"creating a new release"},{"name":"hl7.fhir.uv.pddi","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/pddi","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.pddi-1.0.0-ballot.tgz","date":"2022-12-07T18:00:16.000Z"},{"name":"hl7.fhir.stt","version":"1.0.0-beta14","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/hl7.fhir.stt","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.stt-1.0.0-beta14.tgz","date":"2022-12-08T17:12:04.000Z","description":"Sistema Integrado de Telemedicina e Telessaúde - Universidade Federal de Santa Catarina"},{"name":"acme.canada","version":"0.0.4","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/acme.canada","kind":"fhir.ig","url":"https://packages2.fhir.org/web/acme.canada-0.0.4.tgz","date":"2022-12-16T19:34:57.000Z","description":"This is a demonstration project for FHIR North"},{"name":"progetto.eng","version":"0.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/progetto.eng","kind":"fhir.ig","url":"https://packages2.fhir.org/web/progetto.eng-0.0.1.tgz","date":"2022-12-19T17:08:06.000Z","description":"prova_silvia"},{"name":"nictiz.fhir.nl.r4.vaccinationimmunization","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/nictiz.fhir.nl.r4.vaccinationimmunization","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nictiz.fhir.nl.r4.vaccinationimmunization-1.0.0.tgz","date":"2022-12-20T09:22:56.000Z","description":"NL package of FHIR R4 conformance resources for Vaccination-Immunization."},{"name":"kbv.mio.ueberleitungsbogen","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/kbv.mio.ueberleitungsbogen","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kbv.mio.ueberleitungsbogen-1.0.0.tgz","date":"2022-12-21T12:26:38.000Z","description":"Pflegerisches Informationsobjekt (PIO) Überleitungsbogen V1.0.0"},{"name":"uk.nhsdigital.medicines.r4","version":"2.7.9","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/uk.nhsdigital.medicines.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/uk.nhsdigital.medicines.r4-2.7.9.tgz","date":"2023-01-10T15:13:14.000Z","description":"Electronic Prescription Service"},{"name":"apo.cdl.test","version":"0.0.1-alpha","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/apo.cdl.test","kind":"fhir.ig","url":"https://packages2.fhir.org/web/apo.cdl.test-0.0.1-alpha.tgz","date":"2023-01-12T16:27:40.000Z","description":"Test IG Kereval"},{"name":"nhsdigital.fhir.stu3","version":"1.3.0","fhirVersion":"3.0.1","canonical":"http://simplifier.net/packages/nhsdigital.fhir.stu3","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nhsdigital.fhir.stu3-1.3.0.tgz","date":"2023-01-27T14:04:52.000Z","description":"For testing and evaluation purposes"},{"name":"ufp.core","version":"0.6.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ufp.core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ufp.core-0.6.0.tgz","date":"2023-01-30T12:50:00.000Z","description":"The United Federation of Planet (UFP) FHIR Implementation Guide of intergalactic scope"},{"name":"de.gematik.isip","version":"1.0.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gematik.isip","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.isip-1.0.2.tgz","date":"2023-01-31T17:32:24.000Z","description":"Package Release des ISIP Basis Modul"},{"name":"tiga.health.clinical","version":"1.1.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/tiga.health.clinical","kind":"fhir.ig","url":"https://packages2.fhir.org/web/tiga.health.clinical-1.1.0.tgz","date":"2023-02-02T11:51:51.000Z","description":"tiga-health-clinical"},{"name":"fhir.r4.ukcore.stu1","version":"1.0.4","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.r4.ukcore.stu1","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.r4.ukcore.stu1-1.0.4.tgz","date":"2023-02-02T13:19:30.000Z","description":"UK Core FHIR profiles and assets for the IG 1.0.0."},{"name":"kbv.mio.diga","version":"1.1.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/kbv.mio.diga","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kbv.mio.diga-1.1.0.tgz","date":"2023-02-10T14:55:52.000Z","description":"Medizinische Informationsobjekte (MIO) DiGA Toolkit V1.1.0"},{"name":"de.bbmri.fhir","version":"1.2.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.bbmri.fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.bbmri.fhir-1.2.0.tgz","date":"2023-03-07T13:08:57.000Z","description":"Profiles for the BBMRI.de / GBA biobanking project."},{"name":"iteyes.myhw.core","version":"1.1.9","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/iteyes.myhw.core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/iteyes.myhw.core-1.1.9.tgz","date":"2023-03-09T05:23:26.000Z","description":"마이헬스웨이 FHIR Resource Profiles"},{"name":"sfm.130323","version":"3.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/sfm.130323","kind":"fhir.ig","url":"https://packages2.fhir.org/web/sfm.130323-3.0.1.tgz","date":"2023-03-13T12:48:04.000Z","description":"Medication related projects (SFM, PLL, SAFEST, KIKJ)"},{"name":"egde.health.gateway","version":"0.1.7","fhirVersion":"4.0.1","canonical":"http://www.egde.no","kind":"fhir.ig","url":"https://packages2.fhir.org/web/egde.health.gateway-0.1.7.tgz","date":"2023-03-24T13:28:35.000Z","description":"Egde Health Gateway FHIR facade"},{"name":"fdpg.query_profiles","version":"0.0.6-alpha","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fdpg.query_profiles","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fdpg.query_profiles-0.0.6-alpha.tgz","date":"2023-03-24T16:55:06.000Z","description":"Based on the MII core data set these profiles enforce further restrictions for the FDPG"},{"name":"hl7.fhir.us.odh","version":"1.3.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/odh","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.odh-1.3.0.tgz","date":"2023-03-27T12:00:00.000Z","description":"**HL7 FHIR Profile: Occupational Data for Health (ODH), Release 1.3 (Standard for Trial Use)**\n\nThis Implementation Guide is a reconciled version, containing changes in response to comments received in the Sept. 2018 ballot. It has been updated to FHIR R4.0.1.\n\n**Introduction and Guidance**\n\nThis Implementation Guide (IG) contains profiles to implement support for Occupational Data for Health (ODH). ODH describes structured work information primarily designed to facilitate clinical care, including population health and value-based care. ODH also can be used to support public health reporting. ODH is not designed to support billing activities. \nThis set of FHIR profiles is specified as a composition resource, but it is not intended to be used as a stand-alone composition. Rather, the desired content should be included in broader IGs and available as a response to requests for ODH information. Some use cases may leverage only a subset of the ODH profiles, and these should be specified within those work products. For instance, in the Vital Records Death Reporting (VRDR) IG, the data requirements for work information are limited to those in the Usual Work profile.\nWhile this profile is specified for the US Realm, the design is intended to also support international needs. Three of the referenced value sets—Occupation, Industry, and Supervisory Level— are necessarily US specific. The remaining three value sets—Work Schedule, Employment Status, and Work Classification—use international concepts. Input is requested regarding whether these should be specified as ‘extensible’, ‘required’ (using ‘text only’ where a concept does not yet exist such as a new occupation), or as an ‘example’ for those US specific concepts.\n\n**Background**\n\nThe majority of adults in the U.S. spend more than half their waking hours at work. Therefore, health and work are inextricably inter-related. For example, the management of chronic conditions requires taking the patient’s work environment into consideration. Work-related conditions are often first brought to the attention of a primary care provider. Some conditions related to exposure to hazards in the workplace can have a long latency, requiring knowledge of a person’s work history for recognition, diagnosis, and treatment. The recognition of new conditions related to previously unknown workplace hazards has often come from astute clinicians, which requires knowledge of the patient’s work. ONC has indicated recognition of the value of work information for health care.\nThe incorporation of ODH into Electronic Health Records (EHRs) and other health IT systems presents an opportunity to improve health in relation to work. ODH provides a structure and standardization for work information that can be used across systems to take advantage of system tools for clinical decision support, population health, and public health. Research has been conducted and guidance is available to support clinicians, and the use of ODH by health IT systems can support identification of patients that would benefit the most from this knowledge.\n\n**Scope**\n\nThe Occupational Data for Health (ODH) FHIR IG covers information about a patient’s work, including some voluntary work, or a patient’s household members’ work. ODH is designed for the social history section of a medical record, to facilitate clinical care in multiple disciplines and delivery environments. ODH can be used for clinical decision support, population health activities and value-based care, and public health reporting. The scope of the work information in ODH includes:\n\n• Employment Status\n\n• Retirement Date\n\n• Combat Zone Period\n\n• Past or Present Job for the patient or a household member, which includes:\n \n o Past or Present Job Occupation\n \n o Past or Present Job Industry\n \n o Work Classification\n \n o Work Schedule, which includes:\n \n - Weekly Work Days\n \n - Daily Work Hours\n \n o Job Duty\n \n o Occupational Hazard\n \n o Employer name\n \n o Employer address\n \n o Related Subject (when it is Past or Present Job of a household member of the person)\n \n o Start/End Dates\n\n• Usual Work of the patient or a household member, which includes:\n \n o Usual Occupation\n \n o Usual Industry\n \n o Usual Occupation Duration\n \n o Related Subject (when it is Usual Work of a household member of the person)\n \n o Start Date\n\n**Known Issues and Limitations**\n\nThis IG includes more extensive occupational data than typically collected in current systems. The content and structure of this IG is intended to inform clinical care, support population health, and contribute to public health activities. While there may be some overlap with administrative and billing information maintained by some systems, the information in this IG is not designed to support billing and administrative needs.\nWhile multiple retirement dates are supported, the retirement date is not linked to any specific job, or usual occupation.\n\n**Credits**\n\nCo-Editor:\nLori Reed-Fourquet\ne-HealthSign, LLC\nlfourquet@ehealthsign.com\n\nCo-Editor:\nRob Hausam\nHausam Consulting\nrob@hausamconsulting.com\n\nCo-Editor:\nMark Kramer\nMITRE Corporation\nmkramer@mitre.org\n\nThis set of FHIR profiles was produced and developed through the efforts of a project of the National Institute of Occupational Safety and Health (NIOSH), the U.S. federal agency responsible for conducting research and making recommendations for the prevention of work-related injury and illness. NIOSH is a part of the U.S. Centers for Disease Control and Prevention (CDC). NIOSH consulted stakeholders in clinical care, public health, health IT, health informatics and U.S. government agencies to develop ODH. The HL7® Public Health and Emergency Response Work Group sponsored development of this set of FHIR profiles. Co-sponsoring HL7® Work Groups were Orders and Observations (OO), Patient Administration (PA), and Clinical Quality Initiative (CQI).\nThe following individuals provided subject matter expertise for this set of FHIR profiles: Genevieve Barkocy Luensman, NIOSH; Eileen Storey, Professional Services Partners, formerly NIOSH; Margaret S. Filios, NIOSH; Christina Socias-Morales, NIOSH; Lauren Brewer, NIOSH; Barbara Wallace, Professional Services Partners.\n\n**Authors**\n\nName Email/URL\nHL7 International - Public Health http://www.hl7.org/Special/committees/pher (built Mon, Mar 27, 2023 09:54+1100+11:00)"},{"name":"nictiz.fhir.nl.r4.patientcorrections","version":"1.0.6","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/nictiz.fhir.nl.r4.patientcorrections","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nictiz.fhir.nl.r4.patientcorrections-1.0.6.tgz","date":"2023-03-28T08:17:02.000Z","description":"NL package of FHIR R4 conformance resources for Patient Corrections."},{"name":"hl7.fhir.r4b.core","version":"4.3.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.r4b.core-4.3.0.tgz","date":"2023-03-29T10:54:41.000Z","description":"FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (built Sat, May 28, 2022 12:47+1000+10:00)"},{"name":"hl7.fhir.r4b.corexml","version":"4.3.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.r4b.corexml-4.3.0.tgz","date":"2023-03-29T10:54:52.000Z","description":"FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (XML) (built Sat, May 28, 2022 12:47+1000+10:00)"},{"name":"hl7.fhir.r4b.elements","version":"4.3.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.r4b.elements-4.3.0.tgz","date":"2023-03-29T10:54:53.000Z","description":"Element Definitions for types defined in the R4B version of the FHIR standard"},{"name":"hl7.fhir.r4b.examples","version":"4.3.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.r4b.examples-4.3.0.tgz","date":"2023-03-29T10:55:08.000Z","description":"Example resources in the R4B version of the FHIR standard"},{"name":"hl7.fhir.r4b.expansions","version":"4.3.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.r4b.expansions-4.3.0.tgz","date":"2023-03-29T10:55:17.000Z","description":"Expansions for the 4.3.0 version of the FHIR standard (built Sat, May 28, 2022 12:47+1000+10:00)"},{"name":"hl7.fhir.us.mihr","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/mihr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.mihr-1.0.0.tgz","date":"2023-03-30T00:00:29.000Z","description":"### Scope\nThe Longitudinal Maternal & Child Health Information for Research FHIR R4 implementation guide (IG) defines a framework to enable maternal health researchers to aggregate, calculate, and analyze clinical information of research populations to explore the root causes for maternal and child morbidity and mortality. It uses Clinical Quality Language (CQL) expressions to assist researchers in capturing clinical data based on population study cohort criteria. This IG focuses on information relevant to longitudinal maternal care, which includes antepartum (including pre-pregnancy), intrapartum, and postpartum care of a pregnant woman. It includes how to link maternal longitudinal record with associated child/children records. \n\nThis US Realm IG supports the use of US Core profiles where possible, as well as base FHIR and Vital Records Common Profiles FHIR IG data model for the structural linkage of mother and child clinical records. \n\n\n### Background\nThe rates of maternal mortality have been rising in the United States since 1987. Clinical data relevant to understanding this trend are not standardized, and data exchange is not interoperable across many relevant settings. Maternal health and associated child health are inextricably linked – what happens during gestation, delivery, and after informs health outcomes of both mother and child – but relevant data is often held in separate, unconnected records. These issues impede research on maternal morbidity and longitudinal maternal care and associated impacts to infant health. Research on root causes of maternal mortality, pediatric developmental problems, and effective treatments requires exchange of information stored in disparate sources, such as electronic health record (EHR) systems, registries, and public health agencies (PHAs).\n\nThe types of information needed to research maternal health and morbidity include social determinants of health (SDOH) and associated clinical data such as antepartum, intrapartum, and postpartum care of a pregnant woman; pregnancy-related conditions and outcomes; maternal co-morbidities; child health data; and procedures. The goal of this FHIR IG is to define a model to support data exchange for predictive analysis, risk assessment, and retrospective maternal health research across the spectrum and duration of care. \n\nFuture users may include health departments using EHR data to inform public health interventions (e.g., case identification for reportable conditions, identifying persons lost to care, etc.) and maternal and child health researchers. The standards development effort will also examine options for data exchange mechanisms, including point-in-time query (data pull) and research population creation, i.e., patient enrollment in a study.\n\n### Maternal Research Use Cases\n\nThis IG will eventually support mapping maternal data across health records from specialty care and linking mother and child data harmonized across a broad set of use cases. This will support researchers in identifying root causes of maternal mortality and pediatric developmental problems, including SDOH such as limited income, poor nutrition, lack of medical coverage, etc. The goal of the project is to create a method to standardize data capture for comparative analysis over time to improve health outcomes and define a framework for studying additional research populations in the future.\n\nInitial use cases of this IG focus on hypertensive disorders of pregnancy pre, ante, and postpartum and pregnancy and subsequent death within a specific timeframe. The intent is to specify the consistent capture of clinical data of interest to maternal health researchers and outline implementing FHIR resources for that capture. Currently, the IG defines two initial, separate research use case populations: \n\n* Pregnancy and subsequent death within a specific time frame: This cohort includes women who died within a year (365 days) of a pregnancy regardless of cause of death or pregnancy outcome.\n* Hypertensive Disorders of pregnancy: This use case focuses on women with a diagnosis of hypertensive disorders of pregnancy.\n\nIn both instances, the IG will establish linkages via the US Core Related Person profile to collect associated child health data that may inform maternal health research outcomes. \n\nIn the future, the IG will expand this framework to a range of use cases including:\n* Risks for children related to maternal exposure to medications taken during pregnancy\n* Potential adverse maternal obstetric history impacts on child outcomes\n* Access to relevant sensitive health information\n* Retrospective population-based analysis of inherited disorders\n* The impacts of [work habits, work environment, and work-associated health insurance](http://hl7.org/fhir/us/odh/) impacts to pregnancy and maternal health\n\nThis guide fundamentally relies on creating structural relationships between:\n* Maternal and child records to effectively diagnose and treat otherwise fatal child outcomes\n* Maternal and child birth records and/or maternal and child death records\n* Maternal and child records in multiple disparate systems\n\n### Audience \nThe audience for this IG includes EHR vendors, developers of software tooling researchers, and associated information management systems. Researchers, business analysts, and policy managers can also benefit from a basic understanding of the use of this guide to support measure calculation for research purposes.\n\n### Authors & Project Team\nThis table lists the authors, subject matter experts, and the affiliations which contributed to this standard. \n\n\n\n\n \n \n \n \n \n\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\n
Name & AffiliationRoleContact
Lantana Consulting Group
Courtney Panaia-Rodi Project Executivecourtney.panaia-rodi@lantanagroup.com
Wendy WiseProject Managerwendy.wise@lantanagroup.com
Lani JohnsonAssociate Project Managerlani.johnson@lantanagroup.com
Rick GeimerFHIR Subject Matter Expertrick.geimer@lantanagroup.com
Zabrina GonzagaTerminology Subject Matter Expertzabrina.gonzaga@lantanagroup.com
Sarah GauntSenior FHIR/CDA Analystsarah.gaunt@lantanagroup.com
Dave deRoodeFHIR/CDA Analystdavid.deroode@lantanagroup.com
Ming DunajickFHIR/CDA Analystming.dunajick@lantanagroup.com
Ruby NashFHIR Analystruby.nash@lantanagroup.com
Office of the Assistant Secretary for Planning and Evaluation (ASPE)
Violanda Grigorescu, MD, MSPHSenior Health Scientist
Division of Healthcare Quality and Outcomes, Office of Health Policy		violanda.grigorescu@hhs.gov
Centers for Disease Control and Prevention (CDC)
Margaret Lampe, RN, MPHNurse Epidemiologist & Project Officer
Perinatal HIV Prevention Program		mol0@cdc.gov
Lisa Romero, DrPHHealth Scientist
Division of Adolescent School Health		eon1@cdc.gov
National Institutes of Health (NIH)
Eunice Kennedy Shriver National Institute of Child Health and Human Development (NICHD)
National Information Center on Health Services Research and Health Care Technology (NICHSR)
Alison CernichNICHD Deputy Directoralison.cernich@nih.hhs.gov
John (Jack) Moye, Jr., MDActing Director - National Children's Study
NICHD Medical Officer - Maternal & Pediatric Infectious Disease Branch		moyej@exchange.nih.gov
Nahida Chakhtoura, MD, MsGHNICHD Medical Officer
Maternal and Pediatric Infectious Disease Branch		nahida.chakhtoura@nih.gov
Juanita Chinn, PhDNICHD Program Director
Population Dynamics Branch		juanita.chinn@nih.gov
Valerie CottonNICHD Deputy Director
Office of Data Science and Sharing		valerie.cotton@nih.gov
Liz Amos, MLISSpecial Assistant to the Chief Health Data Standards Officer
National Library of Medicine		liz.amos@nih.gov
Office of the National Coordinator for Health IT (ONC)
Carmen SmileyIT Specialist (Systems Analysis)carmen.smiley@hhs.gov
Rachel AbbeyPublic Health Analyst & Program Officerrachel.abbey@hhs.gov
Stephanie GarciaSenior Program Analyststephanie.garcia@hhs.gov
Brittney Boakye, MPHProgram Assistant
Scientific Advancement Branch		brittney.boakye@hhs.gov
Alan TaylorMedical Informatics Officer, Standards and Terminologyalbert.taylor@hhs.gov
\n\n### Acknowledgements\nThis guide was developed and produced through the efforts of Health Level Seven (HL7) and created using the Trifolia-on-FHIR tool, provided by Lantana Consulting Group. The HL7 Project Insight reference number for this project is 1736.\nThe editors appreciate the support and sponsorship of the HL7 Public Health Workgroup, and all volunteers and staff associated with the creation of this document. This guide would not have been possible without the support of the following groups.\nHealth Level Seven, HL7, CDA, CCD, FHIR and the [FLAME DESIGN] are registered trademarks of Health Level Seven International, registered in the US Trademark Office.\n\nThis IG includes content from SNOMED CT, which is copyright © 2002+ International Health Terminology Standards Development Organisation (IHTSDO), and distributed by agreement between IHTSDO and HL7. Implementer use of SNOMED CT is not covered by this agreement.\n\nThis material contains content from [LOINC](http://loinc.org). LOINC is copyright © 1995-2021, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license at https://loinc.org/kb/license/. LOINC® is a registered United States trademark of Regenstrief Institute, Inc. (built Wed, Mar 29, 2023 19:24+0000+00:00)"},{"name":"fi.digious.kanta.test","version":"0.0.1-preview-2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fi.digious.kanta.test","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fi.digious.kanta.test-0.0.1-preview-2.tgz","date":"2023-04-05T13:54:50.000Z","description":"Profiles for integrating into various EHR systems, mainly Finnish Kanta"},{"name":"questinnaire.profiles","version":"0.0.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/questinnaire.profiles","kind":"fhir.ig","url":"https://packages2.fhir.org/web/questinnaire.profiles-0.0.2.tgz","date":"2023-04-12T16:21:39.000Z","description":"Test Profiles for Questionnaire App"},{"name":"hl7.fhir.uv.security-label-ds4p","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/security-label-ds4p","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.security-label-ds4p-1.0.0.tgz","date":"2023-04-18T00:00:28.000Z","description":"FHIR data segmentation for privacy security label implementation guide (built Mon, Apr 17, 2023 19:19+0000+00:00)"},{"name":"hl7.fhir.uv.vulcan-schedule","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/vulcan-schedule","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.vulcan-schedule-1.0.0.tgz","date":"2023-04-18T18:00:26.000Z","description":"FHIR Implementation Guide representing a Clinical Study Schedule of Activities (built Tue, Apr 18, 2023 16:34+0000+00:00)"},{"name":"hl7.fhir.us.hai-ltcf","version":"1.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/hai-ltcf","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.hai-ltcf-1.1.0.tgz","date":"2023-04-19T18:00:24.000Z","description":"This implementation guide (IG) specifies standards for electronic submission of Healthcare Associated Infection (HAI) Long Term Care Facilities (LTCF) reports to the National Healthcare Safety Network (NHSN) of the Centers for Disease Control and Prevention (CDC). This IG contains a library of FHIR profiles for electronic submission of HAI LTCF reports to the NHSN.\n\nAs reports are modified and new report types are defined, CDC and Health Level Seven (HL7) will develop and publish additional constraints.\n\nThroughout this process, CDC remains the authority on NHSN data collection protocols. When healthcare enterprises choose to participate in NHSN, they must report to CDC reportable events such as identified MDRO (multidrug-resistant organism) or CDI (C. difficile infection) occurrences such as specific reportable procedures, even those without complications, and events such as a bloodstream infection, either confirmed by a positive blood culture or supported by a patients clinical symptoms. This specification opens the channel for data submission by all applications compliant with the data coding requirements defined here.\n\nNote that participation in the NHSN requires enrollment and filing of reporting plans, which are not defined by this specification. For an overview of NHSN and full information on NHSN participation requirements, see: [http://www.cdc.gov/nhsn](http://www.cdc.gov/nhsn). Provisions of the Public Health Service Act protect all data reported to NHSN from discovery through the Freedom of Information Act (FOIA).\n\n\n### Relationship to Another Standard\n\nHL7 has developed this FHIR implementation guide in parallel with the CDA implementation guide. We anticipate several STU releases on the path to a Normative Release 1 of the HL7 implementation guides for CDA and FHIR for Healthcare Associated Infection (HAI) Reports from Long Term Care Facilities (LTCF). The FHIR and CDA implementation guides will align. A change to one standard will require the same change in the other standard. \n\nIn this release, the new forms included in both the CDA and FHIR standards are:\n* **NHSN HAI LTCF Population Summary Report**: MDRO and CDI LabID Event Reporting Monthly Summary Data for LTCF\n* **NHSN HAI LTCF Single-Person Event Report**: Laboratory-identified MDRO or CDI Event for LTCF\n\nFor further details see the [NHSN website](https://www.cdc.gov/nhsn/) for reporting healthcare-associated infections in long-term care facilities.\n\n\n### Audience\n\nThe audience for this work is all developers of software systems who want to enable their systems for reporting HAI data to the NHSN.\n\n### Change Notification Process\n\nCDC maintains an e-mail list of contacts at organizations interested in or responsible for implementations of FHIR for LTCF HAI reporting to NHSN. To be added to the list, send a request with your contact information to nhsncda@cdc.gov. CDC uses the list for e-mail notifications of changes, including new data requirements. Changes may apply to this IG and to other documents such as business rules that are needed to implement and support FHIR for LTCF HAI reporting to NHSN. NHSN CDA related information may be found at https://www.cdc.gov/nhsn/cdaportal/index.html. \n\n### Acknowledgements\n\nThis implementation guide was produced and developed by Lantana Consulting Group in conjunction with the Division of Healthcare Quality Promotion in the National Center for Emerging and Zoonotic Infectious Diseases (NCEZID) at the Centers for Disease Control and Prevention (CDC). Its development and deployment are results of the dedication of the team—led by Daniel A. Pollock, M.D., Surveillance Branch Chief, Division of Healthcare Quality Promotion, NCEZID, CDC and Jeneita Bell, MD, MPH, Long-term Care Team Lead, DHQP, NCEZID, CDC—and their support of the development of interoperable data standards for the CDC’s National Healthcare Safety Network (NHSN). \n\nSpecial thanks and acknowledgment to stakeholders who participated in calls and provided feedback. Specifically, we would like to thank Cindy Frakes, Steve Herron, Jamie Gatzke, Kelly Luden, Prasath Govindarajulu from Cerner; Laura Ditz, Nancy Chi, Nichole (Nicki) Fetterman, Michael Furman, Patti Barton, Aga Lee from Point Click Care; Donna Doneski from NASL; and Denise Wassenaar, Doc DeVore, Rob Price from Matrix Care. \n\nThe best standards are those driven by business requirements. A strong set of Healthcare Associated Infection (HAI) surveillance application vendors monitor, evaluate, and test each release of this guide. \n\n\n|-----|-----|-----|-----| \n\n|Primary Editor:|Sarah Gaunt|Lantana Consulting Group|sarah.gaunt@lantanagroup.com| \n|Primary Editor:|Zabrina Gonzaga|Lantana Consulting Group|zabrina.gonzaga@lantanagroup.com| \n|Primary Editor:|Dave deRoode|Lantana Consulting Group|david.deroode@lantanagroup.com| \n|Co-Editor:|Jeneita Bell, MD, MPH|CDC|hpq8@cdc.gov| \n|Co-Editor:|Angella Antilla PhD, MSN|CDC|vtb9@cdc.gov| \n|Co-Editor:|Daniel Pollock, M.D.|CDC|DPollock@cdc.gov| \n|Co-Editor:|Ahmed Tahir|Leidos Consultant to CDC/NHSN|nmn8@cdc.gov| \n|Co-Editor:|Mindy Durrance|Leidos Consultant to CDC/NHSN|mdq1@cdc.gov| \n|Co-Editor:|Sheri Chernetsky Tejedor, MD|CDC|yei9@cdc.gov| \n|Co-Editor:|Sheila Abner|CDC|sha8@cdc.gov| \n|Co-Chair:|Erin Holt MPH|Tennessee Department of Health|erin.holt@tn.gov| \n|Co-Chair:|Laura Rappleye|Altarum|laura.rappleye@altarum.org| \n|Co-Chair:|Craig Newman|Altarum|craig.newman@altarum.org| \n|Co-Chair:|Danny Wise|Allscripts|danny.wise@allscripts.com| \n|Co-Chair:|Joginder Madra|Madra Consulting Inc.|hl7@madraconsulting.com| \n|Co-Chair:|Gaye Dolin M.S.N., R.N. |Intelligent Medical Objects |gdolin@imo-online.com| \n|Co-Chair:|Calvin Beebe|Mayo Clinic|cbeebe@mayo.edu| \n|Co-Chair:|Austin Kreisler|Leidos Consultant to CDC/NHSN|duz1@cdc.gov| \n|Co-Chair:|Andrew Statler|Cerner Corp|andrew.statler@cerner.com| \n|Co-Chair:|Sean McIlvenna| Lantana Consulting Group|sean.mcilvenna@lantanagroup.com| \n|Co-Chair:|Benjamin Flessner|Redox|benjamin@redoxengine.com| \n|Co-Editor:|Beau Bannerman|Lantana Consulting Group|beau.bannerman@lantanagroup.com| \n|Technical Editor:|Diana Wright|Lantana Consulting Group|diana.wright@lantanagroup.com| \n|Technical Editor:|Chris Hannigan|Lantana Consulting Group|chris.hannigan@lantanagroup.com| \n (built Wed, Apr 19, 2023 14:58+0000+00:00)"},{"name":"hl7.fhir.us.sirb","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/sirb","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.sirb-1.0.0.tgz","date":"2023-04-20T18:00:24.000Z","description":"Data standards to move data and documents from clinical research sites to a single ethics review board in support of the \"NIH Policy on the Use of a Single Institutional Review Board for Multi-Site Research. (built Thu, Apr 20, 2023 13:43+0000+00:00)"},{"name":"myhealthway.main.r4","version":"0.0.12-beta","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/myhealthway.main.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/myhealthway.main.r4-0.0.12-beta.tgz","date":"2023-04-25T00:58:24.000Z","description":"마이헬스웨이 상세규격"},{"name":"sbu_test.r4","version":"0.0.3-alpha","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/sbu_test.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/sbu_test.r4-0.0.3-alpha.tgz","date":"2023-04-25T15:44:51.000Z","description":"Test for branching"},{"name":"fhir.r4.wales.discovery","version":"0.0.5","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.r4.wales.discovery","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.r4.wales.discovery-0.0.5.tgz","date":"2023-04-27T09:53:50.000Z","description":"HL7 FHIR® NHS Wales Draft Data Standards for R4"},{"name":"mein.test.de","version":"0.0.1-alpha","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/mein.test.de","kind":"fhir.ig","url":"https://packages2.fhir.org/web/mein.test.de-0.0.1-alpha.tgz","date":"2023-04-28T06:12:25.000Z","description":"xxx"},{"name":"hl7.fhir.r5.core","version":"5.0.0","fhirVersion":"5.0.0","canonical":"http://hl7.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.r5.core-5.0.0.tgz","date":"2023-05-03T09:45:18.000Z","description":"FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (built Sun, Mar 26, 2023 15:21+1100+11:00)"},{"name":"hl7.fhir.r5.examples","version":"5.0.0","fhirVersion":"5.0.0","canonical":"http://hl7.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.r5.examples-5.0.0.tgz","date":"2023-05-03T09:48:24.000Z","description":"Examples for the 5.0.0 version of the FHIR standard (built Sun, Mar 26, 2023 15:21+1100+11:00)"},{"name":"hl7.fhir.r5.expansions","version":"5.0.0","fhirVersion":"5.0.0","canonical":"http://hl7.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.r5.expansions-5.0.0.tgz","date":"2023-05-03T09:49:07.000Z","description":"Expansions for the 5.0.0 version of the FHIR standard (built Sun, Mar 26, 2023 15:21+1100+11:00)"},{"name":"hl7.fhir.r5.search","version":"5.0.0","fhirVersion":"5.0.0","canonical":"http://hl7.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.r5.search-5.0.0.tgz","date":"2023-05-03T09:49:11.000Z","description":"FHIR 5.0.0 package : Search Parameters (break out combined parameters for server execution convenience) (built Sun, Mar 26, 2023 15:21+1100+11:00)"},{"name":"hl7.fhir.us.specialty-rx","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/specialty-rx","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.specialty-rx-2.0.0.tgz","date":"2023-05-04T18:00:24.000Z","description":"This implementation guide describes the exchange of information needed to dispense specialty medications and enroll patients in associated programs offered by pharmaceutical manufacturers and others. (built Thu, May 4, 2023 14:22+0000+00:00)"},{"name":"hl7.fhir.essilux.core","version":"0.0.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/hl7.fhir.essilux.core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.essilux.core-0.0.2.tgz","date":"2023-05-09T15:42:26.000Z","description":"Essilor Luxottica IT EYECARE FHIR PROJECT"},{"name":"amwell.fhir.profiles","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/amwell.fhir.profiles","kind":"fhir.ig","url":"https://packages2.fhir.org/web/amwell.fhir.profiles-2.0.0.tgz","date":"2023-05-10T16:51:13.000Z","description":"profiles for amwell "},{"name":"ans.cisis.nde.fhir.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ans.cisis.nde.fhir.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ans.cisis.nde.fhir.r4-1.0.0.tgz","date":"2023-05-25T14:23:55.000Z","description":"Ressources de conformité (profils, extensions, capability statements...) du volet Notification d'évènements (NdE) FHIR R4 du cadre d'interopérabilité des systèmes d'information de santé, CI-SIS, de l'ANS"},{"name":"hl7.fhir.uv.vulcan-rwd","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/vulcan-rwd","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.vulcan-rwd-1.0.0.tgz","date":"2023-05-26T18:01:10.000Z","description":"A FHIR Implementation Guide that provides profiles and use cases that show how real world data can be exposed in such a way that it can be used for research purposes. (built Fri, May 26, 2023 22:51+1000+10:00)"},{"name":"hl7.fhir.us.military-service","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/military-service","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.military-service-1.0.0.tgz","date":"2023-05-30T18:01:14.000Z","description":"Military Service History and Status is an implementation guide for military service history and veteran status verification/confirmation. (built Tue, May 30, 2023 14:59+0000+00:00)"},{"name":"hl7.fhir.us.medmorph","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/medmorph","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.medmorph-1.0.0.tgz","date":"2023-06-09T00:01:11.000Z","description":"MedMorph describes a framework to enable submission of data from healthcare organizations to public health and research organizations. (built Thu, Jun 8, 2023 18:48+0000+00:00)"},{"name":"ans.annuaire.fhir.r4","version":"0.2.0-pat23","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ans.annuaire.fhir.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ans.annuaire.fhir.r4-0.2.0-pat23.tgz","date":"2023-06-16T08:01:53.000Z","description":"Description de la structure des données d'identification des acteurs de santé exposées par les nouveaux services Annuaire Santé d'interrogation FHIR de l'Agence du Numérique en Santé (ANS). "},{"name":"cisis.cds","version":"4.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/cisis.cds","kind":"fhir.ig","url":"https://packages2.fhir.org/web/cisis.cds-4.0.0.tgz","date":"2023-06-21T08:28:42.000Z","description":"test"},{"name":"ans.cisis.fhir.r4","version":"3.0.0-pat23v2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ans.cisis.fhir.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ans.cisis.fhir.r4-3.0.0-pat23v2.tgz","date":"2023-06-22T11:55:48.000Z","description":"Ressources de conformité (profils, extensions, capability statements...) des volets FHIR R4 du cadre d'interopérabilité des systèmes d'information de santé, CI-SIS, de l'ANS."},{"name":"surescripts.specialty","version":"1.2.0-beta","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/surescripts.specialty","kind":"fhir.ig","url":"https://packages2.fhir.org/web/surescripts.specialty-1.2.0-beta.tgz","date":"2023-06-23T15:34:43.000Z","description":"This project holds the profiles, message examples, and simplifier implementation guide for the Surescripts Specialty Patient Enrollment products."},{"name":"de.gematik.isik-basismodul-stufe1","version":"1.0.10","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gematik.isik-basismodul-stufe1","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.isik-basismodul-stufe1-1.0.10.tgz","date":"2023-06-29T13:22:25.000Z","description":"Informationstechnische Systeme im Krankenhaus"},{"name":"eng.fhir.profile.dev","version":"0.0.7-beta","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/eng.fhir.profile.dev","kind":"fhir.ig","url":"https://packages2.fhir.org/web/eng.fhir.profile.dev-0.0.7-beta.tgz","date":"2023-07-05T16:01:42.000Z","description":"Raccolta profili FHIR aziendali (dev)"},{"name":"nictiz.fhir.nl.r4.elz","version":"0.2.0-beta.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/nictiz.fhir.nl.r4.elz","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nictiz.fhir.nl.r4.elz-0.2.0-beta.1.tgz","date":"2023-07-10T12:55:20.000Z","description":"NL package of FHIR R4 conformance resources for ELZ."},{"name":"lung.ca.screen.assignment","version":"1.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/lung.ca.screen.assignment","kind":"fhir.ig","url":"https://packages2.fhir.org/web/lung.ca.screen.assignment-1.0.1.tgz","date":"2023-07-25T12:33:06.000Z","description":"This is a project as part of assignment of FHIR Course hosted by SIL-TH"},{"name":"hl7.fhir.uv.emedicinal-product-info","version":"1.0.0","fhirVersion":"5.0.0","canonical":"http://hl7.org/fhir/uv/emedicinal-product-info","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.emedicinal-product-info-1.0.0.tgz","date":"2023-07-26T18:01:26.000Z","description":"FHIR Implementation Guide representing how to create Electronic Medicinal Product Information. (built Wed, Jul 26, 2023 13:29+0000+00:00)"},{"name":"rki.demis.r4.core","version":"1.23.2","fhirVersion":"4.0.1","canonical":"https://demis.rki.de/fhir/demis","kind":"fhir.ig","url":"https://packages2.fhir.org/web/rki.demis.r4.core-1.23.2.tgz","date":"2023-07-28T09:56:24.000Z","description":"Deutsches Elektronisches Melde- und Informationssystem für den Infektionsschutz"},{"name":"hl7.fhir.us.bser","version":"2.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/bser","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.bser-2.0.0-ballot.tgz","date":"2023-07-31T12:00:00.000Z"},{"name":"incisive.fhir","version":"1.0.1-preview","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/incisive.fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/incisive.fhir-1.0.1-preview.tgz","date":"2023-08-04T06:23:53.000Z","description":"European AI Project"},{"name":"pathologyencountertissue.tryout","version":"1.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/pathologyencountertissue.tryout","kind":"fhir.ig","url":"https://packages2.fhir.org/web/pathologyencountertissue.tryout-1.0.1.tgz","date":"2023-08-04T08:05:44.000Z","description":"lets start to get swiss pathology structured"},{"name":"ch.cel.thetest2-core","version":"0.8.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ch.cel.thetest2-core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ch.cel.thetest2-core-0.8.1.tgz","date":"2023-08-04T10:44:18.000Z","description":"Project for testing packaging"},{"name":"careconnect.stu3.03.00.00","version":"3.1.0","fhirVersion":"3.0.1","canonical":"http://simplifier.net/packages/careconnect.stu3.03.00.00","kind":"fhir.ig","url":"https://packages2.fhir.org/web/careconnect.stu3.03.00.00-3.1.0.tgz","date":"2023-08-04T12:07:50.000Z","description":"This is the initial baseline of the STU3 Care Connect assets."},{"name":"qualitype.fhir.samples","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/qualitype.fhir.samples","kind":"fhir.ig","url":"https://packages2.fhir.org/web/qualitype.fhir.samples-1.0.0.tgz","date":"2023-08-07T07:23:32.000Z","description":"The official documentation of the HL7 FHIR interface of SAMPLES by qualitype GmbH."},{"name":"uk.gpc.updaterecord","version":"1.1.0","fhirVersion":"3.0.1","canonical":"http://simplifier.net/packages/uk.gpc.updaterecord","kind":"fhir.ig","url":"https://packages2.fhir.org/web/uk.gpc.updaterecord-1.1.0.tgz","date":"2023-08-07T15:31:21.000Z","description":"This project contains the profiles and packages defined as part of the GP Connect access structured record capability."},{"name":"hl7uk.fhir.communityassets","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/hl7uk.fhir.communityassets","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7uk.fhir.communityassets-1.0.0.tgz","date":"2023-08-08T10:35:29.000Z","description":"A project to mange and develop UK FHIR Assets "},{"name":"kl.dk.fhir.core","version":"1.2.0","fhirVersion":"4.0.1","canonical":"http://fhir.kl.dk/core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kl.dk.fhir.core-1.2.0.tgz","date":"2023-08-08T12:02:09.000Z","description":"Danish municipalities implementation guide for common informationmodel (built Wed, Jun 7, 2023 17:46+0200+02:00)"},{"name":"logex.internal.fhir.profiles","version":"1.0.0","fhirVersion":"3.0.1","canonical":"http://simplifier.net/packages/logex.internal.fhir.profiles","kind":"fhir.ig","url":"https://packages2.fhir.org/web/logex.internal.fhir.profiles-1.0.0.tgz","date":"2023-08-14T14:19:39.000Z","description":"This project is meant for creating and testing profiles used for LOGEX's FHIR integration"},{"name":"hl7.fhir.uv.ichom-breast-cancer","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/ichom-breast-cancer","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.ichom-breast-cancer-1.0.0.tgz","date":"2023-08-21T18:01:30.000Z"},{"name":"hl7.fhir.us.physical-activity","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/physical-activity","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.physical-activity-1.0.0.tgz","date":"2023-08-25T18:01:13.000Z","description":"This implementation guide provides standardization around patient physical activity, including: * measures for recording a patient's level of physical activity; * measures to support assertions of physical activity, including device-based measures; * goals and care plans related to improving a patient's physical activity level; * orders for interventions seeking to improve a patient's physical activity level; and * processes to support closing the loop and evaluating the success of such interventions. (built Fri, Aug 25, 2023 15:28+0000+00:00)"},{"name":"hl7.fhir.us.icsr-ae-reporting","version":"1.0.1","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/icsr-ae-reporting","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.icsr-ae-reporting-1.0.1.tgz","date":"2023-08-30T00:01:17.000Z","description":"A set of profiles that define the data elements needed to detect conditions and observations arising from transfusions or vaccinations that are candidates for Adverse Events as well as profiles that allow the reporting of Adverse Events (built Tue, Aug 29, 2023 21:13+0000+00:00)"},{"name":"ihe.iti.svcm","version":"1.5.1","fhirVersion":"4.0.1","canonical":"https://profiles.ihe.net/ITI/SVCM","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.iti.svcm-1.5.1.tgz","date":"2023-09-01T18:02:01.000Z","description":"The Sharing Valuesets, Codes, and Maps (SVCM) Profile defines a lightweight interface through which healthcare systems may retrieve centrally managed uniform nomenclature and mappings between code systems based on the HL7 Fast Healthcare Interoperability Resources (FHIR) specification. (built Wed, Aug 2, 2023 12:46-0500-05:00)"},{"name":"ihe.iti.mhds","version":"2.3.1","fhirVersion":"4.0.1","canonical":"https://profiles.ihe.net/ITI/MHDS","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.iti.mhds-2.3.1.tgz","date":"2023-09-02T00:02:07.000Z","description":"This Implementation Guide shows how to build a Document Sharing Exchange using IHE-profiled FHIR standard, rather than the legacy IHE profiles that are dominated by XDS and HL7 v2. This Implementation Guide assembles other IHE Implementation guides (Profiles) and defines a Document Registry Actor. (built Fri, Aug 4, 2023 11:14-0500-05:00)"},{"name":"ihe.iti.mxde","version":"1.3.0","fhirVersion":"4.0.1","canonical":"https://profiles.ihe.net/ITI/mXDE","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.iti.mxde-1.3.0.tgz","date":"2023-09-02T00:02:07.000Z","description":"The Mobile Cross-Enterprise Document Data Element Extraction (mXDE) Profile provides the means to access data elements extracted from shared structured documents. The profile enables the deployment of health data exchange infrastructures where fine-grained access to health data coexists and complements the sharing of coarse-grained documents and the fine-grained data elements they contain. (built Fri, Aug 4, 2023 10:53-0500-05:00)"},{"name":"hl7.fhir.rdsuwearme","version":"1.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/hl7.fhir.rdsuwearme","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.rdsuwearme-1.0.1.tgz","date":"2023-09-04T07:38:13.000Z","description":"Package version 1.0.0"},{"name":"hl7.fhir.nume.dev","version":"1.0.3","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/hl7.fhir.nume.dev","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.nume.dev-1.0.3.tgz","date":"2023-09-05T12:54:40.000Z","description":"FHIR Nume - Dev"},{"name":"hl7.fhir.us.hai","version":"2.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/hai","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.hai-2.1.0.tgz","date":"2023-09-07T00:01:24.000Z","description":"This implementation guide (IG) specifies standards for electronic submission of Healthcare Associated Infection (HAI) reports to the National Healthcare Safety Network (NHSN) of the Centers for Disease Control and Prevention (CDC). This IG contains a library of FHIR profiles for electronic submission of HAI reports to the NHSN.\n\nAs reports are modified and new report types are defined, CDC and Health Level Seven (HL7) will develop and publish additional constraints.\n\nThroughout this process, CDC remains the authority on NHSN data collection protocols. When healthcare enterprises choose to participate in NHSN, they must report to CDC occurrences such as specific reportable procedures, even those without complications, and events such as a bloodstream infection, either confirmed by a positive blood culture or supported by a patients clinical symptoms. This specification opens the channel for data submission by all applications compliant with the data coding requirements defined here.\n\nNote that participation in the NHSN requires enrollment and filing of reporting plans, which are not defined by this specification. For an overview of NHSN and full information on NHSN participation requirements, see: [http://www.cdc.gov/nhsn](http://www.cdc.gov/nhsn). Provisions of the Public Health Service Act protect all data reported to NHSN from discovery through the Freedom of Information Act (FOIA). (built Wed, Sep 6, 2023 19:56+0000+00:00)"},{"name":"kl.dk.fhir.ffbmessaging","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.kl.dk/ffbmessaging","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kl.dk.fhir.ffbmessaging-1.0.0.tgz","date":"2023-09-08T18:02:05.000Z","description":"Danish municipalities implementation guide for FFB messaging. A standard for exchanging social information from citizen journals between municipalities. The aim is to support citizens continuously, e.g. when they move, or receives interventions outside their home municipality. (built Sun, Aug 27, 2023 07:52+0200+02:00)"},{"name":"kl.dk.fhir.ffbreporting","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.kl.dk/ffbreporting","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kl.dk.fhir.ffbreporting-1.0.0.tgz","date":"2023-09-08T18:02:05.000Z","description":"Danish municipalities implementation guide for FFB reporting. A standard for reporting social information from citizen journals to a gateway. The aim is to use the data in population based studies and management information systems. (built Sun, Aug 27, 2023 00:02+0200+02:00)"},{"name":"kl.dk.fhir.ffinst","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.kl.dk/ffinst","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kl.dk.fhir.ffinst-1.0.0.tgz","date":"2023-09-08T18:02:06.000Z","description":"Danish municipalities implementation guide for FFInst (built Sun, Aug 27, 2023 10:19+0200+02:00)"},{"name":"care.commonprofiles.fhir","version":"1.0.1","fhirVersion":"4.0.1","canonical":"https://commonprofiles.care/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/care.commonprofiles.fhir-1.0.1.tgz","date":"2023-09-20T18:04:01.000Z"},{"name":"hl7.xprod.uv.gender-harmony","version":"1.0.0","fhirVersion":"5.0.0","canonical":"http://hl7.org/xprod/ig/uv/gender-harmony","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.xprod.uv.gender-harmony-1.0.0.tgz","date":"2023-09-29T12:01:21.000Z","description":"HL7 Cross Paradigm Implementation Guide: Gender Harmony - Sex and Gender Representation, Edition 1 (built Fri, Sep 29, 2023 16:01+1000+10:00)"},{"name":"commonwell-consent-trial01.01","version":"0.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/commonwell-consent-trial01.01","kind":"fhir.ig","url":"https://packages2.fhir.org/web/commonwell-consent-trial01.01-0.0.1.tgz","date":"2023-10-02T20:42:08.000Z","description":"CommonWell consent - attempt 01"},{"name":"niceprofiling.v23q1","version":"0.5.0","fhirVersion":"3.0.1","canonical":"http://simplifier.net/packages/niceprofiling.v23q1","kind":"fhir.ig","url":"https://packages2.fhir.org/web/niceprofiling.v23q1-0.5.0.tgz","date":"2023-10-04T12:43:14.000Z","description":"FHIR STU3 conformance resource for NICE based on zib release 2017"},{"name":"hl7.fhir.us.hsds","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/hsds","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.hsds-1.0.0.tgz","date":"2023-10-05T00:01:18.000Z","description":"fhir-human-services-directory (built Wed, Oct 4, 2023 18:49+0000+00:00)"},{"name":"ihe.rad.ira","version":"1.0.0","fhirVersion":"5.0.0","canonical":"https://profiles.ihe.net/RAD/IRA","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.rad.ira-1.0.0.tgz","date":"2023-10-05T00:02:09.000Z","description":"The Integrated Reporting Applications (IRA) profile helps applications that are used together during reporting (e.g., image display, report creator, clinical applications, AI tools, etc) to share information using a standard called FHIRcast. Each application can share what it is doing and the data it is creating, referred to as Context and Content, respectively. Other applications are notified so they can then intelligently synchronize their behavior or use the new data. (built Tue, Oct 3, 2023 19:27-0500-05:00)"},{"name":"tsti.adultcheck","version":"0.1.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/tsti.adultcheck","kind":"fhir.ig","url":"https://packages2.fhir.org/web/tsti.adultcheck-0.1.2.tgz","date":"2023-10-16T06:42:44.000Z","description":"成人預防保健實作指引(Adult Check IG) 採用HL7® FHIR® standard（Fast Healthcare Interoperability Resources）IG建置方法"},{"name":"acme.canada.2023","version":"1.2.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/acme.canada.2023","kind":"fhir.ig","url":"https://packages2.fhir.org/web/acme.canada.2023-1.2.0.tgz","date":"2023-10-17T19:47:47.000Z","description":"This is a demonstration package for FHIR North 2023"},{"name":"silth.fhir.terminology.core","version":"0.1.2","fhirVersion":"5.0.0","canonical":"https://terms.sil-th.org/core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/silth.fhir.terminology.core-0.1.2.tgz","date":"2023-10-25T06:09:19.000Z","description":"A terminology registry which an be cited by FHIR artifacts (built Wed, Oct 11, 2023 23:14+0700+07:00)"},{"name":"il.core.fhir.r4.2023","version":"0.1.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/il.core.fhir.r4.2023","kind":"fhir.ig","url":"https://packages2.fhir.org/web/il.core.fhir.r4.2023-0.1.0.tgz","date":"2023-10-26T15:54:43.000Z","description":"IL core project "},{"name":"phis.ig.createtest","version":"0.0.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/phis.ig.createtest","kind":"fhir.ig","url":"https://packages2.fhir.org/web/phis.ig.createtest-0.0.2.tgz","date":"2023-10-26T23:09:02.000Z","description":"2023. 10. 26. FHIR IG 생성 테스트 목적"},{"name":"promptly.patient","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/promptly.patient","kind":"fhir.ig","url":"https://packages2.fhir.org/web/promptly.patient-1.0.0.tgz","date":"2023-10-28T07:44:07.000Z","description":"HL7 FHIR - Resource type Patient"},{"name":"test.no.basis","version":"2.2.0-beta3","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/test.no.basis","kind":"fhir.ig","url":"https://packages2.fhir.org/web/test.no.basis-2.2.0-beta3.tgz","date":"2023-10-30T13:44:49.000Z","description":"Testprofiler for basisprofiler"},{"name":"de.gevko.evo.hlm","version":"1.3.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gevko.evo.hlm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gevko.evo.hlm-1.3.0.tgz","date":"2023-11-02T13:00:23.000Z","description":"Umsetzung der elektronischen Heilmittelverordnung"},{"name":"phis.ig.dev","version":"0.1.7","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/phis.ig.dev","kind":"fhir.ig","url":"https://packages2.fhir.org/web/phis.ig.dev-0.1.7.tgz","date":"2023-11-08T04:51:32.000Z","description":"2023. 10. 26. FHIR IG 생성 테스트 목적"},{"name":"pcr.r4.1-1-0-pkg","version":"1.2.5","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/pcr.r4.1-1-0-pkg","kind":"fhir.ig","url":"https://packages2.fhir.org/web/pcr.r4.1-1-0-pkg-1.2.5.tgz","date":"2023-11-08T21:03:01.000Z","description":"Implementation Guide and FHIR artifacts for the Ontario Provincial Provider Registry "},{"name":"de.netzwerk-universitaetsmedizin.codexplus.celida.template","version":"0.1.0","fhirVersion":"4.0.1","canonical":"https://www.netzwerk-universitaetsmedizin.de/fhir/celida/ig-template-celida","kind":"fhir.template","url":"https://packages2.fhir.org/web/de.netzwerk-universitaetsmedizin.codexplus.celida.template-0.1.0.tgz","date":"2023-11-11T12:47:07.000Z","description":"CODEX+ CELIDA template extension for FHIR IG"},{"name":"iknl.fhir.nl.r4.performation","version":"0.2.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/iknl.fhir.nl.r4.performation","kind":"fhir.ig","url":"https://packages2.fhir.org/web/iknl.fhir.nl.r4.performation-0.2.0.tgz","date":"2023-11-15T07:32:34.000Z","description":"FHIR R4 profielen voor samenwerking tussen IKNL en Performation"},{"name":"de.medizininformatikinitiative.kerndatensatz.symptom","version":"2024.0.0-ballot","fhirVersion":"4.0.1","canonical":"https://www.medizininformatik-initiative.de/fhir/ext/modul-symptom/ImplementationGuide/mii-ig-symptom-de-v2024","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.medizininformatikinitiative.kerndatensatz.symptom-2024.0.0-ballot.tgz","date":"2023-11-17T14:24:28.000Z","description":"Medizininformatik Initiative - Modul Symptom"},{"name":"ihe.iti.npfs","version":"2.2.0","fhirVersion":"4.0.1","canonical":"https://profiles.ihe.net/ITI/NPFS","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.iti.npfs-2.2.0.tgz","date":"2023-11-18T00:06:57.000Z","description":"The Non-Patient File Sharing (NPFS) Profile defines how to share non-patient files such as clinical workflow definitions, domain policies, and stylesheets. Those files can be created and consumed by many different systems involved in a wide variety of data sharing workflows. (built Thu, Nov 16, 2023 16:06-0600-06:00)"},{"name":"ihe.iti.sips","version":"1.0.0","fhirVersion":"4.0.1","canonical":"https://profiles.ihe.net/ITI/sIPS","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.iti.sips-1.0.0.tgz","date":"2023-11-18T00:06:59.000Z","description":"Sharing of IPS (sIPS) - defines how HL7 FHIR IPS is communicated using IHE Document Sharing (built Fri, Nov 17, 2023 05:59-0600-06:00)"},{"name":"fhir.ig.mc","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://simplifier.net/packages/fhir.ig.mc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.ig.mc-1.0.0.tgz","date":"2023-12-04T12:25:35.000Z","description":"profiles used by mc"},{"name":"ans.fr.securisation-transport","version":"1.2.0","fhirVersion":"4.0.1","canonical":"https://interop.esante.gouv.fr/ig/securisation-transport","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ans.fr.securisation-transport-1.2.0.tgz","date":"2023-12-06T06:07:00.000Z"},{"name":"hl7.fhir.xver-extensions","version":"0.1.0","fhirVersion":"4.0.1","canonical":"http://fhir.org/packages/hl7.fhir.xver-extensions","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.xver-extensions-0.1.0.tgz","date":"2023-12-14T12:03:51.000Z"},{"name":"kr.myfhirtest","version":"0.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/kr.myfhirtest","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kr.myfhirtest-0.0.1.tgz","date":"2023-12-15T05:10:25.000Z","description":"This is test package."},{"name":"beact.es.publishingtutorial","version":"0.0.1-test","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/beact.es.publishingtutorial","kind":"fhir.ig","url":"https://packages2.fhir.org/web/beact.es.publishingtutorial-0.0.1-test.tgz","date":"2023-12-15T11:31:35.000Z","description":"TestingFHIR"},{"name":"ca.on.dhdr.r4.v4","version":"0.1.2-beta","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.dhdr.r4.v4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.dhdr.r4.v4-0.1.2-beta.tgz","date":"2023-12-15T20:21:30.000Z","description":"Implementation Guide for the Ontario DHDR HL7 FHIR 4.0.0- work-in-progress version"},{"name":"ch.fhir.ig.ch-epr-term","version":"2.0.10","fhirVersion":"4.0.1","canonical":"http://fhir.ch/ig/ch-epr-term","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ch.fhir.ig.ch-epr-term-2.0.10.tgz","date":"2023-12-19T12:07:21.000Z","description":"Implementation guide for the meta data specified in the framework of Annex 3 and 9 of the FDHA Ordinance on the electronic patient record in Switzerland (built Tue, Dec 19, 2023 12:36+0100+01:00)"},{"name":"hl7.fhir.be.allergy","version":"1.2.0","fhirVersion":"4.0.1","canonical":"https://www.ehealth.fgov.be/standards/fhir/allergy","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.be.allergy-1.2.0.tgz","date":"2023-12-19T18:07:26.000Z","description":"Allergy (Patient Dossier) (built Mon, Dec 18, 2023 11:58+0100+01:00)"},{"name":"ch.fhir.ig.ch-epr-ppqm","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.ch/ig/ch-epr-ppqm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ch.fhir.ig.ch-epr-ppqm-2.0.0.tgz","date":"2023-12-20T18:07:29.000Z","description":"Implementation Guide for the Privacy Policy Query for Mobile (PPQm) for the Swiss EPR (built Wed, Dec 20, 2023 11:33+0100+01:00)"},{"name":"hl7.fhir.uv.livd","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/livd","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.livd-1.0.0-ballot.tgz","date":"2023-12-22T00:02:06.000Z","description":"Recommended LOINC mappings for IVD Devices (built Thu, Dec 21, 2023 20:53+0000+00:00)"},{"name":"ehealth4u.package","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ehealth4u.package","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ehealth4u.package-1.0.0.tgz","date":"2024-01-08T23:41:19.000Z","description":"The eHealth4U is a research project that undertakes the challenge of designing and developing a prototype of the national integrated EHR system in Cyprus. More information: http://ehealth4u.cs.ucy.ac.cy/"},{"name":"ig.in","version":"0.1.0","fhirVersion":"4.0.1","canonical":"https://nrces.in/pre/ndhm/fhir/r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ig.in-0.1.0.tgz","date":"2024-01-10T00:08:07.000Z"},{"name":"myhie.v4-test","version":"0.0.1-alpha","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/myhie.v4-test","kind":"fhir.ig","url":"https://packages2.fhir.org/web/myhie.v4-test-0.0.1-alpha.tgz","date":"2024-01-12T07:07:21.000Z","description":"Malaysia Health Information Exchange"},{"name":"hl7.fhir.be.patientwill","version":"1.0.0","fhirVersion":"4.0.1","canonical":"https://www.ehealth.fgov.be/standards/fhir/patientwill","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.be.patientwill-1.0.0.tgz","date":"2024-01-12T18:07:32.000Z","description":"Belgian Patient profiles (built Mon, Jan 8, 2024 16:07+0100+01:00)"},{"name":"ihe.iti.pcf","version":"1.1.0","fhirVersion":"4.0.1","canonical":"https://profiles.ihe.net/ITI/PCF","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.iti.pcf-1.1.0.tgz","date":"2024-02-24T00:07:56.000Z","description":"The Privacy Consent on FHIR (PCF) Profile provides support for patient privacy consents and access control where a FHIR API is used to access Document Sharing Health Information Exchanges. (built Thu, Feb 22, 2024 13:50-0600-06:00)"},{"name":"fmcna.caredata.fhir.ig.r4.copy","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fmcna.caredata.fhir.ig.r4.copy","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fmcna.caredata.fhir.ig.r4.copy-1.0.0.tgz","date":"2024-02-26T03:21:20.000Z","description":"Fresenius Medical Care Data Model"},{"name":"nictiz.fhir.nl.stu3.zib2020-preadopt","version":"0.1.3","fhirVersion":"3.0.1","canonical":"http://simplifier.net/packages/nictiz.fhir.nl.stu3.zib2020-preadopt","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nictiz.fhir.nl.stu3.zib2020-preadopt-0.1.3.tgz","date":"2024-02-27T10:13:12.000Z","description":"Nictiz NL package of FHIR STU3 conformance resources for pre-adopted profiles from HCIM Release 2020 to be used within a HCIM Release 2017 context. Please note: pre-adoption is strongly discouraged and should only be considered in exceptional circumstances."},{"name":"ans.fhir.fr.eclaire","version":"0.3.0","fhirVersion":"4.0.1","canonical":"https://interop.esante.gouv.fr/ig/fhir/eclaire","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ans.fhir.fr.eclaire-0.3.0.tgz","date":"2024-02-27T12:08:29.000Z","description":"Implementation Guide pour définir l'API FHIR pour ECLAIRE (Essais CLiniques Accessibles Interconnectés pour la Recherche ouverts à l'Ecosystème) (built Mon, Feb 26, 2024 13:32+0000+00:00)"},{"name":"ihe.iti.dsubm","version":"1.0.0","fhirVersion":"4.0.1","canonical":"https://profiles.ihe.net/ITI/DSUBm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.iti.dsubm-1.0.0.tgz","date":"2024-03-01T00:07:33.000Z","description":"profile describes the use of document subscription and notification mechanisms for RESTful applications. (built Thu, Feb 29, 2024 12:23-0600-06:00)"},{"name":"ch.fhir.ig.ch-epr-mhealth","version":"3.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.ch/ig/ch-epr-mhealth","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ch.fhir.ig.ch-epr-mhealth-3.0.0.tgz","date":"2024-03-05T12:07:31.000Z","description":"Implementation Guide for the Mobile access to Health Documents (epr-mhealth) Profile for the Swiss EPR (built Tue, Mar 5, 2024 12:06+0100+01:00)"},{"name":"ca.on.ppr.r4","version":"1.2.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.ppr.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.ppr.r4-1.2.0.tgz","date":"2024-03-06T14:17:19.000Z","description":"FHIR-based Implementation Guide for Ontario Provincial Provider Registry System"},{"name":"hl7.fhir.it.lab-report","version":"0.2.0","fhirVersion":"4.0.1","canonical":"http://hl7.it/fhir/lab-report","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.it.lab-report-0.2.0.tgz","date":"2024-03-14T18:11:24.000Z","description":"HL7 FHIR Implementation Guide Laboratory Report specifica come utilizzare lo standard HL7 FHIR per documentare un referto di medicina di laboratorio. (built Fri, Mar 8, 2024 08:50+0100+01:00)"},{"name":"ca.on.oh.patient-summary","version":"0.12.8","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.oh.patient-summary","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.oh.patient-summary-0.12.8.tgz","date":"2024-03-27T14:21:01.000Z","description":"Ontario Patient Summary"},{"name":"tesisoncologicia.ubo","version":"1.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/tesisoncologicia.ubo","kind":"fhir.ig","url":"https://packages2.fhir.org/web/tesisoncologicia.ubo-1.0.1.tgz","date":"2024-03-28T23:23:24.000Z","description":"Tesis HL7 FHIR en Oncologia"},{"name":"br.ufg.cgis.ig","version":"0.0.3","fhirVersion":"4.0.1","canonical":"https://fhir.fabrica.inf.ufg.br/ig","kind":"fhir.ig","url":"https://packages2.fhir.org/web/br.ufg.cgis.ig-0.0.3.tgz","date":"2024-04-01T00:09:28.000Z","description":"Ilustra criação de guias de implementação (built Sun, Mar 31, 2024 18:31-0300-03:00)"},{"name":"de.gematik.isik-labor","version":"4.0.0-rc","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gematik.isik-labor","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.isik-labor-4.0.0-rc.tgz","date":"2024-04-04T15:32:10.000Z","description":"Labor-Modul der Informationstechnischen Systeme im Krankenhaus Ausbaustufe 4; Support-Status!"},{"name":"kbv.mio.emp","version":"1.0.0-kommentierung.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/kbv.mio.emp","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kbv.mio.emp-1.0.0-kommentierung.1.tgz","date":"2024-04-05T05:53:27.000Z","description":"Medikationsplan"},{"name":"deepdive.stress.record","version":"0.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/deepdive.stress.record","kind":"fhir.ig","url":"https://packages2.fhir.org/web/deepdive.stress.record-0.0.1.tgz","date":"2024-04-08T02:07:07.000Z","description":"DeepDive FHIR Stress Record R4"},{"name":"odilab.evo","version":"0.0.5","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/odilab.evo","kind":"fhir.ig","url":"https://packages2.fhir.org/web/odilab.evo-0.0.5.tgz","date":"2024-04-08T14:22:59.000Z","description":"Testprojekt für Hilfs- und Heilmittel eVerordnungen"},{"name":"tw.gov.mohw.cdc.twidir","version":"0.1.1","fhirVersion":"4.0.1","canonical":"https://twidir.cdc.gov.tw/twidir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/tw.gov.mohw.cdc.twidir-0.1.1.tgz","date":"2024-04-10T06:01:57.000Z","description":"臺灣傳染病檢驗報告實作指引 (built Fri, Feb 2, 2024 13:13+0800+08:00)"},{"name":"hl7.fhir.uv.fhircast","version":"3.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/fhircast","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.fhircast-3.0.0-ballot.tgz","date":"2024-04-10T18:01:03.000Z","description":"FHIRcast synchronizes healthcare applications in real time to show the same clinical content to a common user. (built Wed, Apr 10, 2024 15:14+0000+00:00)"},{"name":"kr.mohw.myhealthway","version":"1.0.2-beta.4","fhirVersion":"4.0.1","canonical":"https://hins.or.kr/fhir/MyHealthWay","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kr.mohw.myhealthway-1.0.2-beta.4.tgz","date":"2024-04-19T01:47:21.000Z","description":"KR Core V1 기반의 건강정보 고속도로 상세규격 - 1.0.2-beta.4"},{"name":"ans.fhir.fr.gap","version":"3.0.0","fhirVersion":"4.0.1","canonical":"https://interop.esante.gouv.fr/ig/fhir/gap","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ans.fhir.fr.gap-3.0.0.tgz","date":"2024-04-30T06:01:31.000Z"},{"name":"hl7.fhir.uv.ae-research-backport-ig","version":"1.0.1","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/ae-research-backport-ig","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.ae-research-backport-ig-1.0.1.tgz","date":"2024-05-01T00:01:47.000Z","description":"### Intent The intent of this guide is to provide a profile on the FHIR AdverseEvent Resource suitable for Clinical Research. ### Overview A single Adverse Event (AE) may need to be reported in multiple ways. Choosing the appropriate form of the reporting is dependent upon workflow patterns. In particular, the implementation guides for Clinical Care adverse events and Clinical Research adverse events provide important extensions, value-sets and examples for implementing AdverseEvent. This guide, the Clinical Research adverse event implementation guide, is for the clinical research setting. In this setting, the event is tracked and evaluated as part of the clinical research process for the research study. In the research setting an adverse event is the result of an intervention that caused unintentional harm to a specific subject or group of subjects (this is surfaced in the profile as a constraint of ‘actual’ for the value of ‘actuality’). An example of an adverse event in the clinical research setting would be a patient develops renal failure while on a study drug. These events are characterized by the need to capture cause-and-effect (although they might not be known at the time of the event), severity, and outcome. The context of an adverse event is also important, and captured in the AdverseEvent Clinical Research Profile data elements. A subject may have condition(s) or current treatments (medications, diet, devices) that impact their response to a newly introduced medication, device or procedure. Knowledge of these variables is essential in establishing a cause-and-effect relationship for an adverse event. This information is represented with corresponding resources (e.g. Procedure Resource for procedures, etc.) and referenced. A potential adverse event may also be called a near miss or an error, these are not reported with the AdverseEvent Clinical Research Profile. ### Scope This FHIR IG enables the collection of adverse events in real-world data (RWD) sources such as electronic health records (EHR) and personal health records (PHR) that occur during clinical trials. It ensures the appropriate AE representation required to support clinical research trials within a regulated environment. As the AEs are collected in RWD sources, the data can be transmitted via FHIR to clinical trial management systems, regulatory agencies, sponsors, and clinical research organizations for further processing and reporting. In the pre-market clinical research setting, serious adverse events must be reported to the sponsor, clinical research organization, and regulatory agencies within a specific time frame for Institutional Review Boards (IRBs) and Data Safety Monitoring Board (DSMB) review. By using this IG, a clinical investigator can document an AE in the EHR, it can be received by a secondary clinical trial management system for triage and then forwarded to the sponsor and regulatory agencies. Similarly, a patient on a clinical trial can record an adverse event in their PHR that is then shared with the clinical investigator and reported to the sponsor and regulatory agencies as necessary. In a post-market situation, a patient, provider, or manufacturer can record the adverse event in a system and then report it to the FDA as a FHIR based MedWatch form. Within this guide are several examples. Every effort has been made to capture the most important details of the use of the AdverseEvent profile. However, some examples may provide only a stub to referenced resources (e.g. instances of Patient Resource will be referenced using logical ids but are not resolvable, implementation of Patient is left for other guidance and is not the subject of this guide). Connectathons are ideal opportunities to create, compare and consider the holistic implementation of all FHIR Resources. (built Tue, Apr 30, 2024 20:50+0000+00:00)"},{"name":"hl7.fhir.uv.ae-research-ig","version":"1.0.1","fhirVersion":"5.0.0","canonical":"http://hl7.org/fhir/uv/ae-research-ig","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.ae-research-ig-1.0.1.tgz","date":"2024-05-01T00:01:47.000Z","description":"### Intent The intent of this guide is to provide a profile on the FHIR AdverseEvent Resource suitable for Clinical Research. ### Overview A single Adverse Event (AE) may need to be reported in multiple ways. Choosing the appropriate form of the reporting is dependent upon workflow patterns. In particular, the implementation guides for Clinical Care adverse events and Clinical Research adverse events provide important extensions, value-sets and examples for implementing AdverseEvent. This guide, the Clinical Research adverse event implementation guide, is for the clinical research setting. In this setting, the event is tracked and evaluated as part of the clinical research process for the research study. In the research setting an adverse event is the result of an intervention that caused unintentional harm to a specific subject or group of subjects (this is surfaced in the profile as a constraint of ‘actual’ for the value of ‘actuality’). An example of an adverse event in the clinical research setting would be a patient develops renal failure while on a study drug. These events are characterized by the need to capture cause-and-effect (although they might not be known at the time of the event), severity, and outcome. The context of an adverse event is also important, and captured in the AdverseEvent Clinical Research Profile data elements. A subject may have condition(s) or current treatments (medications, diet, devices) that impact their response to a newly introduced medication, device or procedure. Knowledge of these variables is essential in establishing a cause-and-effect relationship for an adverse event. This information is represented with corresponding resources (e.g. Procedure Resource for procedures, etc.) and referenced. A potential adverse event may also be called a near miss or an error, these are not reported with the AdverseEvent Clinical Research Profile. ### Scope This FHIR IG enables the collection of adverse events in real-world data (RWD) sources such as electronic health records (EHR) and personal health records (PHR) that occur during clinical trials. It ensures the appropriate AE representation required to support clinical research trials within a regulated environment. As the AEs are collected in RWD sources, the data can be transmitted via FHIR to clinical trial management systems, regulatory agencies, sponsors, and clinical research organizations for further processing and reporting. In the pre-market clinical research setting, serious adverse events must be reported to the sponsor, clinical research organization, and regulatory agencies within a specific time frame for Institutional Review Boards (IRBs) and Data Safety Monitoring Board (DSMB) review. By using this IG, a clinical investigator can document an AE in the EHR, it can be received by a secondary clinical trial management system for triage and then forwarded to the sponsor and regulatory agencies. Similarly, a patient on a clinical trial can record an adverse event in their PHR that is then shared with the clinical investigator and reported to the sponsor and regulatory agencies as necessary. In a post-market situation, a patient, provider, or manufacturer can record the adverse event in a system and then report it to the FDA as a FHIR based MedWatch form. Within this guide are several examples. Every effort has been made to capture the most important details of the use of the AdverseEvent profile. However, some examples may provide only a stub to referenced resources (e.g. instances of Patient Resource will be referenced using logical ids but are not resolvable, implementation of Patient is left for other guidance and is not the subject of this guide). Connectathons are ideal opportunities to create, compare and consider the holistic implementation of all FHIR Resources. (built Tue, Apr 30, 2024 20:20+0000+00:00)"},{"name":"hl7.fhir.uv.pharm-quality","version":"1.0.0","fhirVersion":"5.0.0","canonical":"http://hl7.org/fhir/uv/pharm-quality","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.pharm-quality-1.0.0.tgz","date":"2024-05-08T18:00:53.000Z","description":"This IG is developed for the HL7 International Pharmaceutical Quality (PQ) - Industry Use Case project, sponsored by the Biomedical Research and Regulation Work Group \n* [Project Proposal: PSS-2137](https://jira.hl7.org/browse/PSS-2137)\n* [Project Scope Statement: PSS-2145](https://jira.hl7.org/browse/PSS-2145) (built Wed, May 8, 2024 13:18+0000+00:00)"},{"name":"nictiz.fhir.nl.r4.profilingguidelines","version":"0.9.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/nictiz.fhir.nl.r4.profilingguidelines","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nictiz.fhir.nl.r4.profilingguidelines-0.9.0.tgz","date":"2024-05-15T14:44:16.000Z","description":"This package contains profiles to check conformance to the Nictiz profiling guidelines for FHIR R4."},{"name":"acme.dallas.cowboy","version":"0.1.0-alpha","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/acme.dallas.cowboy","kind":"fhir.ig","url":"https://packages2.fhir.org/web/acme.dallas.cowboy-0.1.0-alpha.tgz","date":"2024-05-21T19:30:52.000Z","description":"Definition of the Dallas Cowboy"},{"name":"cidadex.testex","version":"1.0.1-beta","fhirVersion":"5.0.0","canonical":"http://simplifier.net/packages/cidadex.testex","kind":"fhir.ig","url":"https://packages2.fhir.org/web/cidadex.testex-1.0.1-beta.tgz","date":"2024-05-29T12:12:16.000Z","description":"rede de dados em saúde da cidade X"},{"name":"fmcna.caredata.fhir.ig.r4","version":"1.1.9","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fmcna.caredata.fhir.ig.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fmcna.caredata.fhir.ig.r4-1.1.9.tgz","date":"2024-05-30T19:50:20.000Z","description":"Fresenius Medical Care Data Model"},{"name":"ig.fhir-il-community.org.t17","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ig.fhir-il-community.org.t17","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ig.fhir-il-community.org.t17-1.0.0.tgz","date":"2024-06-03T15:09:39.000Z","description":"A national project for managing the pre authorization process between HMOs and Hospitals for ambulatory hospital services "},{"name":"fhir.outburn.co.il","version":"0.5.5","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.outburn.co.il","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.outburn.co.il-0.5.5.tgz","date":"2024-06-04T12:50:11.000Z","description":"outburn LTD\r\n\r\nhttp://outburn.co.il"},{"name":"ihe.pcc.maps","version":"1.0.0-comment","fhirVersion":"4.0.1","canonical":"https://profiles.ihe.net/PCC/mAPS","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.pcc.maps-1.0.0-comment.tgz","date":"2024-06-05T00:01:35.000Z","description":"Antepartum Summary is a content profile that defines the structure for the aggregation of significant events, diagnoses, and plans of care derived from the visits over the course of an antepartum episode. (built Tue, Jun 4, 2024 15:27-0500-05:00)"},{"name":"acme.minneapolis.cowboy","version":"0.1.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/acme.minneapolis.cowboy","kind":"fhir.ig","url":"https://packages2.fhir.org/web/acme.minneapolis.cowboy-0.1.0.tgz","date":"2024-06-10T21:11:08.000Z","description":"This is our Cowboy project"},{"name":"elona.health","version":"1.0.3","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/elona.health","kind":"fhir.ig","url":"https://packages2.fhir.org/web/elona.health-1.0.3.tgz","date":"2024-06-14T15:17:38.000Z","description":"Technical specification of data exports used in apps by Elona Health."},{"name":"hl7.fhir.be.public-health","version":"1.0.3","fhirVersion":"4.0.1","canonical":"https://www.ehealth.fgov.be/standards/fhir/public-health","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.be.public-health-1.0.3.tgz","date":"2024-06-14T18:01:34.000Z","description":"Public Health (built Wed, Jun 12, 2024 10:51+0200+02:00)"},{"name":"kbv.mio.kh-entlassbrief","version":"1.0.0-update","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/kbv.mio.kh-entlassbrief","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kbv.mio.kh-entlassbrief-1.0.0-update.tgz","date":"2024-06-18T09:38:31.000Z","description":"Medizinische Informationsobjekte (MIO) KH-Entlassbrief V1.0.0"},{"name":"ihe.rad.imr","version":"1.1.0","fhirVersion":"4.0.1","canonical":"https://profiles.ihe.net/RAD/IMR","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.rad.imr-1.1.0.tgz","date":"2024-06-26T00:01:31.000Z","description":"Support encoding and presentation of an interactive multimedia report (built Thu, Jun 20, 2024 08:48-0500-05:00)"},{"name":"fhir.rl.sviluppo","version":"2.0.5","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.rl.sviluppo","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.rl.sviluppo-2.0.5.tgz","date":"2024-06-28T09:01:48.000Z","description":"Progetto FHIR per Regione Lombardia"},{"name":"tewhatuora.digitaltooling.iguat","version":"0.0.6","fhirVersion":"4.0.1","canonical":"https://fhir-ig-uat.digital.health.nz/hnz-digital-tooling","kind":"fhir.ig","url":"https://packages2.fhir.org/web/tewhatuora.digitaltooling.iguat-0.0.6.tgz","date":"2024-06-30T00:03:48.000Z","description":"FHIR profiles used in FHIR Publishing processes within Health New Zealand Te Whatu Ora (built Mon, Jun 24, 2024 20:55+0000+00:00)"},{"name":"myhie.v4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/myhie.v4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/myhie.v4-1.0.0.tgz","date":"2024-07-01T02:40:34.000Z","description":"Malaysia Health Information Exchange"},{"name":"br.gov.saude.ccu","version":"0.0.1","fhirVersion":"4.0.1","canonical":"https://fhir.fabrica.inf.ufg.br/ccu","kind":"fhir.ig","url":"https://packages2.fhir.org/web/br.gov.saude.ccu-0.0.1.tgz","date":"2024-07-01T20:32:51.000Z","description":"EXPERIMENTAÇÃO (apenas para experimentação)\r\nProjeto realizado pela cooperação UFG e INCA para o Ministério da Saúde (Brasil)\r\nDetalhes em https://github.com/kyriosdata/farol "},{"name":"fhir.r4.wales.psom","version":"1.0.0-rc3","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.r4.wales.psom","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.r4.wales.psom-1.0.0-rc3.tgz","date":"2024-07-09T12:46:46.000Z","description":"HL7 FHIR® NHS Wales PSOM profiles and conformance resources."},{"name":"de.gematik.epa.research","version":"1.0.0-cc1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gematik.epa.research","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.epa.research-1.0.0-cc1.tgz","date":"2024-07-16T08:01:39.000Z","description":"The ePA research data specification"},{"name":"iknl.fhir.nl.r4.palga","version":"1.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/iknl.fhir.nl.r4.palga","kind":"fhir.ig","url":"https://packages2.fhir.org/web/iknl.fhir.nl.r4.palga-1.0.1.tgz","date":"2024-07-17T12:03:53.000Z","description":"IKNL profiles to fill the NCR (NKR) with data that is sent to IKNL by Palga"},{"name":"ca.ec.demo.test","version":"0.0.3","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.ec.demo.test","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.ec.demo.test-0.0.3.tgz","date":"2024-07-18T20:46:33.000Z","description":"EC Test"},{"name":"tw.cathay.fhir.iclaim","version":"1.0.0","fhirVersion":"4.0.1","canonical":"https://claim.cgh.org.tw/iclaim","kind":"fhir.ig","url":"https://packages2.fhir.org/web/tw.cathay.fhir.iclaim-1.0.0.tgz","date":"2024-07-23T01:52:17.000Z","description":"醫療保險理賠實作指引 (built Tue, Jul 23, 2024 21:52+0800+08:00)"},{"name":"de.ihe-d.terminology","version":"3.0.1","fhirVersion":"4.0.1","canonical":"http://fhir.de/packages/de.ihe-d.terminology","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.ihe-d.terminology-3.0.1.tgz","date":"2024-08-01T18:01:53.000Z","description":"de.ihe-d.terminology"},{"name":"digi.derm","version":"0.1.2","fhirVersion":"5.0.0","canonical":"http://simplifier.net/packages/digi.derm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/digi.derm-0.1.2.tgz","date":"2024-08-06T10:15:38.000Z","description":"Test/spike into FHIR profiling"},{"name":"hl7.fhir.uv.dicom-sr","version":"1.0.0-ballot","fhirVersion":"5.0.0","canonical":"http://hl7.org/fhir/uv/dicom-sr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.dicom-sr-1.0.0-ballot.tgz","date":"2024-08-09T18:00:56.000Z","description":"Provides guidance for extracting key content from DICOM® Structured Report (SR) objects into FHIR Observations to make use of the results with the larger hospital enterprise. (built Fri, Aug 9, 2024 16:23+0000+00:00)"},{"name":"hl7.fhir.uv.ibcm","version":"1.0.0-ballot2","fhirVersion":"5.0.0","canonical":"http://hl7.org/fhir/uv/ibcm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.ibcm-1.0.0-ballot2.tgz","date":"2024-08-09T18:00:57.000Z"},{"name":"hl7.fhir.uv.application-feature","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/application-feature","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.application-feature-1.0.0-ballot.tgz","date":"2024-08-13T18:00:57.000Z"},{"name":"hl7.fhir.uv.termchangeset","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/termchangeset","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.termchangeset-1.0.0-ballot.tgz","date":"2024-08-14T18:00:58.000Z","description":"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 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). (built Wed, Aug 14, 2024 14:50+0000+00:00)"},{"name":"hl7.fhir.uv.lab-report","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/lab-report","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.lab-report-1.0.0-ballot.tgz","date":"2024-08-15T00:00:58.000Z","description":"This guide describes how the Laboratory Report can be represented in the UV REALM. (built Wed, Aug 14, 2024 20:47+0000+00:00)"},{"name":"fhir.nhs.uk.wayfinder","version":"1.0.3","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.nhs.uk.wayfinder","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.nhs.uk.wayfinder-1.0.3.tgz","date":"2024-08-15T16:03:58.000Z","description":"Wayfinder Aggregator"},{"name":"uk.nhsdigital.medicines.r4.test","version":"2.8.21-prerelease","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/uk.nhsdigital.medicines.r4.test","kind":"fhir.ig","url":"https://packages2.fhir.org/web/uk.nhsdigital.medicines.r4.test-2.8.21-prerelease.tgz","date":"2024-08-19T11:37:46.000Z","description":"Electronic Prescription Service"},{"name":"hl7.fhir.uv.shorthand","version":"3.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/shorthand","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.shorthand-3.0.0.tgz","date":"2024-08-19T18:01:00.000Z","description":"Describes FHIR Shorthand (FSH), a domain-specific language (DSL) for defining the content of FHIR Implementation Guides (IG). (built Mon, Aug 19, 2024 15:16+0000+00:00)"},{"name":"package.test.new","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/package.test.new","kind":"fhir.ig","url":"https://packages2.fhir.org/web/package.test.new-2.0.0.tgz","date":"2024-08-23T13:37:25.000Z","description":"Daniel Labs Project"},{"name":"nhs.fhir.lv.vvis","version":"0.1.0-test","fhirVersion":"4.3.0","canonical":"http://simplifier.net/packages/nhs.fhir.lv.vvis","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nhs.fhir.lv.vvis-0.1.0-test.tgz","date":"2024-08-30T07:15:56.000Z","description":"For testing purposes"},{"name":"hl7.fhir.be.core","version":"2.1.2","fhirVersion":"4.0.1","canonical":"https://www.ehealth.fgov.be/standards/fhir/core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.be.core-2.1.2.tgz","date":"2024-09-02T18:01:06.000Z","description":"eHealth Platform Federal Core Profiles (built Fri, Aug 30, 2024 17:07+0200+02:00)"},{"name":"shin.interconnect","version":"1.0.0-beta","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/shin.interconnect","kind":"fhir.ig","url":"https://packages2.fhir.org/web/shin.interconnect-1.0.0-beta.tgz","date":"2024-09-04T20:40:50.000Z","description":"This is a project for the Surescripts Health Information Network Interconnect FHIR guide."},{"name":"hl7.fhir.us.core.v311","version":"3.1.1","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/core/v311","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.core.v311-3.1.1.tgz","date":"2024-09-05T12:00:44.000Z"},{"name":"hl7.fhir.uv.subscriptions-backport","version":"1.2.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/subscriptions-backport","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.subscriptions-backport-1.2.0-ballot.tgz","date":"2024-09-05T12:00:55.000Z","description":"The Subscription R5 Backport Implementation Guide enables servers running versions of FHIR earlier than R5 to implement a subset of R5 Subscriptions in a standardized way. (built Mon, Dec 18, 2023 22:14+0000+00:00)"},{"name":"tewhatuora.digitaltooling","version":"0.0.11","fhirVersion":"4.0.1","canonical":"https://fhir-ig.digital.health.nz/hnz-digital-tooling","kind":"fhir.ig","url":"https://packages2.fhir.org/web/tewhatuora.digitaltooling-0.0.11.tgz","date":"2024-09-05T12:02:18.000Z","description":"FHIR profiles used in FHIR Publishing processes within Health New Zealand Te Whatu Ora (built Wed, Aug 28, 2024 21:00+0000+00:00)"},{"name":"de.dktk.oncology","version":"1.8.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.dktk.oncology","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.dktk.oncology-1.8.0.tgz","date":"2024-09-13T13:48:34.000Z","description":"Data model of the German Cancer Consortium (DKTK) and the Comprehensive Cancer Center Network"},{"name":"acme.fsh.example","version":"0.0.3-demo","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/acme.fsh.example","kind":"fhir.ig","url":"https://packages2.fhir.org/web/acme.fsh.example-0.0.3-demo.tgz","date":"2024-09-16T07:37:59.000Z","description":"Example project from ACME Corp on using FHIR Shorthand/sushi"},{"name":"de.uk-koeln.nngm.form","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.uk-koeln.nngm.form","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.uk-koeln.nngm.form-1.0.0.tgz","date":"2024-09-17T12:24:49.000Z","description":"Profiles for the nNGM project (nngm.de)"},{"name":"hl7.terminology.r4b","version":"6.0.2","fhirVersion":"4.3.0","canonical":"http://terminology.hl7.org","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.terminology.r4b-6.0.2.tgz","date":"2024-09-21T12:01:11.000Z","description":"Defines and exposes all HL7 terminologies managed through the unified terminology governance process (built Sun, Jul 21, 2024 00:17-0600-06:00)"},{"name":"globalalliant.us.eom","version":"1.0.1-rc2","fhirVersion":"4.0.1","canonical":"https://globalalliantinc.com/enhancing-oncology-model","kind":"fhir.ig","url":"https://packages2.fhir.org/web/globalalliant.us.eom-1.0.1-rc2.tgz","date":"2024-09-23T20:27:42.000Z","description":"Aligning mCODE cancer data with the CMS Enhancing Oncology Model to support PP1 data collection"},{"name":"ca.on.oh.corhealth","version":"0.2.0-beta","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.oh.corhealth","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.oh.corhealth-0.2.0-beta.tgz","date":"2024-09-26T21:14:15.000Z","description":"The Ontario CorHealth FHIR implementation guide will provide business and technical information"},{"name":"signal.core.r4","version":"0.2.10","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/signal.core.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/signal.core.r4-0.2.10.tgz","date":"2024-09-30T08:42:10.000Z","description":"Signal Managed Service Organization"},{"name":"ca.on.oh-olis","version":"2.0.0-0.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.oh-olis","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.oh-olis-2.0.0-0.0.1.tgz","date":"2024-10-01T19:29:48.000Z","description":"Ontario Laboratory Information System - R4"},{"name":"rlfhir.lab","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/rlfhir.lab","kind":"fhir.ig","url":"https://packages2.fhir.org/web/rlfhir.lab-1.0.0.tgz","date":"2024-10-02T13:11:56.000Z","description":"Progetto FHIR per Regione Lombardia LAB"},{"name":"smart.who.int.ts","version":"0.1.0","fhirVersion":"4.0.1","canonical":"http://smart.who.int/ts","kind":"fhir.ig","url":"https://packages2.fhir.org/web/smart.who.int.ts-0.1.0.tgz","date":"2024-10-04T18:02:07.000Z","description":"An empty Implementation Guide to be used as a starting point for building SMART Guidelines Implementation Guides (built Fri, Oct 4, 2024 14:19+0000+00:00)"},{"name":"org.sql-on-fhir.ig","version":"2.0.0","fhirVersion":"5.0.0","canonical":"https://sql-on-fhir.org/ig","kind":"fhir.ig","url":"https://packages2.fhir.org/web/org.sql-on-fhir.ig-2.0.0.tgz","date":"2024-10-09T00:00:00.000Z","description":"A specification for defining portable views of FHIR data that can be easily queried using tools such as SQL. (built Wed, Oct 9, 2024 15:17+1000+10:00)"},{"name":"rapportendoscopiequebec.test","version":"0.0.69","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/rapportendoscopiequebec.test","kind":"fhir.ig","url":"https://packages2.fhir.org/web/rapportendoscopiequebec.test-0.0.69.tgz","date":"2024-10-09T13:27:31.000Z","description":"Envoi du rapport d’endoscopie au dépôt provincial"},{"name":"nrlf.poc","version":"1.0.4","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/nrlf.poc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nrlf.poc-1.0.4.tgz","date":"2024-10-10T13:43:03.000Z","description":"NRL Futures API POC"},{"name":"ans.fhir.fr.telesurveillance","version":"0.1.0","fhirVersion":"4.0.1","canonical":"https://interop.esante.gouv.fr/ig/fhir/telesurveillance","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ans.fhir.fr.telesurveillance-0.1.0.tgz","date":"2024-10-11T06:01:26.000Z"},{"name":"fhir.r4.wales.stu1","version":"1.2.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.r4.wales.stu1","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.r4.wales.stu1-1.2.1.tgz","date":"2024-10-14T08:49:30.000Z","description":"1.2.1 of the NHS Wales FHIR assets"},{"name":"first.package","version":"0.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/first.package","kind":"fhir.ig","url":"https://packages2.fhir.org/web/first.package-0.0.1.tgz","date":"2024-10-15T14:26:13.000Z","description":"Testing simplifier"},{"name":"hl7.fhir.us.pdmp","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/pdmp","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.pdmp-1.0.0.tgz","date":"2024-10-16T00:00:47.000Z","description":"US Prescription Drug Monitoring Program (PDMP) FHIR IG (built Tue, Oct 15, 2024 18:20+0000+00:00)"},{"name":"sunwayhie.r4","version":"0.0.1-preview-1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/sunwayhie.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/sunwayhie.r4-0.0.1-preview-1.tgz","date":"2024-10-18T03:51:53.000Z","description":"SunWay HIE Profiles for POC"},{"name":"tewhatuora.hip-core","version":"1.9.2","fhirVersion":"4.0.1","canonical":"https://fhir-ig.digital.health.nz/HIP-FHIR-Common","kind":"fhir.ig","url":"https://packages2.fhir.org/web/tewhatuora.hip-core-1.9.2.tgz","date":"2024-10-22T06:03:26.000Z","description":"Common terminology used by HIP FHIR services (built Tue, Oct 22, 2024 03:28+0000+00:00)"},{"name":"nictiz.fhir.nl.r4.outcomebasedcare","version":"1.0.0-alpha.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/nictiz.fhir.nl.r4.outcomebasedcare","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nictiz.fhir.nl.r4.outcomebasedcare-1.0.0-alpha.1.tgz","date":"2024-10-22T15:00:46.000Z","description":"Contains the conformance resources and Questionnaires for Outcome Based Care."},{"name":"fhir.resources","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.resources","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.resources-1.0.0.tgz","date":"2024-10-23T23:53:49.000Z","description":"Cardiovascular Risk Assessment"},{"name":"test.v202111591","version":"0.0.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/test.v202111591","kind":"fhir.ig","url":"https://packages2.fhir.org/web/test.v202111591-0.0.2.tgz","date":"2024-10-31T10:53:00.000Z","description":"test"},{"name":"kl.dk.fhir.prevention","version":"2.1.1","fhirVersion":"4.0.1","canonical":"http://fhir.kl.dk/prevention","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kl.dk.fhir.prevention-2.1.1.tgz","date":"2024-10-31T18:01:30.000Z","description":"Danish municipalities implementation guide for reporting §119 disease prevention and health promotion (built Mon, Jun 24, 2024 12:34+0200+02:00)"},{"name":"kl.dk.fhir.children","version":"2.1.0","fhirVersion":"4.0.1","canonical":"http://fhir.kl.dk/children","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kl.dk.fhir.children-2.1.0.tgz","date":"2024-11-01T00:01:40.000Z","description":"KLChildren contains the specification for reporting data from the Danish health promotion and disease prevention program for children in Denmark (Sundhedsplejen). Data is reported to FK Gateway (built Thu, Oct 31, 2024 20:27+0100+01:00)"},{"name":"kl.dk.fhir.gateway","version":"1.2.0","fhirVersion":"4.0.1","canonical":"http://fhir.kl.dk/gateway","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kl.dk.fhir.gateway-1.2.0.tgz","date":"2024-11-01T00:01:40.000Z"},{"name":"kl.dk.fhir.rehab","version":"2.2.0","fhirVersion":"4.0.1","canonical":"http://fhir.kl.dk/rehab","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kl.dk.fhir.rehab-2.2.0.tgz","date":"2024-11-01T00:01:40.000Z","description":"Danish municipalities implementation guide for §140 rehabilitation reporting (built Thu, Oct 31, 2024 15:36+0100+01:00)"},{"name":"healthhub.fhir.dk.core","version":"1.0.24","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/healthhub.fhir.dk.core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/healthhub.fhir.dk.core-1.0.24.tgz","date":"2024-11-01T13:28:25.000Z","description":"PLSP Health Hub"},{"name":"nictiz.fhir.nl.r4.cio","version":"1.0.0-beta.5","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/nictiz.fhir.nl.r4.cio","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nictiz.fhir.nl.r4.cio-1.0.0-beta.5.tgz","date":"2024-11-04T14:08:36.000Z","description":"This project contains HL7 FHIR compliant profiles for the information standard Contraindications and hypersensitivities."},{"name":"hl7.fhir.us.cqfmeasures","version":"5.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/cqfmeasures","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.cqfmeasures-5.0.0.tgz","date":"2024-11-05T00:00:44.000Z","description":"The Fast Healthcare Interoperability Resource (FHIR) Quality Measure Implementation Guide (this IG) describes an approach to representing Quality Measures (QMs) using the FHIR Clinical Reasoning Module and Clinical Quality Language (CQL) in the US Realm. However, this Implementation Guide can be usable for multiple use cases across domains, and much of the content is likely to be usable outside the US Realm. (built Mon, Nov 4, 2024 20:07+0000+00:00)"},{"name":"de.gevko.dev.tetvz","version":"1.1.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gevko.dev.tetvz","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gevko.dev.tetvz-1.1.2.tgz","date":"2024-11-07T09:28:23.000Z","description":"Put a description here"},{"name":"gen.kanta.r4","version":"0.9.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/gen.kanta.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/gen.kanta.r4-0.9.1.tgz","date":"2024-11-12T13:42:40.000Z","description":"Tämä opas sisältää eri Kanta-palveluissa käytettävät yhteiset FHIR- ja REST-rajapintamääärittelyt "},{"name":"kbv.basis.ressources.only","version":"1.7.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/kbv.basis.ressources.only","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kbv.basis.ressources.only-1.7.0.tgz","date":"2024-11-12T14:10:59.000Z","description":"KBV-Basis-Profile V 1.6.0"},{"name":"de.gevko.evo.ekb","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gevko.evo.ekb","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gevko.evo.ekb-1.0.0.tgz","date":"2024-11-12T14:32:53.000Z","description":"Umsetzung der elektronischen Heilmittelverordnung"},{"name":"kbv.basis.with.expansion","version":"1.7.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/kbv.basis.with.expansion","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kbv.basis.with.expansion-1.7.0.tgz","date":"2024-11-12T15:18:32.000Z","description":"KBV-Basis-Profile V 1.6.0"},{"name":"test.module3.v2","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://interopsante.org","kind":"fhir.ig","url":"https://packages2.fhir.org/web/test.module3.v2-2.0.0.tgz","date":"2024-11-12T18:35:19.000Z","description":"Projet de test Formation FHIR"},{"name":"kbv.basis.terminology.with.expansion","version":"1.7.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/kbv.basis.terminology.with.expansion","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kbv.basis.terminology.with.expansion-1.7.0.tgz","date":"2024-11-13T08:14:35.000Z","description":"KBV-Basis-Profile-Terminologie"},{"name":"hl7.fhir.be.infsec","version":"1.2.0","fhirVersion":"4.0.1","canonical":"https://www.ehealth.fgov.be/standards/fhir/infsec","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.be.infsec-1.2.0.tgz","date":"2024-11-15T06:01:45.000Z","description":"eHealth Platform Federal infsec Profiles (built Tue, Nov 12, 2024 09:23+0100+01:00)"},{"name":"hl7.fhir.us.core.v610","version":"6.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/core/v610","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.core.v610-6.1.0.tgz","date":"2024-11-19T00:00:44.000Z"},{"name":"ihe.iti.fais","version":"1.0.0","fhirVersion":"4.0.1","canonical":"https://profiles.ihe.net/ITI/FAIS","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.iti.fais-1.0.0.tgz","date":"2024-11-22T06:01:44.000Z","description":"The Finance and Insurance Service (FAIS) stores, categorizes, and facilitates the administration of centralized claims and finance data for patient care. The service receives claims/financial data from Point of Service applications (including financing applications acting as a point of service interface outside of other PoS systems) and curates the management of them. (built Wed, Nov 13, 2024 10:49-0600-06:00)"},{"name":"cce.fhir","version":"0.1.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/cce.fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/cce.fhir-0.1.0.tgz","date":"2024-11-25T14:13:58.000Z","description":"Sample FHIR profiles for CCE sites to follow."},{"name":"ca.on.oh-cms","version":"1.0.2-alpha1.0.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.oh-cms","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.oh-cms-1.0.2-alpha1.0.2.tgz","date":"2024-11-25T16:24:35.000Z","description":"Based on FHIR Cast"},{"name":"cce.fhir.full","version":"0.2.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/cce.fhir.full","kind":"fhir.ig","url":"https://packages2.fhir.org/web/cce.fhir.full-0.2.0.tgz","date":"2024-11-26T09:39:10.000Z","description":"Sample FHIR profiles for CCE sites to follow."},{"name":"de.gkvsv.evp","version":"1.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gkvsv.evp","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gkvsv.evp-1.0.1.tgz","date":"2024-11-27T15:04:20.000Z","description":"elekronischer Versorgungsplan Pflege"},{"name":"eu.miabis.r4","version":"0.2.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/eu.miabis.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/eu.miabis.r4-0.2.0.tgz","date":"2024-11-29T14:04:10.000Z","description":"Minimum Information About BIobank data Sharing"},{"name":"portuguese.use-cases.guide","version":"1.0.1","fhirVersion":"4.3.0","canonical":"http://simplifier.net/packages/portuguese.use-cases.guide","kind":"fhir.ig","url":"https://packages2.fhir.org/web/portuguese.use-cases.guide-1.0.1.tgz","date":"2024-11-29T16:14:21.000Z","description":"Portuguese FHIR R4B Profiles"},{"name":"hl7.fhir.cl.minsal.eis","version":"0.1.0","fhirVersion":"4.0.1","canonical":"https://interoperabilidad.minsal.cl/fhir/ig/eis","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.cl.minsal.eis-0.1.0.tgz","date":"2024-11-30T00:17:02.000Z","description":"Esta Guía de Estandares de Informacionde Salud desarrolla el Decreto Excento 231 del DEIS que reemplaza la norma técnica 820, y tiene como finalidad determinar compatibilidad de esta con el estándar FHIR (built Fri, Nov 29, 2024 11:08-0300-03:00)"},{"name":"smart.who.int.ig-starter-kit","version":"2.0.0","fhirVersion":"5.0.0","canonical":"http://smart.who.int/ig-starter-kit","kind":"fhir.ig","url":"https://packages2.fhir.org/web/smart.who.int.ig-starter-kit-2.0.0.tgz","date":"2024-11-30T12:16:37.000Z","description":"SMART Guidelines Starter Kit with L2 and L3 SOP (built Sat, Nov 30, 2024 06:42+0000+00:00)"},{"name":"animals.core","version":"0.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/animals.core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/animals.core-0.0.1.tgz","date":"2024-12-02T16:02:13.000Z","description":"general implementation when patients are cats/dogs"},{"name":"ihe.pcc.odh","version":"1.0.0","fhirVersion":"4.0.1","canonical":"https://profiles.ihe.net/PCC/ODH","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.pcc.odh-1.0.0.tgz","date":"2024-12-05T18:01:48.000Z","description":"This IG covers the specific data that covers past or present jobs, usual work, employment status, retirement date and combat zone period for the subject. It also includes the past or present jobs and usual work of other household members. This IG is International scope. (built Wed, Dec 4, 2024 15:44-0600-06:00)"},{"name":"sand.box","version":"0.8.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/sand.box","kind":"fhir.ig","url":"https://packages2.fhir.org/web/sand.box-0.8.1.tgz","date":"2024-12-06T22:01:04.000Z","description":"This is a sandbox project "},{"name":"implementation.guide.nhdr","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/implementation.guide.nhdr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/implementation.guide.nhdr-1.0.0.tgz","date":"2024-12-06T22:03:52.000Z","description":"DRAFT: Philippine CDI Implementation Guide for Integration with the National Health Data Repository (NHDR)"},{"name":"tw.cathay.fhir.imri","version":"1.0.0","fhirVersion":"4.0.1","canonical":"https://imri.cgh.org.tw/imri","kind":"fhir.ig","url":"https://packages2.fhir.org/web/tw.cathay.fhir.imri-1.0.0.tgz","date":"2024-12-12T12:08:12.000Z","description":"醫查實作指引"},{"name":"hl7.fhir.uv.cardx-htn-mng","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/cardx-htn-mng","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.cardx-htn-mng-1.0.0.tgz","date":"2024-12-12T18:00:40.000Z"},{"name":"hl7.fhir.uv.genomics-reporting","version":"3.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/genomics-reporting","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.genomics-reporting-3.0.0.tgz","date":"2024-12-13T00:00:41.000Z","description":"Guidelines for reporting of clinical genomics results using HL7 FHIR. (built Thu, Dec 12, 2024 20:34+0000+00:00)"},{"name":"ihe.iti.scheduling","version":"1.0.0","fhirVersion":"4.0.1","canonical":"https://profiles.ihe.net/ITI/Scheduling","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.iti.scheduling-1.0.0.tgz","date":"2024-12-13T00:01:39.000Z","description":"The IHE FHIR Scheduling Profile is a specification providing FHIR APIs and guidance for access to and booking of appointments for patients by both patient and practitioner end users. This specification is based on FHIR Version 4 and specifically the Schedule, Slot, and Appointment resources, and on the previous work of the [Argonaut Project](https://fhir.org/guides/argonaut/scheduling/release1/). (built Thu, Dec 12, 2024 08:19-0600-06:00)"},{"name":"de.medizininformatikinitiative.kerndatensatz.mikrobiologie","version":"2025.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.medizininformatikinitiative.kerndatensatz.mikrobiologie","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.medizininformatikinitiative.kerndatensatz.mikrobiologie-2025.0.1.tgz","date":"2024-12-15T13:40:53.000Z","description":"Medizininformatik Initiative - Modul Mikrobiologie"},{"name":"hl7.fhir.us.ccda","version":"2.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/ccda","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.ccda-2.0.0-ballot.tgz","date":"2024-12-18T00:00:39.000Z","description":"Consolidated CDA (C-CDA) is one of the most widely implemented implementation guides for CDA and covers a significant scope of clinical care. Its target of the 'common/essential' elements of healthcare is closely aligned with FHIR's focus on the '80%'. There is significant interest in industry and government in the ability to interoperate between CDA and FHIR and C-CDA is a logical starting point. Implementers and regulators have both expressed an interest in the ability to map between FHIR and C-CDA.\n\nThis Implementation Guide (IG) defines a series of FHIR profiles on the Composition resource to represent the various document types in C-CDA. This release does not directly map every C-CDA template to FHIR profiles, rather tries to accomplish the C-CDA use case using Composition resource profiles created under this project (the equivalent of Level 2 CDA documents), and begins by linking to the profiles created under the US Core project for any coded entries that would normally be included in C-CDA sections. To have a simpler, more streamlined standard that reuses existing work and focuses on the 80% that implementers actually need in production systems, the resources of US Core represents a portion of the 80% needed for coded entries for coded entries of CCD, Care Plan & Discharge Summary).\n\nThe Composition profiles in this IG do not require coded data in any section. This is a departure from C-CDA, which requires coded data for Problems, Results, Medications, etc. This departure is intentional, as the C-CDA requirement for one or more coded entries in these sections resulted in some very complicated workarounds using nullFlavors to handle the fact that sometimes a patient is not on any medications, or has no current problems. In general, FHIR takes the approach that if something is nullable, it should simply be optional to ease the burden on implementers, thus C-CDA on FHIR does not require any coded entries, but rather uses the \"required if known\" approach, meaning that if an implementer's system has data for a section that requires data under Meaningful Use, they need to send it, but if they have no data there is no need for a null entry.\n\nWe encourage feedback on these Composition profiles, and the general approach to the project as a whole. We also encourage implementers who wish to see more of the coded data from C-CDA mapped to FHIR to comment on the US Core project and make their requests known there. Once US Core creates new profiles, this project can reference them.\n\n### Scope\n\nTo represent Consolidated CDA Templates for Clinical Notes (C-CDA) 2.1 templates using FHIR profiles.\n\nThis first stage of the project defines all the C-CDA document-level profiles on the Composition resource and contained sections.\n\nAny coded data used by sections will be represented using relevant U.S. Core FHIR profiles where they exist. FHIR profiles defined by other work groups or unconstrained FHIR resources may also be referenced if no appropriate US Core Profile exist.\n\nFor further information see the C-CDA specification here: http://www.hl7.org/implement/standards/product_brief.cfm?product_id=408. (built Tue, Dec 17, 2024 21:40+0000+00:00)"},{"name":"who.ddcc","version":"1.0.1","fhirVersion":"4.0.1","canonical":"http://smart.who.int/ddcc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/who.ddcc-1.0.1.tgz","date":"2024-12-18T18:02:16.000Z","description":"This WHO Digital Documentation of COVID-19 Certificates (DDCC) Implementation Guide details how to use Health Level 7 (HL7) Fast Healthcare Interoperability Resources (FHIR) for consistent digital representation of COVID-19 certificates and interoperability. (built Wed, Dec 18, 2024 16:39+0100+01:00)"},{"name":"ch.fhir.ig.ch-atc","version":"3.3.0","fhirVersion":"4.0.1","canonical":"http://fhir.ch/ig/ch-atc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ch.fhir.ig.ch-atc-3.3.0.tgz","date":"2024-12-19T00:01:36.000Z","description":"Implementation Guide for CH ATC (Audit Trail Consumption) (built Wed, Dec 18, 2024 12:52+0000+00:00)"},{"name":"ca.on.oh.mha.pds","version":"2.0.0-alpha-preview-0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.oh.mha.pds","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.oh.mha.pds-2.0.0-alpha-preview-0.1.tgz","date":"2024-12-23T19:54:21.000Z","description":"Ontario Mental Health and Addictions Provincial Data Set 2.0"},{"name":"com.hl7.cyb.r5","version":"0.1.11","fhirVersion":"5.0.0","canonical":"http://simplifier.net/packages/com.hl7.cyb.r5","kind":"fhir.ig","url":"https://packages2.fhir.org/web/com.hl7.cyb.r5-0.1.11.tgz","date":"2024-12-30T07:45:27.000Z","description":"cyb-自定义IG实施指南"},{"name":"ca.on.oh.mha-pds","version":"0.9.0-alpha-1.9.7.38","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.oh.mha-pds","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.oh.mha-pds-0.9.0-alpha-1.9.7.38.tgz","date":"2025-01-10T15:45:43.000Z","description":"Ontario Mental Health and Addictions Provincial Data Set"},{"name":"acme.base.r4","version":"4.1.7","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/acme.base.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/acme.base.r4-4.1.7.tgz","date":"2025-01-14T13:05:17.000Z","description":"ACME Base Profiles R4"},{"name":"test.prova","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/test.prova","kind":"fhir.ig","url":"https://packages2.fhir.org/web/test.prova-1.0.0.tgz","date":"2025-01-16T10:52:27.000Z","description":"Progetto per attività di test "},{"name":"vzvz.fhir.aof","version":"0.15.0","fhirVersion":"4.3.0","canonical":"http://simplifier.net/packages/vzvz.fhir.aof","kind":"fhir.ig","url":"https://packages2.fhir.org/web/vzvz.fhir.aof-0.15.0.tgz","date":"2025-01-28T11:15:34.000Z","description":"FHIR artifacts for Aorta on FHIR"},{"name":"hl7.at.fhir.core.r4","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.at/fhir/HL7ATCoreProfiles/4.0.1","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.at.fhir.core.r4-2.0.0.tgz","date":"2025-01-28T12:03:53.000Z","description":"An Implementation Guide for the HL7® Austria FHIR® Core Profiles. (built Mon, Jan 27, 2025 10:36+0000+00:00)"},{"name":"hl7.at.fhir.core.r5","version":"2.0.0","fhirVersion":"5.0.0","canonical":"http://hl7.at/fhir/HL7ATCoreProfiles/5.0.0","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.at.fhir.core.r5-2.0.0.tgz","date":"2025-01-28T12:03:54.000Z","description":"An Implementation Guide for the HL7® Austria FHIR® Core Profiles. (built Fri, Jan 24, 2025 14:19+0000+00:00)"},{"name":"ca.on.oh-ereferral-econsult","version":"0.12.0-projectathon1.0.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.oh-ereferral-econsult","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.oh-ereferral-econsult-0.12.0-projectathon1.0.2.tgz","date":"2025-01-28T22:29:18.000Z","description":"Ontario-specific business use cases and content"},{"name":"ca.on.oh.erec","version":"0.12.0-projectathon1.0.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.oh.erec","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.oh.erec-0.12.0-projectathon1.0.2.tgz","date":"2025-01-28T22:30:36.000Z","description":"Ontario eReferral-eConsult Implementation Guide\r\n\r\n\r\nClick https://simplifier.net/guide/ca-on-ereferral-r4-iguide/Index?version=0.11.1 to access the most recently published IG (v0.11.1)\r\n\r\n"},{"name":"de.netzwerk-universitaetsmedizin.ceosys.template","version":"0.1.2","fhirVersion":"4.0.1","canonical":"https://www.netzwerk-universitaetsmedizin.de/fhir/ceosys/ig-template-ceosys","kind":"fhir.template","url":"https://packages2.fhir.org/web/de.netzwerk-universitaetsmedizin.ceosys.template-0.1.2.tgz","date":"2025-01-31T18:03:46.000Z","description":"CEOsys template extension for FHIR IG"},{"name":"de.biv-ot.everordnungabgabedaten","version":"0.1.0-preview","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.biv-ot.everordnungabgabedaten","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.biv-ot.everordnungabgabedaten-0.1.0-preview.tgz","date":"2025-02-01T23:12:29.000Z","description":"Abgabedaten-Modell für die eVerordnung Hilfsmittel"},{"name":"hl7.fhir.dk.smart","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.dk/fhir/smart","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.dk.smart-1.0.0.tgz","date":"2025-02-02T00:01:45.000Z","description":"Guidelines for using the SMART App Launch mechanism in Denmark. (built Sat, Feb 1, 2025 20:09+0100+01:00)"},{"name":"smart.who.int.dak-immz","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://smart.who.int/dak-immz","kind":"fhir.ig","url":"https://packages2.fhir.org/web/smart.who.int.dak-immz-1.0.0.tgz","date":"2025-02-04T18:03:43.000Z","description":"SMART DAK for Immunizations (built Mon, Feb 3, 2025 11:15+0000+00:00)"},{"name":"nxh.fhir.r4","version":"0.0.0-beta.20","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/nxh.fhir.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nxh.fhir.r4-0.0.0-beta.20.tgz","date":"2025-02-06T07:08:19.000Z","description":"Technical profiles used by nexuzhealth for the import and export of data. "},{"name":"ans.fhir.fr.cdl","version":"3.0.0","fhirVersion":"4.0.1","canonical":"https://interop.esante.gouv.fr/ig/fhir/cdl","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ans.fhir.fr.cdl-3.0.0.tgz","date":"2025-02-07T06:01:35.000Z"},{"name":"de.gematik.dev.epa","version":"1.0.5-alpha.3","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gematik.dev.epa","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.dev.epa-1.0.5-alpha.3.tgz","date":"2025-02-07T13:10:43.000Z","description":"ePA Common"},{"name":"ans.fr.nos","version":"1.5.0","fhirVersion":"4.0.1","canonical":"https://interop.esante.gouv.fr/ig/nos","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ans.fr.nos-1.5.0.tgz","date":"2025-02-12T06:01:40.000Z","description":"Les nomenclatures des objets de Sante (built Tue, Feb 11, 2025 10:50+0000+00:00)"},{"name":"acme.cowboy.fsh","version":"0.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/acme.cowboy.fsh","kind":"fhir.ig","url":"https://packages2.fhir.org/web/acme.cowboy.fsh-0.0.1.tgz","date":"2025-02-12T15:10:57.000Z","description":"A cowboy and his favorite hat, in FHIR Shorthand"},{"name":"ca.bc.bcy-ids","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.bc.bcy-ids","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.bc.bcy-ids-1.0.0.tgz","date":"2025-02-12T22:21:16.000Z","description":"PHSA - BC and Yukon Immunization Distribution Service (IDS)"},{"name":"cezih.hr.condition-management","version":"0.2.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/cezih.hr.condition-management","kind":"fhir.ig","url":"https://packages2.fhir.org/web/cezih.hr.condition-management-0.2.1.tgz","date":"2025-02-13T13:42:55.000Z","description":"Ovaj vodič za implementaciju integracijskog sučelja opisuje funkcionalnosti usluge za upravljanje slučajevima."},{"name":"t.est-project2052","version":"1.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/t.est-project2052","kind":"fhir.ig","url":"https://packages2.fhir.org/web/t.est-project2052-1.0.1.tgz","date":"2025-02-18T07:40:33.000Z","description":"test for learning"},{"name":"hl7.fhir.uv.vhdir","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/vhdir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.vhdir-1.0.0.tgz","date":"2025-02-18T18:00:48.000Z","description":"This is a Healthedata1 sandbox for creation of resources and examples (built Tue, Feb 18, 2025 15:14+0000+00:00)"},{"name":"ca.argentixinfo.howtopub","version":"1.1.0","fhirVersion":"4.0.1","canonical":"http://argentixinfo.com/ig/howtopub","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.argentixinfo.howtopub-1.1.0.tgz","date":"2025-02-21T12:02:17.000Z","description":"A Guide to HL7 IG Publisher's -go-publish feature (built Thu, Feb 20, 2025 21:17-0800-08:00)"},{"name":"hl7.fhir.ca.baseline","version":"1.2.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/ca/baseline/ImplementationGuide/hl7.fhir.ca.baseline","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.ca.baseline-1.2.0.tgz","date":"2025-02-21T20:03:57.000Z","description":"Canadian Baseline (CA Baseline) FHIR Profiles\r\n\r\nThe goal of the CA Baseline specification is to expose the implementation guide author community and vendor community to a set of profiles that identify the data elements, code systems and value sets that are commonly present across Canada for a given FHIR resource (e.g., patient, medication, etc.) regardless of use case, jurisdiction or implementation."},{"name":"fhir.ca-bc.client","version":"1.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.ca-bc.client","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.ca-bc.client-1.0.1.tgz","date":"2025-02-22T00:05:38.000Z","description":"The BC Provincial Client Registry is the registry of the Patients in British Columbia."},{"name":"hl7.fhir.be.nihdi-terminology","version":"1.0.0","fhirVersion":"4.0.1","canonical":"https://www.ehealth.fgov.be/standards/fhir/nihdi-terminology","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.be.nihdi-terminology-1.0.0.tgz","date":"2025-02-22T12:01:43.000Z","description":"Terminology managed by the NIHDI (RIZIV/INAMI) in various publications, such as https://www.inami.fgov.be/SiteCollectionDocuments/instructions_facturation_electronique.pdf (built Mon, Feb 17, 2025 19:20+0100+01:00)"},{"name":"laniado.test.fhir.r4","version":"0.1.92","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/laniado.test.fhir.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/laniado.test.fhir.r4-0.1.92.tgz","date":"2025-02-23T10:31:10.000Z","description":"Laniado Hospital Test Project"},{"name":"fhir.r4.ukcore.stu2","version":"2.0.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.r4.ukcore.stu2","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.r4.ukcore.stu2-2.0.2.tgz","date":"2025-02-24T13:06:40.000Z","description":"UK Core FHIR profiles and Assets"},{"name":"cce.fhir.minimal","version":"0.4.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/cce.fhir.minimal","kind":"fhir.ig","url":"https://packages2.fhir.org/web/cce.fhir.minimal-0.4.0.tgz","date":"2025-02-24T16:16:20.000Z","description":"Sample FHIR profiles for CCE sites to follow."},{"name":"eu.epi.february2025b","version":"1.0.0","fhirVersion":"5.0.0","canonical":"http://simplifier.net/packages/eu.epi.february2025b","kind":"fhir.ig","url":"https://packages2.fhir.org/web/eu.epi.february2025b-1.0.0.tgz","date":"2025-02-25T16:19:13.000Z","description":"Validate against EMA QRD business rules"},{"name":"de.gematik.dev.ti","version":"1.0.0-alpha.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gematik.dev.ti","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.dev.ti-1.0.0-alpha.2.tgz","date":"2025-02-27T09:00:30.000Z","description":"[Development] TI Common"},{"name":"fhir.ca-bc.provider","version":"1.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.ca-bc.provider","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.ca-bc.provider-1.0.1.tgz","date":"2025-02-28T18:07:01.000Z","description":"The BC Provider Location Registry is providing a reliable registry of the Practitioner, Organization"},{"name":"hl7.fhir.core","version":"4.1.0","fhirVersion":"4.1.0","canonical":"http://hl7.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.core-4.1.0.tgz","date":"2025-03-03T18:00:06.000Z","description":"FHIR Core - Group package for Release 4B Ballot #1"},{"name":"hl7.fhir.us.davinci-drug-formulary","version":"2.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-drug-formulary","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-drug-formulary-2.1.0.tgz","date":"2025-03-03T18:00:46.000Z","description":"DaVinci Payer Data Exchange (PDex) US Drug Formulary\" (built Wed, Feb 26, 2025 17:11+0000+00:00)"},{"name":"hl7.fhir.us.davinci-pdex-plan-net","version":"1.2.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-pdex-plan-net","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-pdex-plan-net-1.2.0.tgz","date":"2025-03-03T18:00:51.000Z","description":"Da Vinci PDex Plan Net (built Tue, Feb 25, 2025 19:12+0000+00:00)"},{"name":"hl7.fhir.uv.fhir-for-fair","version":"0.1.0","fhirVersion":"4.1.0","canonical":"http://hl7.org/fhir/uv/fhir-for-fair","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.fhir-for-fair-0.1.0.tgz","date":"2025-03-03T18:01:19.000Z","description":"The FHIR for FAIR - FHIR Implementation Guide aims to provide guidance on how HL7 FHIR can be used for supporting FAIR health data implementation and assessment. (built Sun, Dec 5, 2021 00:01+0000+00:00)"},{"name":"ihe.pcc.maps.us","version":"1.0.0-comment","fhirVersion":"4.0.1","canonical":"https://profiles.ihe.net/us/PCC/mAPS","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.pcc.maps.us-1.0.0-comment.tgz","date":"2025-03-03T18:02:55.000Z","description":"Mobile Antepartum Summary is a content profile that defines the structure for the aggregation of significant events, diagnoses, and plans of care derived from the visits over the course of an antepartum episode. (built Tue, Jun 4, 2024 16:23-0500-05:00)"},{"name":"ihe.pcc.qedm","version":"3.0.0-comment1","fhirVersion":"4.0.1","canonical":"https://profiles.ihe.net/PCC/QEDm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.pcc.qedm-3.0.0-comment1.tgz","date":"2025-03-03T18:02:56.000Z","description":"The Query for Existing Data for Mobile Profile (QEDm) supports dynamic queries for clinical data elements, including observations, allergy and intolerances, problems, diagnostic results, medications, immunizations, procedures, encounters and provenance by making the information widely available to other systems within and across enterprises to support provision of better clinical care. It defines a transaction used to query a list of specific data elements, persisted as FHIR resources. (built Mon, Aug 5, 2024 09:48-0500-05:00)"},{"name":"silth.fhir.th.extensions","version":"0.1.0","fhirVersion":"4.3.0","canonical":"https://fhir-ig.sil-th.org/th/extensions","kind":"fhir.ig","url":"https://packages2.fhir.org/web/silth.fhir.th.extensions-0.1.0.tgz","date":"2025-03-03T18:03:08.000Z","description":"An extension registry which an be cited by FHIR artifacts (built Sat, Sep 9, 2023 14:19+0700+07:00)"},{"name":"silth.fhir.th.claimcon","version":"0.1.2","fhirVersion":"4.3.0","canonical":"https://fhir-ig.sil-th.org/th/claimcon","kind":"fhir.ig","url":"https://packages2.fhir.org/web/silth.fhir.th.claimcon-0.1.2.tgz","date":"2025-03-03T18:03:08.000Z","description":"A representation of Thailand's public health claim dataset in FHIR format (built Sat, Sep 9, 2023 15:29+0700+07:00)"},{"name":"silth.fhir.th.mophpc1","version":"0.1.1","fhirVersion":"4.3.0","canonical":"https://fhir-ig.sil-th.org/th/mophpc1","kind":"fhir.ig","url":"https://packages2.fhir.org/web/silth.fhir.th.mophpc1-0.1.1.tgz","date":"2025-03-03T18:03:09.000Z","description":"An implementation guide for adopting FHIR for health information exchange in 43files-plus format. (built Sat, Sep 9, 2023 14:50+0700+07:00)"},{"name":"smart.who.int.dak-ccc","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://smart.who.int/dak-ccc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/smart.who.int.dak-ccc-1.0.0.tgz","date":"2025-03-03T18:03:31.000Z","description":"CCC DAK (built Mon, Jul 15, 2024 07:07+0000+00:00)"},{"name":"smart.who.int.dak-tb","version":"1.0.1","fhirVersion":"4.0.1","canonical":"http://smart.who.int/dak-tb","kind":"fhir.ig","url":"https://packages2.fhir.org/web/smart.who.int.dak-tb-1.0.1.tgz","date":"2025-03-03T18:03:32.000Z","description":"TB DAK (built Wed, Jul 17, 2024 05:57+0000+00:00)"},{"name":"smart.who.int.ips-pilgrimage","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://smart.who.int/ips-pilgrimage","kind":"fhir.ig","url":"https://packages2.fhir.org/web/smart.who.int.ips-pilgrimage-1.0.0.tgz","date":"2025-03-03T18:03:32.000Z","description":"An Implementation Guide which describes how to utilize GDHCN and IPS for verifiable health documents during pilgrimage. (built Thu, Apr 25, 2024 17:22+0000+00:00)"},{"name":"de.netzwerk-universitaetsmedizin.ebm-cpg","version":"1.2.0","fhirVersion":"5.0.0","canonical":"https://www.netzwerk-universitaetsmedizin.de/fhir/cpg-on-ebm-on-fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.netzwerk-universitaetsmedizin.ebm-cpg-1.2.0.tgz","date":"2025-03-04T12:03:45.000Z"},{"name":"bbmri.cz","version":"0.1.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/bbmri.cz","kind":"fhir.ig","url":"https://packages2.fhir.org/web/bbmri.cz-0.1.0.tgz","date":"2025-03-11T10:16:46.000Z","description":"Showcase of Extension of MIABIS on FHIR project"},{"name":"ha.ho.he","version":"0.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ha.ho.he","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ha.ho.he-0.0.1.tgz","date":"2025-03-11T12:40:47.000Z","description":"Testprojekt_BSC"},{"name":"ca.clicsante.base","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://documentation.clicsante.ca/fhir/base","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.clicsante.base-1.0.0.tgz","date":"2025-03-19T12:02:13.000Z"},{"name":"hl7.fhir.uv.ipa","version":"1.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/ipa","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.ipa-1.1.0.tgz","date":"2025-03-19T18:00:39.000Z","description":"This IG describes how an application acting on behalf of a patient can access information about the patient from an clinical records system using a FHIR based API. The clinical records system may be supporting a clinical care provider (e.g. a hospital, or a general practitioner), or a health data exchange, including a national health record system. (built Wed, Mar 19, 2025 14:34+0000+00:00)"},{"name":"tw.cohesion.fhir.clinemr","version":"1.0.0","fhirVersion":"4.0.1","canonical":"https://fhir.cohesiondata.com/clinemr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/tw.cohesion.fhir.clinemr-1.0.0.tgz","date":"2025-03-20T10:16:26.000Z","description":"診所門診病摘實作指引"},{"name":"test.public.project.pvt.package","version":"0.0.4","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/test.public.project.pvt.package","kind":"fhir.ig","url":"https://packages2.fhir.org/web/test.public.project.pvt.package-0.0.4.tgz","date":"2025-03-24T12:13:30.000Z","description":"test"},{"name":"kanta.sosiaalihuolto.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/kanta.sosiaalihuolto.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kanta.sosiaalihuolto.r4-1.0.0.tgz","date":"2025-03-25T11:41:26.000Z","description":"Kanta sosiaalihuolto R4, sosiaalihuollon luovutusilmoitus. "},{"name":"ca.on.oh-erec","version":"0.12.1-alpha1.0.3","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.oh-erec","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.oh-erec-0.12.1-alpha1.0.3.tgz","date":"2025-03-25T19:59:13.000Z","description":"Ontario eReferral-eConsult Specification\r\n\r\nClick https://simplifier.net/guide/ca-on-ereferral-r4-iguide/Index?version=0.12.0 to access the most recently published IG (v0.12.0)\r\n\r\nClick https://simplifier.net/guide/ca-on-ereferral-r4-iguide/Index?version=0.11.1 to access v0.11.1\r\n\r\n"},{"name":"hl7.fhir.no.basis","version":"2.2.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/hl7.fhir.no.basis","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.no.basis-2.2.2.tgz","date":"2025-03-27T12:23:40.000Z","description":"Norwegian base profiles for R4\r\n\r\n## Version 2.2\r\n\r\nFeature release to add no-basis-Appointment and no-basis-AppointmentResponse profile definition (issue #97).\r\nIncluding bugfixes:\r\n\r\nissue #87 HNR, lokale hjelpenummer\r\nissue #99 Wrong canonical on NoBasisRelatedPersonReference\r\nissue #97 Removed deprecated proposal for no-basis-Encounter\r\n"},{"name":"hl7.fhir.uv.ebm","version":"1.0.0-ballot2","fhirVersion":"6.0.0-ballot2","canonical":"http://hl7.org/fhir/uv/ebm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.ebm-1.0.0-ballot2.tgz","date":"2025-03-28T12:00:00.000Z"},{"name":"hl7.fhir.us.pacio-toc","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/pacio-toc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.pacio-toc-1.0.0-ballot.tgz","date":"2025-03-28T18:00:38.000Z","description":"Implementation Guide for exchanging Transitions of Care minimum data set for patients transitioning between health organizations. (built Fri, Mar 28, 2025 13:46+0000+00:00)"},{"name":"fhir.hrsa.uds-plus","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.org/guides/hrsa/uds-plus","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.hrsa.uds-plus-2.0.0.tgz","date":"2025-03-28T18:00:44.000Z","description":"A brief description of what udsplus is about (probably the same text as in your readme) (built Fri, Mar 28, 2025 22:44+1100+11:00)"},{"name":"hl7.fhir.us.pco","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/pco","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.pco-1.0.0-ballot.tgz","date":"2025-03-29T00:00:39.000Z","description":"Person-Centered Outcomes (PCO) FHIR Implementation Guide (built Fri, Mar 28, 2025 21:02+0000+00:00)"},{"name":"hl7.fhir.us.womens-health-registries","version":"0.2.0-withdrawal","fhirVersion":"4.0.0","canonical":"http://hl7.org/fhir/us/womens-health-registries","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.womens-health-registries-0.2.0-withdrawal.tgz","date":"2025-03-29T00:00:41.000Z"},{"name":"de.abda.erezeptabgabedatenbasis","version":"1.5.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.abda.erezeptabgabedatenbasis","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.abda.erezeptabgabedatenbasis-1.5.0.tgz","date":"2025-03-31T10:25:35.000Z","description":"Basis-Profile für die Abgabedaten im eRezept-Kontext"},{"name":"de.abda.erezeptabgabedaten","version":"1.5.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.abda.erezeptabgabedaten","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.abda.erezeptabgabedaten-1.5.0.tgz","date":"2025-03-31T10:53:21.000Z","description":"eRezeptAbgabedatensatz 1.5.0 zum 01.10.2025"},{"name":"acme.usecase.r4","version":"2.0.0-alpha","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/acme.usecase.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/acme.usecase.r4-2.0.0-alpha.tgz","date":"2025-03-31T13:45:45.000Z","description":"A project from ACME Corp for a specific use case, building on the R4 ACME Base Profiles"},{"name":"hl7.fhir.r6.corexml","version":"6.0.0-ballot3","fhirVersion":"6.0.0-ballot3","canonical":"http://hl7.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.r6.corexml-6.0.0-ballot3.tgz","date":"2025-04-01T01:28:44.000Z","description":"FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (XML) (built Tue, Apr 1, 2025 12:16+1100+11:00)"},{"name":"uk.nhsdigital.r4","version":"2.11.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/uk.nhsdigital.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/uk.nhsdigital.r4-2.11.0.tgz","date":"2025-04-01T10:22:51.000Z","description":"NHS (England) National Services Implementation Guide"},{"name":"hl7.fhir.eu.laboratory","version":"0.1.1","fhirVersion":"4.0.1","canonical":"http://hl7.eu/fhir/laboratory","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.eu.laboratory-0.1.1.tgz","date":"2025-04-01T12:01:41.000Z","description":"This guide describes how the Laboratory Report can be represented in the European REALM. (built Tue, Mar 25, 2025 12:00+0100+01:00)"},{"name":"ca.on.oh-dhdr","version":"4.0.2-alpha1.0.6","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.oh-dhdr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.oh-dhdr-4.0.2-alpha1.0.6.tgz","date":"2025-04-01T15:07:43.000Z","description":"Implementation Guide for the Ontario DHDR HL7 FHIR 4.0.2"},{"name":"ezprava.fhir","version":"1.0.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ezprava.fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ezprava.fhir-1.0.2.tgz","date":"2025-04-02T09:23:00.000Z","description":"Reprezentace DASTA 4 pomocí FHIR."},{"name":"smart.who.int.base","version":"0.2.0","fhirVersion":"4.0.1","canonical":"http://smart.who.int/base","kind":"fhir.ig","url":"https://packages2.fhir.org/web/smart.who.int.base-0.2.0.tgz","date":"2025-04-02T12:01:54.000Z","description":"Base SMART Guidelines implementation guide to be used as the base dependency for all SMART Guidelines IGs (built Wed, Apr 2, 2025 12:10+0200+02:00)"},{"name":"il.dqa.fhir.r4","version":"0.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/il.dqa.fhir.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/il.dqa.fhir.r4-0.0.1.tgz","date":"2025-04-02T14:40:27.000Z","description":"Data Quality Assurance "},{"name":"dqa.outburn.r4","version":"0.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/dqa.outburn.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/dqa.outburn.r4-0.0.1.tgz","date":"2025-04-02T15:07:29.000Z","description":"Data Quality Assurance - Outburn"},{"name":"synapxe.rcm.snapshots","version":"1.0.0","fhirVersion":"5.0.0","canonical":"http://simplifier.net/packages/synapxe.rcm.snapshots","kind":"fhir.ig","url":"https://packages2.fhir.org/web/synapxe.rcm.snapshots-1.0.0.tgz","date":"2025-04-03T05:46:23.000Z","description":"Synapxe RCM Project"},{"name":"de.abda.erezeptabgabedatenpkv","version":"1.3.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.abda.erezeptabgabedatenpkv","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.abda.erezeptabgabedatenpkv-1.3.1.tgz","date":"2025-04-03T07:26:37.000Z","description":"Der PKV-Abgabedatensatz enthält die notwendigen Informationen für die Abrechnung einer elektronischen Arzneimittelverordnung (E-Rezept) für Privatversicherte durch eine Apotheke."},{"name":"on.accdr.pkg","version":"0.9.24-beta","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/on.accdr.pkg","kind":"fhir.ig","url":"https://packages2.fhir.org/web/on.accdr.pkg-0.9.24-beta.tgz","date":"2025-04-03T17:58:04.000Z","description":"eHealth Ontario "},{"name":"hl7.fhir.uv.phr","version":"1.0.0-ballot2","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/phr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.phr-1.0.0-ballot2.tgz","date":"2025-04-03T18:00:40.000Z","description":"Guidance on how to create longitudinal personal health records using FHIR. Exporting, file formats, patient examples, and more. (built Thu, Apr 3, 2025 14:45+0000+00:00)"},{"name":"hl7.fhir.uv.cow","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/cow","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.cow-1.0.0-ballot.tgz","date":"2025-04-07T18:00:42.000Z","description":"An Implementation Guide providing the foundational guidance for order-based workflow FHIR interoperability (built Mon, Apr 7, 2025 15:35+0000+00:00)"},{"name":"rki.emiga.orgv","version":"1.1.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/rki.emiga.orgv","kind":"fhir.ig","url":"https://packages2.fhir.org/web/rki.emiga.orgv-1.1.1.tgz","date":"2025-04-08T10:03:23.000Z","description":"EMIGA Organizationsverzeichnis MVP Version"},{"name":"fhir.workshop.test","version":"1.9.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.workshop.test","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.workshop.test-1.9.1.tgz","date":"2025-04-08T14:30:30.000Z","description":"Test"},{"name":"fhir.workshop.cshtml","version":"10.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.workshop.cshtml","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.workshop.cshtml-10.0.1.tgz","date":"2025-04-08T14:34:14.000Z","description":"Test"},{"name":"hl7.fhir.us.davinci-pr","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-pr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-pr-1.0.0.tgz","date":"2025-04-08T18:00:42.000Z"},{"name":"hl7.fhir.us.davinci-alerts","version":"1.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-alerts","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-alerts-1.1.0.tgz","date":"2025-04-09T00:00:43.000Z","description":"This implementation guide describes a method for the communication of relevant notifications to support the real-time exchange of information that impacts patient care and value based or risk based services. Providers and Payers may need to be notified when activities occur that impact a patient’s care. This may be as traditional as a notification of an admission or transfer to or discharge from a care setting. It also includes notifications about changes in treatment such as a new or different medication, or changes in patient status like a new diagnosis. These notifications provide information that can improve care management and care coordination as well as act as the trigger for quality programs and other patient focused activities (for example, risk adjustment). By allowing the patient’s healthcare providers to be better informed and able to take actions and intervene earlier, the twin goals of better patient care and reduced cost of care may be met. (built Tue, Apr 8, 2025 18:46+0000+00:00)"},{"name":"hl7.fhir.us.bfdr","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/bfdr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.bfdr-2.0.0.tgz","date":"2025-04-10T00:00:48.000Z"},{"name":"hl7.fhir.us.codex-radiation-therapy","version":"2.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/codex-radiation-therapy","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.codex-radiation-therapy-2.0.0-ballot.tgz","date":"2025-04-10T00:00:49.000Z","description":"CodeX™ Radiation Therapy is an initiative intended to assemble a core set of structured data elements for radiation therapy electronic health records. (built Tue, Apr 9, 2024 14:34+0000+00:00)"},{"name":"hl7.fhir.us.davinci-cdex","version":"2.1.0-snapshot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-cdex","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-cdex-2.1.0-snapshot.tgz","date":"2025-04-10T00:00:52.000Z","description":"This IG provides detailed guidance that helps implementers use FHIR-based interactions to support specific exchanges of clinical data between providers and payers (or other providers). (built Sat, Sep 28, 2024 07:21-0400-04:00)"},{"name":"hl7.fhir.us.eltss","version":"2.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/eltss","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.eltss-2.0.0-ballot.tgz","date":"2025-04-10T00:01:11.000Z","description":"Provides guidance to US Realm implementers to use the FHIR for implementing access and exchange Electronic Long-Term Services and Supports (eLTSS) Dataset data elements (built Fri, Dec 15, 2023 20:54+0000+00:00)"},{"name":"hl7.fhir.us.home-lab-report","version":"1.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/home-lab-report","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.home-lab-report-1.1.0.tgz","date":"2025-04-10T00:01:15.000Z"},{"name":"hl7.fhir.us.insurance-card","version":"1.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/insurance-card","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.insurance-card-1.1.0.tgz","date":"2025-04-10T00:01:19.000Z","description":"CARIN Digital Insurance Card (built Tue, Apr 16, 2024 17:25+0000+00:00)"},{"name":"hl7.fhir.us.mcc","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/mcc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.mcc-1.0.0.tgz","date":"2025-04-10T00:01:20.000Z","description":"### Introduction\nThis HL7® Multiple Chronic Condition (MCC) Care Plan Implementation Guide (IG) defines FHIR R4 profiles, structures, extensions, transactions and value sets needed to represent, query for, and exchange Care Plan information. It defines how to represent coded content used to support the care planning activities focusing on the needs of patients with multiple chronic conditions. This initial version focuses on Chronic Kidney Disease Type 2 diabetes mellitus, common cardiovascular disease (hypertension, ischemic heart disease and heart failure), chronic pain and Long Covid.The profiles defined within this IG were based on data elements of importance identified by the National Institute of Health's (NIH) National Institute of Diabetes and Digestive and Kidney Disease technical expert panels.\n\nA Care Plan is a consensus-driven dynamic plan that represents a patient’s and Care Team Members’ prioritized concerns, goals, planned and actual interventions and the resultant care outcomes. It serves as a blueprint shared by all Care Team Members (including the patient, their caregivers, and providers), to guide the patient’s care. A Care Plan integrates multiple interventions proposed by multiple providers and disciplines for multiple conditions. A Care Plan may represent one or more Care Plans and serves to reconcile and resolve conflicts between the various plans developed for a specific patient by different providers. It supports the following use cases:\n \n1. Query for patient data across providers and compile into a consolidated care plan representation.\n2. Encourage capture of and communication of a patient's health concerns and related goals, interventions, and outcomes.\n3. Gather and aggregate patient data for uses beyond the point of care (e.g. public health, population health, quality measurement, risk adjustment, quality improvement, and research.)\n\nThis FHIR IG addresses the needs of multiple audiences. It provides technical artifacts that assist programmers when implementing standards-based FHIR application program interfaces (APIs) for specific purposes. It provides instructive material that explains how FHIR is used to accomplish specific use cases. It also provides general information that helps business analysts and technology decision-makers understand the use cases and benefits associated with achieving specific data exchange capabilities. A FHIR IG is as much a business planning tool as it is an educational resource and a technical specification.\n\n### How to Read this Guide and Cautions\nThis Guide is divided into several pages which are listed in the navigation bar at the top each page. The contents of each page are listed in a yellow \"Contents\" box at the top right of each page.\n\n### Value Set Library\n\nRather than creating nearly 1000 profiles covering important concepts for chronic care coordination for use within the MCC FHIR Care Plan profile, we have created 21 foundation profiles which conform to US Core Profiles (where available) adding constraints or extensions pertinent to their representation within a dynamic FHIR care plan and then creating libraries of value sets pertinent to the base profiles for representing chronic conditions, and their related interventions and goals and outcomes. \nThis project has built and houses its value sets in the National Library of Medicine's (NLM) Value Set Authority Center (VSAC). The value sets are not directly bound within the foundation profiles, but value set library pages are provided with links to the value sets in VSAC and descriptions of where within the profile each value set may be used. Because the value sets are housed in VSAC, it is necessary for implementation sites to obtain a free (for the US) UMLS license. In addition, HL7 FHIR Policies requiring everything to be open source in all realms, may present some implementation validation issues when interfacing with a value set housed in VSAC. This IG will provide guidance for this issue.\n\n### History of the Care Plan and Electronic Care Plans\n\nThe concept of a care plan began as a teaching tool for nursing students to research and document the medical conditions their patients had and identify the associated nursing care and family support needed. This was documented in a structured paper format that fostered the nursing process. The nursing process is the identification of health concerns and related goals, and the interventions needed to meet those goals and then evaluating the meeting of those goals – the outcomes. Over the years, the care plan evolved from a student teaching tool to something required for most patients in some format by various regulating or certifying bodies, and further, from a nursing care based plan, to an interdisciplinary patient focused tool.\n\nMost major vendors have electronic Care Plan modules, but the degree to which the modules are implemented and actively used is unknown. Few, if any, are exchange standards ready or mapped to exchange standards. The first HL7 standard representing Care Plan was the C-CDA Care Plan document designed to represent an instance of an EHR Care Plan similar to the Continuity of Care (CCD) CDA. Many of the learnings and designs for the FHIR Care Plan Resource and this IG were derived from the C-CDA Care Plan. There is also an IHE [Dynamic Care Planning (DCP)](https://wiki.ihe.net/index.php/Dynamic_Care_Planning_(DCP)) that provides the structures and transactions for care planning, creating, updating and sharing Care Plans that meet the needs of many, such as providers, patients and payers.. The Office of the National Coordinator (ONC) has put into regulation requirements around goals and health concerns which can currently be met by free text. The Dynamic Care Planning (DCP) Profile provides leveraged FHIR Resources to provide the structures and transactions for care planning and sharing Care Plans that meet the needs of many, such as providers, patients and payers. The DCP profile leverages the FHIR Care Plan resource, but does not specify, describe or define the use of it for representing specific conditions or multiple conditions. We are unaware of any real world implementations of it at this time.\n\nWe believe that this IG will be the first fully defined HL7 FHIR IG leveraging the FHIR Care Plan resources as its backbone structure for representing a dynamic care plan and testing its ability to bring together aggregated patient care plan data including patient outcomes.\n\n### Project Overview\n\nMore than 25 percent of Americans have MCC, accounting for more than 65 percent of U.S. healthcare spending. These individuals have complex health needs handled by diverse providers, across multiple settings of care. As a result, their care is often fragmented, poorly coordinated, and inefficient. Therefore, data aggregation is particularly important and challenging for people with MCC. These challenges will increasingly strain the U.S. health system, with the aging of the U.S. population. Projections suggest numbers of adults aged 65 and older will more than double and numbers of those aged 85 and older will triple by 2050.\n \nCare plans are a prominent part of multifaceted, care coordination interventions that reduce mortality and hospitalizations and improve disease management and satisfaction. In addition, proactive care planning promotes person-centeredness, improves outcomes, and reduces the cost of care. By design, care plans take a patient-centered approach, both by making comprehensive health data available across providers and settings and through the incorporation of data elements that have not traditionally been included in health IT systems (e.g., social determinants of health SDOH, patient health and life goals, patient preferences). While Care Plans have been developed, they remain paper-based in many U.S. healthcare settings and are not standardized and interoperable across care settings when electronic. While care plans focused on a single disease or condition are unlikely to be tenable for patients with MCC or their providers, existing care plans infrequently address individuals with MCC. The development of care plans based on structured data has been proposed as a method for enabling electronic systems to pull together and share data elements automatically and dynamically. Such aggregated data would not only provide actionable information to identify and achieve health and wellness goals for individuals with MCC, but also would reduce missingness and improve quality of point-of-care data for use in pragmatic research.\n \nThe Fast Healthcare Interoperability Resources (FHIR) specification is an open-source standard for exchanging healthcare information electronically based on emerging industry approaches. The FHIR workflow specification includes a CarePlan request resource that may facilitate transfer of data for an e-care plan across healthcare settings. SMART (https://smarthealthit.org/) and SMART on FHIR standards include open specifications to integrate applications with health IT systems and may enable the development of an e-care plan application that can integrate with a variety of electronic health record (EHR) systems.\n\nInitiated by the National Institute of Diabetes and Digestive and Kidney Diseases (NIDDK), the multiple chronic conditions (MCC) electronic care (eCare) Plan Project aims to develop, test, and pilot an interoperable eCare plan that will facilitate aggregation and sharing of critical patient-centered data across home, community, clinic, and research-based settings for persons with MCC, including chronic kidney disease (CKD), type 2 diabetes mellitus (T2D), cardiovascular disease (CVD), pain with opioid use disorder (OUD), and long COVID. \n\nThe HL7-based activities of the MCC eCare Plan Project include:\n \n - Identified use cases to support the documentation and exchange of MCC eCare plan data within EHRs and related systems.\n - Identified, developed, and prioritized the necessary MCC data elements and clinical terminology standards and FHIR® mappings that will enable the standardized transfer of data across health settings.\n - Develop, test, and ballot an HL7® Fast Health Interoperability Resources (FHIR®) Implementation Guide based on the defined use cases and MCC data elements.\n \nNon-HL7 related activities of the MCC eCare Plan project will be facilitated through the [AHRQ eCare Plan Project Confluence](https://ecareplan.ahrq.gov/collaborate):\n - The project includes the develoment and testing of an open-source clinician and patient facing SMART-on-FHIR eCare plan application for managing persons with MCC.\n\n#### Project Timelines\n - January 2024: A For comment ballot to gather community input prior to the formal STU Ballot\n - September 2024: Formal STU Ballot\n - May 2025 Formal HL7 Publication\n\n\n### Guidance\nThe guidance section provides general implementation guidance and best practices. It describes the relation to and reuse of the US Core Implementation Guide profiles and reuse of its conformance requirements and expectations for the servers and client applications. Vocabulary use and value set binding heuristics are described.\n\n#### Relationship to US Core\n\nThis Implementation Guide reuses US Core profiles either through direct use or by constraining select profiles for representation within a FHIR Care Plan profile. Where US Core does not have a profile or function that is needed for the use cases or data elements, the IG constrains or directly reuses other resources, or profiles defined in other FHIR IGs. \nThis guide will reuse the US Core Care Plan. However, the required US Core CarePlan.text and the required Care.Plan.category:AssessPlan may be limiting factors for this context of use: aggregation of multiple chronic condition care plans and the ability to query for structured data within a structured Care Plan. As such, we recommend adding additional Care Plan categories if deemed more informational to reflect multiple chronic condition care coordination and plans and to hard code “Multiple Chronic Condition Care Coordination Plan” at CarePlan.text\n\n\n##### General US Core IG Conformance\n\nThis guide will adhere to or build on US conformance requirements, most of its [General Guidance](https://www.hl7.org/fhir/us/core/general-guidance.html), and its [Capability Statements](https://www.hl7.org/fhir/us/core/capstatements.html) where applicable. \n\n##### Provenance\n\nThis IG recommends implementers adhere to guidelines and definitions provided in US Core’s [Basic Provenance Guidance](https://www.hl7.org/fhir/us/core/basic-provenance.html). \n\n##### Must Support\n\nThis IG will adhere to the US Core [Must Support](https://www.hl7.org/fhir/us/core/general-guidance.html#must-support) concept and rules.\n\n### Acknowledgements\nThis Implementation Guide was made possible through the visionary leadership of the [National Institute of Diabetes and Digestive and Kidney Diseases (NIDDK) ](https://www.niddk.nih.gov/)and the [Agency for Healthcare Research and Quality (AHRQ) ](https://www.ahrq.gov/)with funding from the [Office of the Assistant Secretary for Planning and Evaluation (ASPE)](https://aspe.hhs.gov/collaborations-committees-advisory-groups/os-pcortf/explore-portfolio). The joint NIDDK-AHRQ project team can be found [here](https://cmext.ahrq.gov/confluence/display/EC/Project+Team). We would also like to thank the many clinicians, patients, caregivers, researchers, advocates, and subject matter experts who served on our [Technical Expert Panels](https://cmext.ahrq.gov/confluence/display/EC/Technical+Expert+Panels) and [Contract Monitoring Board ](https://cmext.ahrq.gov/confluence/display/EC/Contract+Monitoring+Board) for their time, insight, and support. \n\nThis Implementation Guide was created under the supervision and review of the [HL7 Patient Care Work Group](https://www.hl7.org/Special/committees/patientcare/index.cfm). This is the HL7 project page for the [Multiple Chronic Conditions e-Care Project.](https://confluence.hl7.org/display/PC/Multiple+Chronic+Conditions+%28MCC%29+eCare+Plan)\n\n (built Tue, Aug 13, 2024 20:59+0000+00:00)"},{"name":"hl7.fhir.us.mcode","version":"3.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/mcode","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.mcode-3.0.0.tgz","date":"2025-04-10T00:01:23.000Z","description":"mCODE™ (short for Minimal Common Oncology Data Elements) is an initiative intended to assemble a core set of structured data elements for oncology electronic health records. (built Wed, Oct 25, 2023 23:16+0000+00:00)"},{"name":"hl7.fhir.us.registry-protocols","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/registry-protocols","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.registry-protocols-1.0.0.tgz","date":"2025-04-10T00:01:34.000Z","description":"The IG demonstrates a process and workflow to support the needs of clinical registries to define how registry submissions can be automatically extracted from multiple data sources and combined into a registry submission. (built Tue, Nov 14, 2023 18:48+0000+00:00)"},{"name":"hl7.fhir.us.vr-common-library","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/vr-common-library","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.vr-common-library-2.0.0.tgz","date":"2025-04-10T00:01:38.000Z"},{"name":"hl7.fhir.us.vrdr","version":"3.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/vrdr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.vrdr-3.0.0.tgz","date":"2025-04-10T00:01:41.000Z"},{"name":"hl7.fhir.uv.cpg","version":"2.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/cpg","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.cpg-2.0.0-ballot.tgz","date":"2025-04-10T00:01:47.000Z","description":"Implementation guidance for creating Clinical Practice Guidelines with formal artifacts to facilitate sharing and implementation of the guideline (built Tue, Dec 19, 2023 19:42+0000+00:00)"},{"name":"hl7.fhir.uv.ehrs-rle","version":"1.1.0-ballot","fhirVersion":"5.0.0","canonical":"http://hl7.org/fhir/uv/ehrs-rle","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.ehrs-rle-1.1.0-ballot.tgz","date":"2025-04-10T00:01:57.000Z","description":"EHRS Functional Model - Record Lifecycle Events - FHIR Implementation Guide (built Wed, Mar 29, 2023 18:54+0000+00:00)"},{"name":"hl7.fhir.uv.ihe-sdc-ecc","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/ihe-sdc-ecc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.ihe-sdc-ecc-1.0.0.tgz","date":"2025-04-10T00:02:03.000Z","description":"Integrating the Healthcare Enterprise (IHE) Structured Data Capture (SDC) on FHIR uses a form-driven workflow to capture and transmit encoded data by creating FHIR Observations (built Tue, Dec 12, 2023 21:56+0000+00:00)"},{"name":"hl7.fhir.uv.smart-app-launch","version":"2.2.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/smart-app-launch","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.smart-app-launch-2.2.0-ballot.tgz","date":"2025-04-10T00:02:13.000Z"},{"name":"de.gematik.erezept-patientenrechnung.r4","version":"1.1.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gematik.erezept-patientenrechnung.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.erezept-patientenrechnung.r4-1.1.0.tgz","date":"2025-04-10T13:30:52.000Z","description":"Abrechnungsinformationen des E-Rezeptes für den Patienten"},{"name":"hl7.fhir.us.ndh","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/ndh","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.ndh-1.0.0.tgz","date":"2025-04-10T18:00:50.000Z"},{"name":"ans.fhir.fr.annuaire","version":"1.1.0","fhirVersion":"4.0.1","canonical":"https://interop.esante.gouv.fr/ig/fhir/annuaire","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ans.fhir.fr.annuaire-1.1.0.tgz","date":"2025-04-15T06:01:40.000Z","description":"Ressources de conformité basées sur le modèle d'exposition de l'Annuaire Santé. (built Mon, Apr 14, 2025 13:04+0000+00:00)"},{"name":"medmij.dental.care.r4","version":"1.0.0-alpha.3","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/medmij.dental.care.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/medmij.dental.care.r4-1.0.0-alpha.3.tgz","date":"2025-04-15T10:58:11.000Z","description":"MedMij Dental Care 1.0.0-alpha.3"},{"name":"cp.test.project.v1-0","version":"1.0.1-beta","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/cp.test.project.v1-0","kind":"fhir.ig","url":"https://packages2.fhir.org/web/cp.test.project.v1-0-1.0.1-beta.tgz","date":"2025-04-16T10:05:32.000Z","description":"This is a test project and a test package"},{"name":"hl7.fhir.uv.cds-hooks-library","version":"1.0.1","fhirVersion":"4.0.1","canonical":"http://cds-hooks.hl7.org/hooks","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.cds-hooks-library-1.0.1.tgz","date":"2025-04-18T12:00:56.000Z","description":"CDS Hooks describes a \"hook\"-based pattern for invoking decision support from within a clinician's workflow. The CDS Hooks Hook Library defines hooks standardized across the community. (built Wed, Mar 12, 2025 17:00+1100+11:00)"},{"name":"ontariomicdrfhirimplementationguide-0.10.00","version":"0.9.14","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ontariomicdrfhirimplementationguide-0.10.00","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ontariomicdrfhirimplementationguide-0.10.00-0.9.14.tgz","date":"2025-04-22T18:57:38.000Z","description":"OH MI FHIR IG package for internal testing"},{"name":"fhir.test.package","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.test.package","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.test.package-1.0.0.tgz","date":"2025-04-23T18:16:39.000Z","description":"test"},{"name":"e44.evo13","version":"1.1.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/e44.evo13","kind":"fhir.ig","url":"https://packages2.fhir.org/web/e44.evo13-1.1.0.tgz","date":"2025-04-24T08:49:17.000Z","description":"Profile für die eVO13 (Heilmittelverordnung Muster 13)"},{"name":"fhirtest.project","version":"0.1.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhirtest.project","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhirtest.project-0.1.0.tgz","date":"2025-04-29T08:18:35.000Z","description":"测试"},{"name":"test.project1","version":"0.2.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/test.project1","kind":"fhir.ig","url":"https://packages2.fhir.org/web/test.project1-0.2.0.tgz","date":"2025-04-29T08:32:48.000Z","description":"新增实施指南"},{"name":"myhealth.eu.fhir.laboratory","version":"0.1.1","fhirVersion":"4.0.1","canonical":"http://fhir.ehdsi.eu/laboratory","kind":"fhir.ig","url":"https://packages2.fhir.org/web/myhealth.eu.fhir.laboratory-0.1.1.tgz","date":"2025-04-29T18:06:37.000Z","description":"This guide describes how the Laboratory Report can be represented for the purpose of the MyHealthEu. (built Thu, Mar 20, 2025 14:16+0100+01:00)"},{"name":"test.pro","version":"0.3.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/test.pro","kind":"fhir.ig","url":"https://packages2.fhir.org/web/test.pro-0.3.0.tgz","date":"2025-04-30T02:19:45.000Z","description":"测试"},{"name":"fhir.project","version":"0.4.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.project","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.project-0.4.0.tgz","date":"2025-04-30T06:35:35.000Z","description":"测试"},{"name":"basisprofil.tiplu.de.r4.dev","version":"1.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/basisprofil.tiplu.de.r4.dev","kind":"fhir.ig","url":"https://packages2.fhir.org/web/basisprofil.tiplu.de.r4.dev-1.0.1.tgz","date":"2025-04-30T13:02:36.000Z","description":"Basisprofil Tiplu (DE) (R4) Dev-Stage"},{"name":"fhir.test","version":"0.0.1-alfa","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.test","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.test-0.0.1-alfa.tgz","date":"2025-05-02T16:25:39.000Z","description":"My online test"},{"name":"recon.v1","version":"0.1.0","fhirVersion":"5.0.0","canonical":"http://simplifier.net/packages/recon.v1","kind":"fhir.ig","url":"https://packages2.fhir.org/web/recon.v1-0.1.0.tgz","date":"2025-05-04T16:03:20.000Z","description":"Regulatory Content Exchange"},{"name":"test.circular.snapshot","version":"0.0.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/test.circular.snapshot","kind":"fhir.ig","url":"https://packages2.fhir.org/web/test.circular.snapshot-0.0.2.tgz","date":"2025-05-05T12:13:19.000Z","description":"test"},{"name":"hl7.eu.fhir.pcsp","version":"0.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.eu/fhir/ig/pcsp","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.eu.fhir.pcsp-0.1.0.tgz","date":"2025-05-06T12:02:12.000Z","description":"PanCareSurPass is an EU project aiming to conduct a robust assessment of the Cancer Survivorship Passport (SurPass). (built Thu, Jan 26, 2023 09:44+0100+01:00)"},{"name":"lin.project","version":"0.6.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/lin.project","kind":"fhir.ig","url":"https://packages2.fhir.org/web/lin.project-0.6.0.tgz","date":"2025-05-08T09:12:04.000Z","description":"新增实施指南"},{"name":"medcom.fhir.dk.xdsmetadata","version":"1.0.1","fhirVersion":"4.0.1","canonical":"http://medcomfhir.dk/ig/xdsmetadata","kind":"fhir.ig","url":"https://packages2.fhir.org/web/medcom.fhir.dk.xdsmetadata-1.0.1.tgz","date":"2025-05-08T12:02:15.000Z"},{"name":"nictiz.fhir.nl.stu3.bgz","version":"2.0.3-beta.2","fhirVersion":"3.0.1","canonical":"http://simplifier.net/packages/nictiz.fhir.nl.stu3.bgz","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nictiz.fhir.nl.stu3.bgz-2.0.3-beta.2.tgz","date":"2025-05-08T15:19:30.000Z","description":"Nictiz NL package of FHIR STU3 conformance resources for BgZ."},{"name":"vzvz.fhir.nl-vzvz-core","version":"0.3.3","fhirVersion":"4.3.0","canonical":"http://simplifier.net/packages/vzvz.fhir.nl-vzvz-core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/vzvz.fhir.nl-vzvz-core-0.3.3.tgz","date":"2025-05-12T13:35:22.000Z","description":"Generic FHIR artifacts for VZVZ projects"},{"name":"medcom.fhir.dk.conditionlist","version":"1.0.1","fhirVersion":"4.0.1","canonical":"http://medcomfhir.dk/ig/conditionlist","kind":"fhir.ig","url":"https://packages2.fhir.org/web/medcom.fhir.dk.conditionlist-1.0.1.tgz","date":"2025-05-13T12:02:20.000Z","description":"The MedCom ConditionList Implementation Guide includes profiles developed exchange a patients diagnoses in a FHIR-document (built Tue, May 13, 2025 06:30+0000+00:00)"},{"name":"ndhm.in","version":"6.5.0","fhirVersion":"4.0.1","canonical":"https://nrces.in/ndhm/fhir/r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ndhm.in-6.5.0.tgz","date":"2025-05-13T12:06:49.000Z"},{"name":"hl7.fhir.us.mdi","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/mdi","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.mdi-2.0.0.tgz","date":"2025-05-15T18:00:52.000Z"},{"name":"hl7.fhir.us.davinci-atr","version":"2.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-atr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-atr-2.1.0.tgz","date":"2025-05-17T00:00:50.000Z","description":"Exchange of member attribution list between payers and providers (built Fri, May 16, 2025 16:00+0000+00:00)"},{"name":"hl7.fhir.us.smp","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/smp","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.smp-1.0.0.tgz","date":"2025-05-17T00:00:55.000Z","description":"Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Fri, May 16, 2025 20:17+0000+00:00)"},{"name":"hl7.fhir.us.davinci-deqm","version":"5.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-deqm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-deqm-5.0.0.tgz","date":"2025-05-19T18:00:54.000Z"},{"name":"pharmacyeclaims.preview","version":"1.0.1-preview","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/pharmacyeclaims.preview","kind":"fhir.ig","url":"https://packages2.fhir.org/web/pharmacyeclaims.preview-1.0.1-preview.tgz","date":"2025-05-19T20:14:32.000Z","description":"DRAFT FHIR specification for submission of Pharmacy eClaims for adjudication in Canada. This FHIR standard is created by CPHA, CLHIA and various Canadian stakeholder groups including vendors, Pharmacy associations, Pharmacy Benefit Managers."},{"name":"pharmacyeclaim.two","version":"1.0.2-preview","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/pharmacyeclaim.two","kind":"fhir.ig","url":"https://packages2.fhir.org/web/pharmacyeclaim.two-1.0.2-preview.tgz","date":"2025-05-19T22:23:04.000Z","description":"DRAFT FHIR specification for submission of Pharmacy eClaims for adjudication in Canada. This FHIR standard is created by CPHA, CLHIA and various Canadian stakeholder groups including vendors, Pharmacy associations, Pharmacy Benefit Managers."},{"name":"hl7se.fhir.base","version":"1.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.se/fhir/ig/base","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7se.fhir.base-1.1.0.tgz","date":"2025-05-20T18:01:57.000Z","description":"Implementation Guide for Swedish Base Profiles (built Tue, May 20, 2025 13:02+0200+02:00)"},{"name":"ten.fhir","version":"0.7.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ten.fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ten.fhir-0.7.0.tgz","date":"2025-05-22T07:51:11.000Z","description":"该版本包含的内容如下：\r\n1、定义了Patient.gender不能为空。\r\n2、定义了Condition.code强制绑定本地的值域。\r\n3、扩展新增Patient.nation元素，用于表述民族，并要求强制绑定本地的值域。"},{"name":"tencent.project","version":"3.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/tencent.project","kind":"fhir.ig","url":"https://packages2.fhir.org/web/tencent.project-3.0.0.tgz","date":"2025-05-22T11:20:23.000Z","description":"该版本包含的内容如下： 1、定义了Patient.gender不能为空。 2、定义了Condition.code强制绑定本地的值域。 3、扩展新增Patient.nation元素，用于表述民族，并要求强制绑定本地的值域。\r\n\r\n"},{"name":"new.project20250522","version":"4.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/new.project20250522","kind":"fhir.ig","url":"https://packages2.fhir.org/web/new.project20250522-4.0.0.tgz","date":"2025-05-22T11:38:51.000Z","description":"该版本包含的内容如下： 1、定义了Patient.gender不能为空。 2、定义了Condition.code强制绑定本地的值域。 3、扩展新增Patient.nation元素，用于表述民族，并要求强制绑定本地的值域。\r\n\r\n"},{"name":"caseworks.mhaie","version":"0.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/caseworks.mhaie","kind":"fhir.ig","url":"https://packages2.fhir.org/web/caseworks.mhaie-0.0.1.tgz","date":"2025-05-22T22:06:13.000Z","description":"Caseworks MHAIE"},{"name":"ihe.iti.mcsd","version":"4.0.0","fhirVersion":"4.0.1","canonical":"https://profiles.ihe.net/ITI/mCSD","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.iti.mcsd-4.0.0.tgz","date":"2025-05-23T00:02:02.000Z","description":"The IHE Mobile Care Services Discovery (mCSD) IG provides a transaction for mobile and lightweight browser-based applications to find and update care services resources. (built Wed, May 21, 2025 13:38-0500-05:00)"},{"name":"ihe.pharm.mpd","version":"1.0.0-comment-2","fhirVersion":"5.0.0","canonical":"https://profiles.ihe.net/PHARM/MPD","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.pharm.mpd-1.0.0-comment-2.tgz","date":"2025-05-28T02:32:53.000Z","description":"ImplementationGuide for IHE Pharmacy Medication Prescription and Dispense (MPD) profile (built Tue, May 27, 2025 16:32+0200+02:00)"},{"name":"ihe.pharm.mpd.r4","version":"1.0.0-comment-2","fhirVersion":"4.0.1","canonical":"https://profiles.ihe.net/PHARM/MPD","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.pharm.mpd.r4-1.0.0-comment-2.tgz","date":"2025-05-28T18:02:08.000Z","description":"ImplementationGuide for IHE Pharmacy Medication Prescription and Dispense (MPD) profile (built Tue, May 27, 2025 16:32+0200+02:00)"},{"name":"de.nfdi4health.mds","version":"2.1.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.nfdi4health.mds","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.nfdi4health.mds-2.1.0.tgz","date":"2025-06-02T11:02:56.000Z","description":"NFDI4Health' Metadata Schema V3.3 for clinical, epidemiological and Public Health studies of the MDS version 3.3.1"},{"name":"asdmc.draft","version":"0.2.1","fhirVersion":"4.0.1","canonical":"http://fhir.ash-mc.health.gov.il/ImplementationGuide/il.fhir.r4.asdmc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/asdmc.draft-0.2.1.tgz","date":"2025-06-03T10:00:43.000Z","description":"draft no2"},{"name":"dvmd.kdl.r4","version":"2025.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/dvmd.kdl.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/dvmd.kdl.r4-2025.0.1.tgz","date":"2025-06-03T12:00:03.000Z","description":"Publikation der Terminologie-Ressourcen für die Nutzung der Klinische Dokumentenklassen-Liste (KDL) des DVMD\r\nVersion 2025\r\n\r\n"},{"name":"hl7.fhir.eu.hdr","version":"0.1.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.eu/fhir/hdr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.eu.hdr-0.1.0-ballot.tgz","date":"2025-06-03T18:02:28.000Z","description":"This implementation guide specifies the Hospital Discharge Report in the European context, as defined in eHN Hospital Discharge Report guidelines. (built Tue, Jun 3, 2025 12:48+0200+02:00)"},{"name":"ashmc.fhir","version":"0.2.0","fhirVersion":"4.0.1","canonical":"http://fhir.ashmc.co.il/ImplementationGuide/il.fhir.r4.ashmc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ashmc.fhir-0.2.0.tgz","date":"2025-06-04T11:23:47.000Z","description":"Assuta Ashdod FHIR Projects"},{"name":"hl7.fhir.uv.xver.r4","version":"0.0.1-snapshot-1","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/xver","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver.r4-0.0.1-snapshot-1.tgz","date":"2025-06-04T18:40:35.000Z","description":"All Cross Version Extensions for FHIR R4"},{"name":"hl7.fhir.uv.xver.r4b","version":"0.0.1-snapshot-1","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/xver","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver.r4b-0.0.1-snapshot-1.tgz","date":"2025-06-04T18:40:35.000Z","description":"All Cross Version Extensions for FHIR R4B"},{"name":"nictiz.fhir.nl.stu3.eoverdracht","version":"4.1.0-alpha.5","fhirVersion":"3.0.1","canonical":"http://simplifier.net/packages/nictiz.fhir.nl.stu3.eoverdracht","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nictiz.fhir.nl.stu3.eoverdracht-4.1.0-alpha.5.tgz","date":"2025-06-05T14:25:43.000Z","description":"Nictiz NL package of FHIR STU3 conformance resources for eOverdracht information standard. Includes dependency on Zib2017.\r\n\r\nHCIMs: https://zibs.nl/wiki/HCIM_Release_2017(EN)"},{"name":"de.gematik.elektronische-versicherungsbescheinigung","version":"1.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gematik.elektronische-versicherungsbescheinigung","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.elektronische-versicherungsbescheinigung-1.0.1.tgz","date":"2025-06-06T06:48:35.000Z","description":"Definition Versichertenstammdaten zum Versand via KIM für GKV VSDM Ersatzbescheinigung und PKV Online Check-In\r\n(INTERMEDIATE PACKAGE für Stichtag 30.09.2025)"},{"name":"hl7.fhir.eu.mpd","version":"0.1.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.eu/fhir/mpd","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.eu.mpd-0.1.0-ballot.tgz","date":"2025-06-06T12:02:37.000Z","description":"This guide describes how to represent in HL7 FHIR Prescription and Dispense in the European context (built Wed, Jun 4, 2025 09:09+0200+02:00)"},{"name":"hl7.fhir.eu.mpd-r5","version":"0.1.0-ballot","fhirVersion":"5.0.0","canonical":"http://hl7.eu/fhir/mpd-r5","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.eu.mpd-r5-0.1.0-ballot.tgz","date":"2025-06-06T12:02:37.000Z","description":"This guide describes how to represent in HL7 FHIR Prescription and Dispense in the European context (built Wed, Jun 4, 2025 20:58+0200+02:00)"},{"name":"vzvz.fhir.nl-vzvz-core-stu3","version":"1.0.1","fhirVersion":"3.0.1","canonical":"http://simplifier.net/packages/vzvz.fhir.nl-vzvz-core-stu3","kind":"fhir.ig","url":"https://packages2.fhir.org/web/vzvz.fhir.nl-vzvz-core-stu3-1.0.1.tgz","date":"2025-06-11T20:00:53.000Z","description":"nl-vzvz-core profiles in FHIR STU3"},{"name":"fi.kanta.gen.r4","version":"0.9.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fi.kanta.gen.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fi.kanta.gen.r4-0.9.2.tgz","date":"2025-06-12T08:55:15.000Z","description":"Tämä opas sisältää eri Kanta-palveluissa käytettävät yhteiset FHIR- ja REST-rajapintamääärittelyt "},{"name":"smart.who.int.dak-bds","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://smart.who.int/dak-bds","kind":"fhir.ig","url":"https://packages2.fhir.org/web/smart.who.int.dak-bds-1.0.0.tgz","date":"2025-06-14T12:04:37.000Z","description":"SMART Digital Adaptation Kit (DAK) for birth defects surveillance (BDS) (built Fri, Jun 13, 2025 13:35+0000+00:00)"},{"name":"rki.demis.ars","version":"1.0.0-rc.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/rki.demis.ars","kind":"fhir.ig","url":"https://packages2.fhir.org/web/rki.demis.ars-1.0.0-rc.2.tgz","date":"2025-06-15T09:16:52.000Z","description":"Antibiotika-Resistenz-Surveillance (ARS)"},{"name":"gdr.lab","version":"1.3.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/gdr.lab","kind":"fhir.ig","url":"https://packages2.fhir.org/web/gdr.lab-1.3.2.tgz","date":"2025-06-16T15:34:47.000Z","description":"Gestione digitale rete di laboratori"},{"name":"ca.on.oh-setp","version":"1.0.40","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.oh-setp","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.oh-setp-1.0.40.tgz","date":"2025-06-17T17:06:42.000Z","description":"The purpose of SETP is to improve surgical performance in Ontario through the measurement and report"},{"name":"hl7.fhir.us.davinci-pdex","version":"2.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-pdex","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-pdex-2.1.0.tgz","date":"2025-06-18T12:57:14.000Z","description":"This specification has undergone ballot and connectathon testing. It is expected to continue to evolve, possibly significantly, as part of that process.\nFeedback is welcome and may be submitted through the FHIR JIRA tracker indicating US Da Vinci PDex as the specification. If balloting on this IG, please submit your comments via the tracker and reference them in your ballot submission implementation guide.\n\nThis guide can be reviewed offline. Go to the Downloads section. Click on the link to download the full Implementation Guide as a zip file. Expand the zip file and use a web browser to launch the index.html file in the directory created by the zip extract process. External hyperlinks in the guide will not be available unless you have an active internet connection. \n\n[Financial Management](https://confluence.hl7.org/display/FM/Financial+Management+Home) is the Sponsoring Work Group for this Implementation Guide.\n\n**The Payer Data Exchange (PDex) Implementation Guide (IG) is provided for Payers/Health Plans to enable them to create a Member's Health History using clinical resources (based on US Core 3.1.1 and 6.1.0 Profiles based on FHIR R4) which can be understood by providers and, if they choose to, committed to their Electronic Medical Records (EMR) System.**\n\nThe PDex work group has made changes to the original version of the IG following the publication of the final CMS Interoperability and Patient Access Rule (CMS-9115_ and in STU 2.1 the IG has been expanded to meet the requirements of the CMS Prior Authorization Rule (CMS-0057).\n\nThis IG uses the same Member Health History \"payload\" for member-authorized exchange of information with other Health Plans, with Providers and with Third-Party Applications. It describes the interaction patterns that, when followed, allow the various parties involved in managing healthcare and payer data to more easily integrate and exchange data securely and effectively.\n\nThis IG covers the exchange of:\n- Claims-based information (without financials)\n- Clinical Information (such as Lab Results, Allergies and Conditions)\n- Prior Authorization information\n\nThis IG covers the exchange of this information using US Core and Da Vinci Health Record Exchange (HRex) Profiles. This superset of clinical profiles forms the Health Plan Member's Health History. \n\nThis IG covers the exchange of a Member's Health History in the following scenarios:\n- Provider requested exchange using SMART-on-FHIR Bulk exchange\n- Health Plan Exchange using SMART-on-FHIR\n- Member-authorized Health Plan to Health Plan exchange\n- Member-authorized Health Plan to Third-Party Application exchange\n\nThe latter two scenarios are provided to meet the requirements identified in the CMS Interoperability and Patient Access Final Rule.\n\n**There are items in this guide that are subject to update**. This includes:\n- Value Sets\n- Vocabularies (X12, NUBC etc.)\n- Examples\n\n**The Vocabulary, Value Sets and codings used to express data in this IG are subject to review and will be reconciled with** [X12](http://www.x12.org).\n\nSee the [Table of Contents](toc.html) for more information.\n (built Wed, Jun 18, 2025 00:57+0000+00:00)"},{"name":"ths-greifswald.ttp-fhir-gw","version":"2025.1.0-final","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ths-greifswald.ttp-fhir-gw","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ths-greifswald.ttp-fhir-gw-2025.1.0-final.tgz","date":"2025-06-19T07:59:03.000Z","description":"Finalisierung v2025.1.0 inkl mii kds consent 2025.0.4"},{"name":"ee.fhir.terminology","version":"1.0.0","fhirVersion":"5.0.0","canonical":"https://fhir.ee","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ee.fhir.terminology-1.0.0.tgz","date":"2025-06-19T12:02:11.000Z","description":"Terminoloogia mis on kasutusel juurutusjuhendites (built Thu, Jun 19, 2025 06:40+0000+00:00)"},{"name":"fhir.project0620","version":"0.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.project0620","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.project0620-0.0.0.tgz","date":"2025-06-20T06:51:46.000Z","description":"增加搜索参数"},{"name":"caseworks.mhaie002","version":"0.0.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/caseworks.mhaie002","kind":"fhir.ig","url":"https://packages2.fhir.org/web/caseworks.mhaie002-0.0.2.tgz","date":"2025-06-20T20:40:32.000Z","description":"Caseworks MHAIE"},{"name":"vzvz.fhir.mitz","version":"3.8.0","fhirVersion":"4.3.0","canonical":"http://simplifier.net/packages/vzvz.fhir.mitz","kind":"fhir.ig","url":"https://packages2.fhir.org/web/vzvz.fhir.mitz-3.8.0.tgz","date":"2025-06-23T08:04:21.000Z","description":"FHIR artifacts for Mitz specifications version 3.8.0"},{"name":"com.healthcare3","version":"0.1.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/com.healthcare3","kind":"fhir.ig","url":"https://packages2.fhir.org/web/com.healthcare3-0.1.0.tgz","date":"2025-06-24T00:10:54.000Z","description":"To build FHIR profiles for the Health Care application"},{"name":"tiplu.maia.schnittstellendefinition","version":"1.1.3","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/tiplu.maia.schnittstellendefinition","kind":"fhir.ig","url":"https://packages2.fhir.org/web/tiplu.maia.schnittstellendefinition-1.1.3.tgz","date":"2025-06-24T09:19:21.000Z","description":"* Dependencies\r\n * Increased de.basisprofil.r4 to 1.5.4\r\n* CapabilityStatement\r\n * Fixed SHALL and SHOULD flags"},{"name":"de.gkvsv.erezeptabrechnungsdaten","version":"1.4.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gkvsv.erezeptabrechnungsdaten","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gkvsv.erezeptabrechnungsdaten-1.4.2.tgz","date":"2025-06-24T09:25:28.000Z","description":"Der Abrechnungsdatensatz zum E-Rezept"},{"name":"fhir.erezept.validator","version":"0.4.9","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.erezept.validator","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.erezept.validator-0.4.9.tgz","date":"2025-06-25T13:38:02.000Z","description":"FHIR-Profil zur strukturierten Validierung von eRezept-Daten."},{"name":"smart.who.int.pcmt","version":"0.1.0","fhirVersion":"4.0.1","canonical":"http://smart.who.int/pcmt","kind":"fhir.ig","url":"https://packages2.fhir.org/web/smart.who.int.pcmt-0.1.0.tgz","date":"2025-06-26T12:04:55.000Z","description":"Data exchange specifications for Product Catalog supporting the SMART Guidelines (built Thu, Jun 26, 2025 06:29+0000+00:00)"},{"name":"ans.fr.doctrine","version":"0.1.0","fhirVersion":"4.0.1","canonical":"https://interop.esante.gouv.fr/ig/doctrine","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ans.fr.doctrine-0.1.0.tgz","date":"2025-07-01T06:01:58.000Z"},{"name":"smart.who.int.dak-smbp","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://smart.who.int/dak-smbp","kind":"fhir.ig","url":"https://packages2.fhir.org/web/smart.who.int.dak-smbp-1.0.0.tgz","date":"2025-07-01T12:05:11.000Z","description":"SMART Digital Adaptation Kit (DAK) for self-monitoring of blood pressure in pregnancy (SMBP) (built Tue, Jul 1, 2025 06:57+0000+00:00)"},{"name":"smart.who.int.ra","version":"0.1.0","fhirVersion":"4.0.1","canonical":"http://smart.who.int/ra","kind":"fhir.ig","url":"https://packages2.fhir.org/web/smart.who.int.ra-0.1.0.tgz","date":"2025-07-01T12:05:13.000Z","description":"The Reference Architecture Implementation Guide to be used as a starting point for building infrastructure with the SMART Guidelines aproach (built Tue, Jul 1, 2025 07:59+0000+00:00)"},{"name":"hl7.fhir.us.davinci-ra","version":"2.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-ra","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-ra-2.1.0.tgz","date":"2025-07-02T12:00:49.000Z","description":"The Da Vinci Fast Healthcare Interoperability Resource (FHIR) Risk Adjustment Implementation Guide (this IG) describes exchange of risk-based coding gaps among stakeholders such as payers, providers, and government care programs in support of driving towards accurate and complete documentation of health conditions that would lead to more accurate risk-adjustment payment calculations. (built Wed, Jul 2, 2025 02:08+0000+00:00)"},{"name":"fhir2.base.template","version":"0.1.0","fhirVersion":"4.0.1","canonical":"http://fhir.org/templates/fhir2.base.template","kind":"fhir.template","url":"https://packages2.fhir.org/web/fhir2.base.template-0.1.0.tgz","date":"2025-07-06T00:01:53.000Z","description":"FHIR IG Translated Base Template - foundational for use by anyone"},{"name":"openehr.fhir.template","version":"0.2.0","fhirVersion":"4.0.1","canonical":"http://fhir.org/templates/openehr.fhir.template","kind":"fhir.template","url":"https://packages2.fhir.org/web/openehr.fhir.template-0.2.0.tgz","date":"2025-07-06T00:01:56.000Z","description":"OpenEHR FHIR Template"},{"name":"hla.antibody.report","version":"0.1.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/hla.antibody.report","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hla.antibody.report-0.1.2.tgz","date":"2025-07-07T03:43:28.000Z","description":"HLA Antibody Report project\r\n- R4 / US Core\r\n- Define resource bundle\r\n- Create resource extensions "},{"name":"medmij.bglz.stu3","version":"1.0.0-alpha.1","fhirVersion":"3.0.1","canonical":"http://simplifier.net/packages/medmij.bglz.stu3","kind":"fhir.ig","url":"https://packages2.fhir.org/web/medmij.bglz.stu3-1.0.0-alpha.1.tgz","date":"2025-07-07T09:52:02.000Z","description":"This package contains only the FHIR examples. There is a dependency on the corresponding zib profiles. For the nl-core-nursingreport, there is a separate Simplifier project: https://simplifier.net/anw/nl-core-nursingreport"},{"name":"fhir.course.yuyao.e-prescribing","version":"0.1.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.course.yuyao.e-prescribing","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.course.yuyao.e-prescribing-0.1.0.tgz","date":"2025-07-08T10:51:02.000Z","description":"test"},{"name":"hl7.fhir.us.pq-cmc-fda","version":"2.0.0","fhirVersion":"5.0.0","canonical":"http://hl7.org/fhir/us/pq-cmc-fda","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.pq-cmc-fda-2.0.0.tgz","date":"2025-07-08T12:00:55.000Z","description":"The FDA PQ-CMC FHIR IG is for submission of structured and standardized information regarding drug product quality, chemistry, manufacturing and processes controls.  This data is intended for submission to the US FDA by biopharmaceutical companies for the purpose of drug application review. (built Tue, Jul 8, 2025 07:43+0000+00:00)"},{"name":"hl7.fhir.uv.cql","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/cql","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.cql-2.0.0.tgz","date":"2025-07-09T00:00:54.000Z","description":"This 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. (built Tue, Jul 8, 2025 14:47+0000+00:00)"},{"name":"test.ami.ad","version":"0.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/test.ami.ad","kind":"fhir.ig","url":"https://packages2.fhir.org/web/test.ami.ad-0.0.1.tgz","date":"2025-07-09T00:20:53.000Z","description":"Test"},{"name":"test.ami.a","version":"0.0.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/test.ami.a","kind":"fhir.ig","url":"https://packages2.fhir.org/web/test.ami.a-0.0.2.tgz","date":"2025-07-09T01:06:55.000Z","description":"Test"},{"name":"smart.who.int.hiv","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://smart.who.int/hiv","kind":"fhir.ig","url":"https://packages2.fhir.org/web/smart.who.int.hiv-1.0.0.tgz","date":"2025-07-09T12:04:54.000Z","description":"The implementation guide for the SMART WHO HIV guidelines, translated from the WHO HIV L2 artifacts and HIV DAK. (built Tue, Jul 8, 2025 23:21+0200+02:00)"},{"name":"cezih.hr.cezih-osnova","version":"0.2.9","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/cezih.hr.cezih-osnova","kind":"fhir.ig","url":"https://packages2.fhir.org/web/cezih.hr.cezih-osnova-0.2.9.tgz","date":"2025-07-09T13:18:04.000Z","description":"Ovaj vodič za implementaciju sadržava specifikaciju osnovnih elemenata (resursa, poruka, dokumenata, proširenja) i terminologija (kodnih sistema, skupova koncepata i mapa koncepata) koje se koriste u svim vodičima za implementaciju CEZIH sustava."},{"name":"cezih.hr.encounter-management","version":"0.2.3","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/cezih.hr.encounter-management","kind":"fhir.ig","url":"https://packages2.fhir.org/web/cezih.hr.encounter-management-0.2.3.tgz","date":"2025-07-09T13:52:28.000Z","description":"Ovaj vodič za implementaciju integracijskog sučelja opisuje funkcionalnosti usluge za upravljanje posjetama."},{"name":"ca.healthpei.io.core","version":"0.1.7-DFT","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.healthpei.io.core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.healthpei.io.core-0.1.7-DFT.tgz","date":"2025-07-09T14:39:59.000Z","description":"Government of Prince Edward Island - Core FHIR resources for the Clinical Data Repository. This repository consists of core profiles to be adopted by PEI FHIR IGs. "},{"name":"hl7.fhir.us.nhsn-dqm","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/nhsn-dqm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.nhsn-dqm-1.0.0.tgz","date":"2025-07-10T00:00:52.000Z","description":"This content describes the specifications for the for the Health Level Seven International® (HL7) Fast Healthcare Interoperability Resources® (FHIR) digital quality measures (dQMs) reported to the National Healthcare Safety Network (NHSN). (built Wed, Jul 9, 2025 20:38+0000+00:00)"},{"name":"hl7.fhir.uv.patient-corrections","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/patient-corrections","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.patient-corrections-1.0.0.tgz","date":"2025-07-10T18:00:54.000Z","description":"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. (built Thu, Jul 10, 2025 15:50+0000+00:00)"},{"name":"test.public.project","version":"0.0.3","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/test.public.project","kind":"fhir.ig","url":"https://packages2.fhir.org/web/test.public.project-0.0.3.tgz","date":"2025-07-11T08:58:32.000Z","description":"test"},{"name":"hl7.fhir.be.mycarenet","version":"2.1.2","fhirVersion":"4.0.1","canonical":"https://www.ehealth.fgov.be/standards/fhir/mycarenet","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.be.mycarenet-2.1.2.tgz","date":"2025-07-11T18:02:07.000Z"},{"name":"fhir.facade.cnes.organization","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.facade.cnes.organization","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.facade.cnes.organization-2.0.0.tgz","date":"2025-07-14T13:58:44.000Z","description":"FHIR® facades for accessing data from CNES, in Brazil."},{"name":"gpc.stu3.fhir-assets","version":"1.3.0","fhirVersion":"3.0.1","canonical":"http://simplifier.net/packages/gpc.stu3.fhir-assets","kind":"fhir.ig","url":"https://packages2.fhir.org/web/gpc.stu3.fhir-assets-1.3.0.tgz","date":"2025-07-14T15:09:07.000Z","description":"GP Connect / ITK specific FHIR STU3 assets"},{"name":"fhir.r4.nhsengland.stu1","version":"1.5.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.r4.nhsengland.stu1","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.r4.nhsengland.stu1-1.5.0.tgz","date":"2025-07-16T11:46:44.000Z","description":"A UK Core derived Implementation Guide for use within NHS England."},{"name":"tw.gov.mohw.emr","version":"0.2.0","fhirVersion":"4.0.1","canonical":"https://twcore.mohw.gov.tw/ig/emr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/tw.gov.mohw.emr-0.2.0.tgz","date":"2025-07-17T06:05:36.000Z","description":"電子病歷交換單張實作指引 EMR IG (built Mon, Jan 20, 2025 16:33+0800+08:00)"},{"name":"gdrl.fhir.r4","version":"1.4.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/gdrl.fhir.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/gdrl.fhir.r4-1.4.0.tgz","date":"2025-07-17T10:38:36.000Z","description":"Progetto OMr Gestione Rete Digitale Rete Laboratori per Regione Lombardia"},{"name":"nr.gp.leumit","version":"0.1.1","fhirVersion":"4.0.1","canonical":"http://fhir.leumit.co.il/ImplementationGuide/il.fhir.r4.leumit-hdp","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nr.gp.leumit-0.1.1.tgz","date":"2025-07-17T11:51:12.000Z","description":"This project is meant to display pacakges for QA prior to them being merged into production projects"},{"name":"fhir.org.nz.ig.base","version":"3.0.1","fhirVersion":"4.0.1","canonical":"http://fhir.org.nz/ig/base","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.org.nz.ig.base-3.0.1.tgz","date":"2025-07-17T12:02:05.000Z","description":"New Zealand base profiles (built Wed, Aug 14, 2024 09:17+1200+12:00)"},{"name":"hl7.fhir.uv.smart-health-cards-and-links","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/smart-health-cards-and-links","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.smart-health-cards-and-links-1.0.0.tgz","date":"2025-07-22T18:00:54.000Z","description":"FHIR Implementation Guide for SMART Health Cards and Links (built Tue, Jul 22, 2025 13:19+0000+00:00)"},{"name":"tw.gov.mohw.nhi.ngs","version":"1.0.0","fhirVersion":"4.0.1","canonical":"https://nhicore.nhi.gov.tw/ngs","kind":"fhir.ig","url":"https://packages2.fhir.org/web/tw.gov.mohw.nhi.ngs-1.0.0.tgz","date":"2025-07-23T06:11:33.000Z","description":"臺灣次世代基因定序檢測實作指引(TWNGS IG) (built Tue, Jul 22, 2025 15:53+0800+08:00)"},{"name":"de.thieme-compliance.anamnese","version":"0.0.2-dev","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.thieme-compliance.anamnese","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.thieme-compliance.anamnese-0.0.2-dev.tgz","date":"2025-07-23T09:46:54.000Z","description":"- Dev-Profile und OperationDefinitions ergänzt\r\n- Batch-Beispiel um Zustimmungs-Frage ergänzt\r\n"},{"name":"hl7.fhir.us.pacio-pfe","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/pacio-pfe","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.pacio-pfe-2.0.0.tgz","date":"2025-07-24T00:00:50.000Z","description":"FHIR Implementation Guide to exchange assessments of and data on a person's functioning, including body functions, activities, and participation, between post-acute care (PAC) and other providers, patients, and key stakeholders (built Wed, Jul 23, 2025 17:08+0000+00:00)"},{"name":"general.purpose.staging","version":"0.1.2","fhirVersion":"4.0.1","canonical":"http://fhir.leumit.co.il/ImplementationGuide/il.fhir.r4.leumit-hdp","kind":"fhir.ig","url":"https://packages2.fhir.org/web/general.purpose.staging-0.1.2.tgz","date":"2025-07-24T12:50:24.000Z","description":"This project is meant to display pacakges for QA prior to them being merged into production projects"},{"name":"fhir.tx.support.r3","version":"0.27.0","fhirVersion":"3.0.2","canonical":"http://fhir.org/terminology-support","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.tx.support.r3-0.27.0.tgz","date":"2025-07-28T12:01:08.000Z","description":"Various supporting code systems for tx.fhir.org (R3)"},{"name":"ca.on.health.idms","version":"1.0.9","fhirVersion":"5.0.0","canonical":"http://simplifier.net/packages/ca.on.health.idms","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.health.idms-1.0.9.tgz","date":"2025-07-28T18:14:22.000Z","description":"The system will support a single authoritative record of drug product info in a central repository."},{"name":"fhir.dicom","version":"2025.3.20250714","fhirVersion":"4.0.1","canonical":"http://fhir.org/packages/fhir.dicom","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.dicom-2025.3.20250714.tgz","date":"2025-07-29T00:01:07.000Z"},{"name":"nictiz.fhir.nl.stu3.geboortezorg.test","version":"1.3.3-rc.8","fhirVersion":"3.0.1","canonical":"http://simplifier.net/packages/nictiz.fhir.nl.stu3.geboortezorg.test","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nictiz.fhir.nl.stu3.geboortezorg.test-1.3.3-rc.8.tgz","date":"2025-07-29T15:22:07.000Z","description":"Please find a selection of the Nictiz packages here."},{"name":"hl7.fhir.uv.omop","version":"1.0.0-ballot","fhirVersion":"5.0.0","canonical":"http://hl7.org/fhir/uv/omop","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.omop-1.0.0-ballot.tgz","date":"2025-07-30T00:00:57.000Z","description":"An IG that provides the mappings and use cases for converting from FHIR to OMOP. (built Tue, Jul 29, 2025 21:03+0000+00:00)"},{"name":"hl7.fhir.uv.cardx-cied","version":"1.0.0-ballot","fhirVersion":"5.0.0","canonical":"http://hl7.org/fhir/uv/cardx-cied","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.cardx-cied-1.0.0-ballot.tgz","date":"2025-07-31T06:00:50.000Z"},{"name":"de.gematik.fhir.atf","version":"1.4.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gematik.fhir.atf","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.fhir.atf-1.4.1.tgz","date":"2025-07-31T09:33:47.000Z","description":"A framework for applications that use KIM or TI-Messenger for end to end data transport"},{"name":"de.gematik.erp-servicerequest","version":"1.2.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gematik.erp-servicerequest","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.erp-servicerequest-1.2.0.tgz","date":"2025-07-31T13:11:07.000Z","description":"Rezeptanforderung im Gesundheitswesen"},{"name":"nictiz.fhir.nl.stu3.geboortezorg","version":"1.3.3","fhirVersion":"3.0.1","canonical":"http://simplifier.net/packages/nictiz.fhir.nl.stu3.geboortezorg","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nictiz.fhir.nl.stu3.geboortezorg-1.3.3.tgz","date":"2025-07-31T14:03:18.000Z","description":"Geboortezorg informatiestandaard"},{"name":"hl7.fhir.uv.pharmaceutical-research-protocol","version":"1.0.0-ballot","fhirVersion":"6.0.0-ballot3","canonical":"http://hl7.org/fhir/uv/pharmaceutical-research-protocol","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.pharmaceutical-research-protocol-1.0.0-ballot.tgz","date":"2025-08-01T12:18:30.000Z"},{"name":"ks.workinprogress","version":"0.0.2-sample","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ks.workinprogress","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ks.workinprogress-0.0.2-sample.tgz","date":"2025-08-05T07:05:43.000Z","description":"FHIR-related WIPs"},{"name":"hl7.fhir.us.cdc-opioid-cpg","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/cdc-opioid-cpg","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.cdc-opioid-cpg-1.0.0-ballot.tgz","date":"2025-08-06T18:00:48.000Z","description":"Defines exchange expectations for systems that implement the 2022 CDC Clinical Practice Guideline for Prescribing Opioids, both in terms of the data required to evaluate whether recommendations are applicable, as well as the data required to represent proposals resulting from those recommendations. (built Fri, Aug 1, 2025 20:38+0000+00:00)"},{"name":"hl7.fhir.us.pacio-adi","version":"2.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/pacio-adi","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.pacio-adi-2.0.0-ballot.tgz","date":"2025-08-06T18:01:03.000Z","description":"PACIO Advance Directive Interoperability Implementation Guide (built Mon, Aug 4, 2025 21:33+0000+00:00)"},{"name":"hl7.fhir.us.resp-net","version":"2.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/resp-net","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.resp-net-2.0.0-ballot.tgz","date":"2025-08-06T18:01:10.000Z","description":"The RESP-NET Content IG focuses on the respiratory virus surveillance data that will be extracted from EHRs via FHIR and APIs and sent to RESP-NET sites. (built Mon, Aug 4, 2025 13:36+0000+00:00)"},{"name":"hl7.fhir.uv.crmi","version":"2.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/crmi","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.crmi-2.0.0-ballot.tgz","date":"2025-08-06T18:01:22.000Z","description":"This 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. (built Fri, Aug 1, 2025 18:39+0000+00:00)"},{"name":"outburn.general.purpose.staging","version":"1.0.0-beta","fhirVersion":"4.0.1","canonical":"http://fhir.leumit.co.il/ImplementationGuide/il.fhir.r4.leumit-hdp","kind":"fhir.ig","url":"https://packages2.fhir.org/web/outburn.general.purpose.staging-1.0.0-beta.tgz","date":"2025-08-07T06:58:18.000Z","description":"This project is meant to display pacakges for QA prior to them being merged into production projects"},{"name":"hl7.fhir.uv.rtls","version":"1.0.0-ballot2","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/rtls","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.rtls-1.0.0-ballot2.tgz","date":"2025-08-07T18:00:56.000Z","description":"Description of IG (built Thu, Aug 7, 2025 17:38+0000+00:00)"},{"name":"hl7.xprod.uv.piqi","version":"1.0.0-ballot","fhirVersion":"5.0.0","canonical":"http://hl7.org/xprod/ig/uv/piqi","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.xprod.uv.piqi-1.0.0-ballot.tgz","date":"2025-08-11T06:00:57.000Z","description":"HL7 Informative Document: Patient Information Quality Improvement (PIQI) Framework, Edition 1 (built Mon, Aug 11, 2025 12:11+1000+10:00)"},{"name":"fi.kela.kanta.hrp.potilastiedot","version":"1.1.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fi.kela.kanta.hrp.potilastiedot","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fi.kela.kanta.hrp.potilastiedot-1.1.0.tgz","date":"2025-08-11T12:07:05.000Z","description":"Kanta Hyvinvointisovellusten rajapinta potilastietoihin FHIR R4 määrittelyt (profiilit, laajennokset, ValueSet:it ja CodeSystem:it)."},{"name":"ca.pipeline.test.package","version":"0.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.pipeline.test.package","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.pipeline.test.package-0.0.1.tgz","date":"2025-08-12T17:45:57.000Z","description":"A temporary project to test / validate a new pipeline conformance testing workflow."},{"name":"medmij.fhir.nl.r4.dentalcare","version":"1.0.0-beta.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/medmij.fhir.nl.r4.dentalcare","kind":"fhir.ig","url":"https://packages2.fhir.org/web/medmij.fhir.nl.r4.dentalcare-1.0.0-beta.1.tgz","date":"2025-08-14T12:36:23.000Z","description":"MedMij Dental Care 1.0.0-beta.1"},{"name":"ca.pipeline.test.breaks","version":"0.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.pipeline.test.breaks","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.pipeline.test.breaks-0.0.1.tgz","date":"2025-08-14T19:47:49.000Z","description":"A temporary project to test / validate a new pipeline conformance testing workflow."},{"name":"dot.cdr-implementation-guide","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/dot.cdr-implementation-guide","kind":"fhir.ig","url":"https://packages2.fhir.org/web/dot.cdr-implementation-guide-1.0.0.tgz","date":"2025-08-14T21:31:08.000Z","description":"CDR-Implementation-Guide"},{"name":"medcom.fhir.dk.homecareobservationtestscripts","version":"1.0.0-draft","fhirVersion":"4.0.1","canonical":"http://medcomfhir.dk/ig/homecareobservationtestscripts","kind":"fhir.ig","url":"https://packages2.fhir.org/web/medcom.fhir.dk.homecareobservationtestscripts-1.0.0-draft.tgz","date":"2025-08-18T12:02:43.000Z","description":"Testscripts for HomeCareObservations FHIR Implementation Guide (built Mon, Aug 18, 2025 06:59+0000+00:00)"},{"name":"fhir.astp.bhp","version":"0.1.0","fhirVersion":"4.0.1","canonical":"http://fhir.org/guides/astp/bhp","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.astp.bhp-0.1.0.tgz","date":"2025-08-18T18:01:07.000Z"},{"name":"ca.on.oh-erec-ig","version":"0.12.4-alpha1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.oh-erec-ig","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.oh-erec-ig-0.12.4-alpha1.0.0.tgz","date":"2025-08-18T20:57:51.000Z","description":"ON eReC Specifications:\r\n\r\nLatest: https://simplifier.net/guide/ca-on-ereferral-r4-iguide?version=0.12.1\r\n\r\nOther:\r\n\r\nhttps://simplifier.net/guide/ca-on-ereferral-r4-iguide/Index?version=0.12.0 \r\n\r\nhttps://simplifier.net/guide/ca-on-ereferral-r4-iguide/Index?version=0.11.1\r\n\r\n"},{"name":"kl.dk.fhir.term","version":"2.3.0","fhirVersion":"4.0.1","canonical":"http://fhir.kl.dk/term","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kl.dk.fhir.term-2.3.0.tgz","date":"2025-08-21T12:01:58.000Z"},{"name":"de.gematik.directory","version":"0.11.26","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gematik.directory","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.directory-0.11.26.tgz","date":"2025-08-25T04:53:54.000Z","description":"gematik FHIR Directory: Verzeichnisdienst der Telematikinfrastruktur "},{"name":"br.ufg.cgis.rnds-lite","version":"0.2.7","fhirVersion":"4.0.1","canonical":"http://www.saude.gov.br/fhir/r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/br.ufg.cgis.rnds-lite-0.2.7.tgz","date":"2025-08-26T06:02:33.000Z"},{"name":"ans.cda.fr.tddui","version":"1.0.0","fhirVersion":"4.0.1","canonical":"https://interop.esante.gouv.fr/ig/cda/tddui","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ans.cda.fr.tddui-1.0.0.tgz","date":"2025-08-28T06:01:53.000Z"},{"name":"nr.gp.rmc","version":"0.1.3","fhirVersion":"4.0.1","canonical":"http://fhir.leumit.co.il/ImplementationGuide/il.fhir.r4.leumit-hdp","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nr.gp.rmc-0.1.3.tgz","date":"2025-09-02T05:19:40.000Z","description":"This project is meant to display packages for QA prior to them being merged into production projects"},{"name":"nexuzhealth.fhir.r4","version":"1.0.5","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/nexuzhealth.fhir.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nexuzhealth.fhir.r4-1.0.5.tgz","date":"2025-09-02T08:35:23.000Z","description":"Technical profiles used by Nexuzhealth FHIR Stores"},{"name":"ca.on.mi.pkg","version":"0.9.0-beta-5-testing","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.mi.pkg","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.mi.pkg-0.9.0-beta-5-testing.tgz","date":"2025-09-02T14:13:03.000Z","description":"The purpose of the Medical Imaging (MI) project is to consolidate medical imaging documents and imag"},{"name":"ca.infoway.io.ca-ext-reg","version":"0.0.3-beta-1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.infoway.io.ca-ext-reg","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.infoway.io.ca-ext-reg-0.0.3-beta-1.tgz","date":"2025-09-02T20:55:23.000Z","description":"Canadian Extension Registry."},{"name":"synapxe.nde","version":"1.0.0","fhirVersion":"5.0.0","canonical":"http://simplifier.net/packages/synapxe.nde","kind":"fhir.ig","url":"https://packages2.fhir.org/web/synapxe.nde-1.0.0.tgz","date":"2025-09-03T01:47:45.000Z","description":"Synapxe NDE Project"},{"name":"de.fhir.terminologie","version":"0.0.1-alpha2","fhirVersion":"4.0.1","canonical":"http://ig.fhir.de/igs/terminologie","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.fhir.terminologie-0.0.1-alpha2.tgz","date":"2025-09-04T18:02:41.000Z"},{"name":"dk.ehmi.eer","version":"1.0.0-draft","fhirVersion":"4.0.1","canonical":"http://medcomehmi.dk/ig/eer","kind":"fhir.ig","url":"https://packages2.fhir.org/web/dk.ehmi.eer-1.0.0-draft.tgz","date":"2025-09-10T18:02:55.000Z","description":"The EHMI Endpoint Register (EER) IG (built Wed, Sep 10, 2025 11:53+0000+00:00)"},{"name":"hl7.fhir.uv.cqm","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/cqm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.cqm-1.0.0.tgz","date":"2025-09-12T00:00:52.000Z","description":"The Fast Healthcare Interoperability Resource (FHIR) Quality Measure Implementation Guide (this IG) describes an approach to representing Quality Measures (QMs) using the FHIR Clinical Reasoning Module and Clinical Quality Language (CQL) in the US Realm. However, this Implementation Guide can be usable for multiple use cases across domains, and much of the content is likely to be usable outside the US Realm. (built Thu, Sep 11, 2025 18:58+0000+00:00)"},{"name":"hl7.fhir.pl.laboratory.r5","version":"0.1.0","fhirVersion":"5.0.0","canonical":"http://hl7.org.pl/fhir/ig/pl-lab","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.pl.laboratory.r5-0.1.0.tgz","date":"2025-09-15T12:05:47.000Z"},{"name":"ca.infoway.io.core","version":"1.1.0-dft-preballot","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.infoway.io.core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.infoway.io.core-1.1.0-dft-preballot.tgz","date":"2025-09-16T16:40:31.000Z","description":"The CA Core+ project provides profiles based on the business, conceptual, and logical models in the pan-Canadian Health Data Content Framework and Canadian Core for Data Interoperability (pCHDCF-CACDI). These models capture the data that is essential for clinical and business workflows to provide better health outcomes for Canadians."},{"name":"t.t.t1","version":"0.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/t.t.t1","kind":"fhir.ig","url":"https://packages2.fhir.org/web/t.t.t1-0.0.1.tgz","date":"2025-09-17T10:48:00.000Z","description":"Test"},{"name":"smart.who.int.dak-pnc","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://smart.who.int/dak-pnc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/smart.who.int.dak-pnc-1.0.0.tgz","date":"2025-09-17T12:06:09.000Z","description":"SMART DAK for postnatal care (PNC) (built Wed, Sep 17, 2025 08:01+0000+00:00)"},{"name":"smart.who.int.pcmt-vaxprequal","version":"0.2.0","fhirVersion":"4.0.1","canonical":"http://smart.who.int/pcmt-vaxprequal","kind":"fhir.ig","url":"https://packages2.fhir.org/web/smart.who.int.pcmt-vaxprequal-0.2.0.tgz","date":"2025-09-17T12:06:13.000Z","description":"Data exchange specifications for Product Catalog supporting the SMART Guidelines (built Tue, Sep 16, 2025 20:38+0000+00:00)"},{"name":"dk.ehmi.terminology","version":"1.0.1-draft","fhirVersion":"4.0.1","canonical":"http://medcomehmi.dk/ig/terminology","kind":"fhir.ig","url":"https://packages2.fhir.org/web/dk.ehmi.terminology-1.0.1-draft.tgz","date":"2025-09-18T12:03:31.000Z","description":"The DK EHMI Terminology IG (built Thu, Sep 18, 2025 07:41+0000+00:00)"},{"name":"firely.r4.sample.ig","version":"0.2.0-draft","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/firely.r4.sample.ig","kind":"fhir.ig","url":"https://packages2.fhir.org/web/firely.r4.sample.ig-0.2.0-draft.tgz","date":"2025-09-18T14:19:43.000Z","description":"Firely R4 Sample IG"},{"name":"globalalliant.us.eom-updates","version":"1.1.0-alpha-13","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/globalalliant.us.eom-updates","kind":"fhir.ig","url":"https://packages2.fhir.org/web/globalalliant.us.eom-updates-1.1.0-alpha-13.tgz","date":"2025-09-18T16:50:21.000Z","description":"This package is empty to ensure it's not used. The new package will be privately distributed."},{"name":"medmij.fhir.nl.r4.imageavailability","version":"1.0.0-rc.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/medmij.fhir.nl.r4.imageavailability","kind":"fhir.ig","url":"https://packages2.fhir.org/web/medmij.fhir.nl.r4.imageavailability-1.0.0-rc.1.tgz","date":"2025-09-19T09:49:21.000Z","description":"MedMij Image Availability 1.0.0-rc.1"},{"name":"ca.on.oh-seris-r4","version":"1.1.0-snapshot1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.oh-seris-r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.oh-seris-r4-1.1.0-snapshot1.tgz","date":"2025-09-19T14:38:46.000Z","description":"The purpose of SERIS is to improve surgical performance in Ontario through the measurement and report."},{"name":"test.202111519","version":"0.0.2","fhirVersion":"5.0.0","canonical":"http://simplifier.net/packages/test.202111519","kind":"fhir.ig","url":"https://packages2.fhir.org/web/test.202111519-0.0.2.tgz","date":"2025-09-19T18:47:27.000Z","description":"A playground like test project."},{"name":"test.package.feeds.terminal","version":"0.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/test.package.feeds.terminal","kind":"fhir.ig","url":"https://packages2.fhir.org/web/test.package.feeds.terminal-0.0.1.tgz","date":"2025-09-22T09:33:30.000Z","description":"test package feeds from firely terminal"},{"name":"fhir.deep6.ai","version":"2.5.0","fhirVersion":"4.0.1","canonical":"http://deep6.ai/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.deep6.ai-2.5.0.tgz","date":"2025-09-23T00:05:07.000Z","description":"Deep 6 AI Inc FHIR IG"},{"name":"medcom.fhir.dk.messagedefinitions","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://medcomfhir.dk/ig/messagedefinitions","kind":"fhir.ig","url":"https://packages2.fhir.org/web/medcom.fhir.dk.messagedefinitions-1.0.0.tgz","date":"2025-09-24T12:02:48.000Z","description":"Collection of all MedCom MessageDefinitions (built Wed, Sep 24, 2025 11:31+0000+00:00)"},{"name":"hl7.fhir.uv.cgm","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/cgm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.cgm-1.0.0.tgz","date":"2025-09-25T00:00:55.000Z","description":"Communicate Continuous Glucose Monitoring (CGM) data using FHIR (built Wed, Sep 24, 2025 19:31+0000+00:00)"},{"name":"synapxe.nehr","version":"2.0.0","fhirVersion":"5.0.0","canonical":"http://simplifier.net/packages/synapxe.nehr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/synapxe.nehr-2.0.0.tgz","date":"2025-09-30T07:46:48.000Z","description":"Synapxe NEHR Project"},{"name":"fhir.r4.wales.test","version":"2.3.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.r4.wales.test","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.r4.wales.test-2.3.0.tgz","date":"2025-09-30T07:56:33.000Z","description":"FHIR Standards Wales TEST - for testing resource changes on branches prior to pushing to main"},{"name":"ca.infoway.io.cafex","version":"2.2.0-DFT","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.infoway.io.cafex","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.infoway.io.cafex-2.2.0-DFT.tgz","date":"2025-09-30T17:29:35.000Z","description":"The CA:FeX Interoperability Specifications (Canadian FHIR Exchange (CA:FeX)) seek to promote FHIR RESTful exchange patterns, developed by industry-leading FHIR standards that can be applied on top of an existing infrastructure just as easily as it can be applied on top of FHIR servers. "},{"name":"ca.infoway.io.psca","version":"2.1.1-DFT","fhirVersion":"4.0.1","canonical":"http://fhir.infoway-inforoute.ca/io/psca","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.infoway.io.psca-2.1.1-DFT.tgz","date":"2025-09-30T18:12:12.000Z","description":"Pan-Canadian Patient Summary (PS-CA) 2.1.1 DFT Release to support Patient Summary in Canada"},{"name":"ans.fr.template","version":"1.0.0","fhirVersion":"4.0.1","canonical":"https://interop.esante.gouv.fr/ig/template","kind":"fhir.template","url":"https://packages2.fhir.org/web/ans.fr.template-1.0.0.tgz","date":"2025-10-01T06:01:56.000Z","description":"ANS FHIR IG Base Template"},{"name":"cqf.opioidcds.fhir.template","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.org/templates/cqf.opioidcds.fhir.template","kind":"fhir.template","url":"https://packages2.fhir.org/web/cqf.opioidcds.fhir.template-1.0.0.tgz","date":"2025-10-01T06:01:57.000Z","description":"CQF OpioidCDS FHIR Template"},{"name":"cqf.fhir.template","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.org/templates/cqf.fhir.template","kind":"fhir.template","url":"https://packages2.fhir.org/web/cqf.fhir.template-1.0.0.tgz","date":"2025-10-01T06:01:57.000Z","description":"CQF FHIR Template"},{"name":"fhir.base.template","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.org/templates/fhir.base.template","kind":"fhir.template","url":"https://packages2.fhir.org/web/fhir.base.template-1.0.0.tgz","date":"2025-10-01T06:01:58.000Z","description":"FHIR IG Base Template - foundational for use by anyone"},{"name":"fhir.carequality.template","version":"1.0.0","fhirVersion":"4.0.1","canonical":"https://github.com/Carequality/ig-template-carequality","kind":"fhir.template","url":"https://packages2.fhir.org/web/fhir.carequality.template-1.0.0.tgz","date":"2025-10-01T06:02:01.000Z","description":"FHIR IG Carequality Template"},{"name":"hl7.at.fhir.template","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.org/templates/hl7.at.fhir.template","kind":"fhir.template","url":"https://packages2.fhir.org/web/hl7.at.fhir.template-1.0.0.tgz","date":"2025-10-01T06:02:02.000Z","description":"Austrian FHIR® IG Base Template - for use by anyone in the Austrian domain"},{"name":"hl7.au.base.template","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.org/templates/hl7.base.template","kind":"fhir.template","url":"https://packages2.fhir.org/web/hl7.au.base.template-1.0.0.tgz","date":"2025-10-01T06:02:03.000Z","description":"HL7 Australia base template for use with HL7 Australia-published implementation guides"},{"name":"hl7.au.fhir.template","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.org/templates/hl7.au.fhir.template","kind":"fhir.template","url":"https://packages2.fhir.org/web/hl7.au.fhir.template-1.0.0.tgz","date":"2025-10-01T06:02:05.000Z","description":"HL7 Australia template for use with HL7 Australia-published FHIR implementation guides"},{"name":"hl7.au.sparked.template","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.org/templates/hl7.au.sparked.template","kind":"fhir.template","url":"https://packages2.fhir.org/web/hl7.au.sparked.template-1.0.0.tgz","date":"2025-10-01T06:02:06.000Z","description":"HL7 Australia template for use with FHIR implementation guides published in scope of Sparked program"},{"name":"hl7.base.template","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.org/templates/hl7.base.template","kind":"fhir.template","url":"https://packages2.fhir.org/web/hl7.base.template-1.0.0.tgz","date":"2025-10-01T06:02:08.000Z","description":"HL7 Core Template - base tempalte for use with HL7-published IGs. Shouldn't be used directly - use FHIR, v2, CDA, etc."},{"name":"hl7.ca.fhir.template","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.org/templates/hl7.ca.fhir.template","kind":"fhir.template","url":"https://packages2.fhir.org/web/hl7.ca.fhir.template-1.0.0.tgz","date":"2025-10-01T06:02:09.000Z","description":"HL7 Canada Template - for use with HL7 Canada-published FHIR IGs"},{"name":"hl7.cda.template","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://github.com/HL7/ig-template-cda","kind":"fhir.template","url":"https://packages2.fhir.org/web/hl7.cda.template-1.0.0.tgz","date":"2025-10-01T06:02:11.000Z","description":"HL7 CDA Template - for use with HL7-published FHIR IGs"},{"name":"hl7.davinci.template","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.org/templates/hl7.davinci.template","kind":"fhir.template","url":"https://packages2.fhir.org/web/hl7.davinci.template-1.0.0.tgz","date":"2025-10-01T06:02:14.000Z","description":"HL7 Da Vinci Template - for use with HL7 Da Vinci-published FHIR IGs"},{"name":"hl7.dk.fhir.template","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://github.com/hl7dk/dk-ig-template","kind":"fhir.template","url":"https://packages2.fhir.org/web/hl7.dk.fhir.template-1.0.0.tgz","date":"2025-10-01T06:02:16.000Z","description":"HL7 Denmark Template - for use with HL7 Denmark-published FHIR IGs"},{"name":"hl7.ehrs.template","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://github.com/HL7/ig-template-ehrs","kind":"fhir.template","url":"https://packages2.fhir.org/web/hl7.ehrs.template-1.0.0.tgz","date":"2025-10-01T06:02:18.000Z","description":"Template used for HL7-defined EHR-S product family implementation guides."},{"name":"hl7.extensions.template","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://github.com/HL7/ig-template-extensions","kind":"fhir.template","url":"https://packages2.fhir.org/web/hl7.extensions.template-1.0.0.tgz","date":"2025-10-01T06:02:20.000Z","description":"Template for extensions Pack"},{"name":"hl7.fhir.template","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.org/templates/hl7.fhir.template","kind":"fhir.template","url":"https://packages2.fhir.org/web/hl7.fhir.template-1.0.0.tgz","date":"2025-10-01T06:02:23.000Z","description":"HL7 FHIR Template - for use with HL7-published FHIR IGs"},{"name":"hl7.sdc.template","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.org/templates/hl7.davinci.template","kind":"fhir.template","url":"https://packages2.fhir.org/web/hl7.sdc.template-1.0.0.tgz","date":"2025-10-01T06:02:26.000Z","description":"HL7 SDC Template - for use with the HL7 SDC FHIR IG"},{"name":"hl7.utg.template","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://github.com/HL7/ig-template-hl7","kind":"fhir.template","url":"https://packages2.fhir.org/web/hl7.utg.template-1.0.0.tgz","date":"2025-10-01T06:02:29.000Z","description":"HL7 UTG Template"},{"name":"ihe.fhir.template","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.org/templates/ihe.fhir.template","kind":"fhir.template","url":"https://packages2.fhir.org/web/ihe.fhir.template-1.0.0.tgz","date":"2025-10-01T06:02:32.000Z","description":"IHE FHIR Template"},{"name":"who.fhir.template","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://github.com/WorldHealthOrganization/smart-ig-template-who","kind":"fhir.template","url":"https://packages2.fhir.org/web/who.fhir.template-1.0.0.tgz","date":"2025-10-01T06:02:36.000Z","description":"WHO FHIR IG Template"},{"name":"tw.gov.mohw.nhi.empd","version":"0.1.0","fhirVersion":"4.0.1","canonical":"https://nhicore.nhi.gov.tw/empd","kind":"fhir.ig","url":"https://packages2.fhir.org/web/tw.gov.mohw.nhi.empd-0.1.0.tgz","date":"2025-10-01T06:14:26.000Z","description":"臺灣電子處方箋與調劑單張實作指引 (built Fri, Sep 26, 2025 18:00+0800+08:00)"},{"name":"hl7.fhir.cl.clcore","version":"1.9.4","fhirVersion":"4.0.1","canonical":"https://hl7chile.cl/fhir/ig/clcore","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.cl.clcore-1.9.4.tgz","date":"2025-10-03T00:02:12.000Z","description":"Guía de Implementación de FHIR R4 para Chile, versión 2.0.0, que contiene los recursos básicos de FHIR necesarios para la interoperabilidad en el contexto chileno. Esta guía es una evolución de la versión 1.0.0, incorporando mejoras y correcciones basadas en la experiencia adquirida en su uso. (built Thu, Oct 2, 2025 16:23-0300-03:00)"},{"name":"hl7.fhir.us.cancer-reporting","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/cancer-reporting","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.cancer-reporting-2.0.0.tgz","date":"2025-10-03T18:00:45.000Z","description":"This implementation guide (IG) provides Health Level Seven (HL7 FHIR) resources to define standards for cancer pathology information exchange from a hospital or facility-based laboratory information system (LIS) to a hospital or facility-based electronic health record (EHR) system or to a central cancer registry. When sending between LIS and EHR systems, implementors may choose to use transport and processing modalities, such as FHIR bundles. This publication provides the data model, defined data items and their corresponding code and value sets specific to a cancer pathology synoptic report. This guide contains a library of FHIR profiles to create a cancer pathology bundle and is compliant with FHIR Release 4. (built Fri, Oct 3, 2025 14:09+0000+00:00)"},{"name":"hl7.fhir.uv.ips","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/ips","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.ips-2.0.0.tgz","date":"2025-10-03T18:00:49.000Z"},{"name":"ihe.qrph.ccg","version":"1.0.0","fhirVersion":"4.0.1","canonical":"https://profiles.ihe.net/QRPH/CCG","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.qrph.ccg-1.0.0.tgz","date":"2025-10-04T00:02:00.000Z","description":"The IHE Computable Care Guidelines (CCG) Profile specifies a normative grammar and a normative transaction processing model that allows evidence-based care recommendations to be expressed in a way that a digital health solution can ingest and operationalize. This is an implementable and conformance-testable specification. It is targeted to regulated healthcare markets where the support for multiple conditions is an important requirement. The CCG Profile supports jurisdictions that want to leverage digital health to systemically improve the adoption of guideline-adherent best practices across an entire care delivery network. (built Thu, Oct 2, 2025 10:20-0500-05:00)"},{"name":"ihe.qrph.madx","version":"3.0.0","fhirVersion":"4.0.1","canonical":"https://profiles.ihe.net/QRPH/mADX","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.qrph.madx-3.0.0.tgz","date":"2025-10-04T00:02:00.000Z","description":"The Mobile Aggregate Data Exchange (mADX) Profile supports interoperable public health reporting of aggregate health data. This data most typically takes the form of routine reports (weekly, monthly, quarterly, etc.) from a health facility to some administrative jurisdiction such as a health district, though there are numerous other use cases such as international reporting and community health worker reporting. (built Wed, Sep 17, 2025 13:24-0500-05:00)"},{"name":"synapxe.rcm","version":"1.2.0","fhirVersion":"5.0.0","canonical":"http://simplifier.net/packages/synapxe.rcm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/synapxe.rcm-1.2.0.tgz","date":"2025-10-07T01:44:43.000Z","description":"Synapxe RCM Project"},{"name":"fhir.vn.core.ironx","version":"0.1.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.vn.core.ironx","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.vn.core.ironx-0.1.1.tgz","date":"2025-10-07T09:09:12.000Z","description":"VN Core Fhir"},{"name":"smart.who.int.trust-phw","version":"0.1.0","fhirVersion":"4.0.1","canonical":"http://smart.who.int/trust-phw","kind":"fhir.ig","url":"https://packages2.fhir.org/web/smart.who.int.trust-phw-0.1.0.tgz","date":"2025-10-07T12:06:32.000Z","description":"Describes common workflows and specifications for usage of personal health wallets on the WHO GDHCN Trust Network (built Tue, Oct 7, 2025 06:40+0000+00:00)"},{"name":"ma.ambulanter.fall","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ma.ambulanter.fall","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ma.ambulanter.fall-2.0.0.tgz","date":"2025-10-07T17:56:58.000Z","description":"Ambulanter Abrechnungsfall im Krankenhaus"},{"name":"hl7.fhir.uv.v2mappings","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/v2mappings","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.v2mappings-1.0.0.tgz","date":"2025-10-08T00:00:56.000Z","description":"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. (built Tue, Oct 7, 2025 19:28+0000+00:00)"},{"name":"de.medizininformatikinitiative.kerndatensatz.person","version":"2025.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.medizininformatikinitiative.kerndatensatz.person","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.medizininformatikinitiative.kerndatensatz.person-2025.0.1.tgz","date":"2025-10-08T13:22:27.000Z","description":"Medizininformatik Initiative - Modul Person"},{"name":"smart.who.int.icvp","version":"0.2.0","fhirVersion":"4.0.1","canonical":"http://smart.who.int/icvp","kind":"fhir.ig","url":"https://packages2.fhir.org/web/smart.who.int.icvp-0.2.0.tgz","date":"2025-10-08T18:05:50.000Z","description":"SMART Guidelines for International Certificate for Vaccination or Prophylaxis (built Wed, Oct 8, 2025 14:32+0000+00:00)"},{"name":"il.rmc.fhir.r4","version":"0.2.4","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/il.rmc.fhir.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/il.rmc.fhir.r4-0.2.4.tgz","date":"2025-10-09T07:21:05.000Z","description":"DRAFT"},{"name":"ca.infoway.io.erec.branch","version":"1.0.5-dft","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.infoway.io.erec.branch","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.infoway.io.erec.branch-1.0.5-dft.tgz","date":"2025-10-10T17:49:15.000Z","description":"This project is a sub-branch of the Canadian eReferral / eConsult project version 1.0 project."},{"name":"elb.ck.private","version":"0.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/elb.ck.private","kind":"fhir.ig","url":"https://packages2.fhir.org/web/elb.ck.private-0.0.1.tgz","date":"2025-10-14T10:20:10.000Z","description":"see https://www.eleistungsbestaetigung.de/"},{"name":"test.rmc.fhir.r4","version":"0.1.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/test.rmc.fhir.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/test.rmc.fhir.r4-0.1.2.tgz","date":"2025-10-16T07:40:16.000Z","description":"Different projects can live here for testing purposes"},{"name":"ca.on.accdr.r4","version":"1.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.accdr.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.accdr.r4-1.0.1.tgz","date":"2025-10-16T14:59:45.000Z","description":"Ontario acCDR FHIR IG package"},{"name":"ans.fhir.fr.ror","version":"0.7.0-snapshot-1","fhirVersion":"4.0.1","canonical":"https://interop.esante.gouv.fr/ig/fhir/ror","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ans.fhir.fr.ror-0.7.0-snapshot-1.tgz","date":"2025-10-18T06:02:02.000Z","description":"Ressources de conformité basées sur le modèle d'exposition 3.1 du ROR (built Fri, Oct 17, 2025 14:07+0000+00:00)"},{"name":"de.medizininformatikinitiative.kerndatensatz.diagnose","version":"2025.0.1","fhirVersion":"4.0.1","canonical":"https://www.medizininformatik-initiative.de/fhir/core/modul-diagnose/ImplementationGuide/mii-ig-diagnose","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.medizininformatikinitiative.kerndatensatz.diagnose-2025.0.1.tgz","date":"2025-10-20T13:52:24.000Z","description":"Medizininformatik Initiative - Modul Diagnose"},{"name":"synapxe.hsar","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://simplifier.net/packages/synapxe.hsar","kind":"fhir.ig","url":"https://packages2.fhir.org/web/synapxe.hsar-1.0.0.tgz","date":"2025-10-22T02:58:02.000Z","description":"Synapxe HSAR Project - Healthier SG"},{"name":"acs.ig.epi.pl.deu","version":"0.3.1","fhirVersion":"5.0.0","canonical":"http://fhir.pharmaprotect.de/digital/epil-fhir-ig","kind":"fhir.ig","url":"https://packages2.fhir.org/web/acs.ig.epi.pl.deu-0.3.1.tgz","date":"2025-10-22T08:48:48.000Z","description":"German (DEU) electroinic Product Information Leaflet (ePIL) Implementation Guide"},{"name":"laniado.test.fhir","version":"0.1.93","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/laniado.test.fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/laniado.test.fhir-0.1.93.tgz","date":"2025-10-22T10:41:24.000Z","description":"Laniado Hospital Test Project"},{"name":"hl7.at.fhir.gkl.ig-tooling","version":"0.5.3","fhirVersion":"4.0.1","canonical":"https://gabriel0316.github.io/ig-tooling-pages/ig/ig-tooling-test","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.at.fhir.gkl.ig-tooling-0.5.3.tgz","date":"2025-10-22T12:04:02.000Z","description":"This IG is built in order to describe the IG tooling in Austria. (built Wed, Oct 22, 2025 13:51+0200+02:00)"},{"name":"sk.registry.core.r5","version":"4.0.0","fhirVersion":"5.0.0","canonical":"http://simplifier.net/packages/sk.registry.core.r5","kind":"fhir.ig","url":"https://packages2.fhir.org/web/sk.registry.core.r5-4.0.0.tgz","date":"2025-10-22T15:26:53.000Z","description":"Slovak Registry Data modeled using HL7 FHIR R5"},{"name":"de.medizininformatikinitiative.kerndatensatz.prozedur","version":"2025.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.medizininformatikinitiative.kerndatensatz.prozedur","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.medizininformatikinitiative.kerndatensatz.prozedur-2025.0.1.tgz","date":"2025-10-22T17:56:09.000Z","description":"Medizininformatik Initiative - Modul Prozedur"},{"name":"bd.fhir.core","version":"0.2.0","fhirVersion":"4.0.1","canonical":"https://fhir.dghs.gov.bd/core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/bd.fhir.core-0.2.0.tgz","date":"2025-10-23T00:10:57.000Z","description":"This Implementation Guide defines the Bangladesh Core FHIR profiles, value sets, code systems, and implementation rules for national digital health systems. (built Fri, Oct 3, 2025 12:29+0000+00:00)"},{"name":"nictiz.fhir.nl.stu3.zib2017","version":"2.3.2","fhirVersion":"3.0.1","canonical":"http://simplifier.net/packages/nictiz.fhir.nl.stu3.zib2017","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nictiz.fhir.nl.stu3.zib2017-2.3.2.tgz","date":"2025-10-23T09:02:10.000Z","description":"Nictiz NL package of FHIR STU3 conformance resources for HCIM Release 2017. Includes MedMij and HL7 NL.\r\n\r\nHCIMs: https://zibs.nl/wiki/HCIM_Release_2017(EN)"},{"name":"nictiz.fhir.nl.r4.labexchange","version":"3.0.0-beta.4","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/nictiz.fhir.nl.r4.labexchange","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nictiz.fhir.nl.r4.labexchange-3.0.0-beta.4.tgz","date":"2025-10-24T10:01:06.000Z","description":"Nictiz NL package of FHIR R4 conformance resources for Lab Exchange."},{"name":"rki.demis.common.strict","version":"3.0.0-rc.4","fhirVersion":"4.0.1","canonical":"https://demis.rki.de/fhir/common","kind":"fhir.ig","url":"https://packages2.fhir.org/web/rki.demis.common.strict-3.0.0-rc.4.tgz","date":"2025-10-24T12:03:36.000Z","description":"DEMIS-Basismeldeinhalte Strikt"},{"name":"rki.demis.laboratory.strict","version":"5.0.0-rc.1","fhirVersion":"4.0.1","canonical":"https://demis.rki.de/fhir/demis","kind":"fhir.ig","url":"https://packages2.fhir.org/web/rki.demis.laboratory.strict-5.0.0-rc.1.tgz","date":"2025-10-24T13:44:24.000Z","description":"DEMIS-Erregernachweismeldung Strikt"},{"name":"ca.on.hrm.r4","version":"1.0.1-snapshot1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.hrm.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.hrm.r4-1.0.1-snapshot1.tgz","date":"2025-10-26T22:44:37.000Z","description":"Implementation Guide for the Ontario HRM\r\n"},{"name":"de.medizininformatikinitiative.kerndatensatz.fall","version":"2025.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.medizininformatikinitiative.kerndatensatz.fall","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.medizininformatikinitiative.kerndatensatz.fall-2025.0.1.tgz","date":"2025-10-28T20:31:42.000Z","description":"Medizininformatik Initiative - Modul Fall"},{"name":"hl7.fhir.r5.corexml","version":"5.0.0","fhirVersion":"5.0.0","canonical":"http://hl7.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.r5.corexml-5.0.0.tgz","date":"2025-10-29T00:00:32.000Z","description":"FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (XML) (built Sun, Mar 26, 2023 15:21+1100+11:00)"},{"name":"hl7.fhir.smart.dstu2","version":"1.0.0","fhirVersion":"4.0.0","canonical":"http://hl7.org/fhir/smart-app-launch","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.smart.dstu2-1.0.0.tgz","date":"2025-10-29T00:01:08.000Z"},{"name":"hl7.fhir.us.bfdr.r4","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/bfdr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.bfdr.r4-2.0.0.tgz","date":"2025-10-29T00:01:09.000Z"},{"name":"hl7.fhir.us.bfdr.r4b","version":"2.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/bfdr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.bfdr.r4b-2.0.0.tgz","date":"2025-10-29T00:01:13.000Z"},{"name":"hl7.fhir.us.bser.r4","version":"2.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/bser","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.bser.r4-2.0.0-ballot.tgz","date":"2025-10-29T00:01:17.000Z"},{"name":"hl7.fhir.us.bser.r4b","version":"2.0.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/bser","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.bser.r4b-2.0.0-ballot.tgz","date":"2025-10-29T00:01:18.000Z"},{"name":"hl7.fhir.us.cancer-reporting.r4","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/cancer-reporting","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.cancer-reporting.r4-2.0.0.tgz","date":"2025-10-29T00:01:30.000Z","description":"This implementation guide (IG) provides Health Level Seven (HL7 FHIR) resources to define standards for cancer pathology information exchange from a hospital or facility-based laboratory information system (LIS) to a hospital or facility-based electronic health record (EHR) system or to a central cancer registry. When sending between LIS and EHR systems, implementors may choose to use transport and processing modalities, such as FHIR bundles. This publication provides the data model, defined data items and their corresponding code and value sets specific to a cancer pathology synoptic report. This guide contains a library of FHIR profiles to create a cancer pathology bundle and is compliant with FHIR Release 4. (built Fri, Oct 3, 2025 14:20+0000+00:00)"},{"name":"hl7.fhir.us.cancer-reporting.r4b","version":"2.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/cancer-reporting","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.cancer-reporting.r4b-2.0.0.tgz","date":"2025-10-29T00:01:39.000Z","description":"This implementation guide (IG) provides Health Level Seven (HL7 FHIR) resources to define standards for cancer pathology information exchange from a hospital or facility-based laboratory information system (LIS) to a hospital or facility-based electronic health record (EHR) system or to a central cancer registry. When sending between LIS and EHR systems, implementors may choose to use transport and processing modalities, such as FHIR bundles. This publication provides the data model, defined data items and their corresponding code and value sets specific to a cancer pathology synoptic report. This guide contains a library of FHIR profiles to create a cancer pathology bundle and is compliant with FHIR Release 4. (built Fri, Oct 3, 2025 14:20+0000+00:00)"},{"name":"hl7.fhir.us.carin-bb.r4","version":"2.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/carin-bb","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.carin-bb.r4-2.1.0.tgz","date":"2025-10-29T00:01:45.000Z","description":"CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) (built Tue, Feb 18, 2025 18:08+0000+00:00)"},{"name":"hl7.fhir.us.carin-bb.r4b","version":"2.1.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/carin-bb","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.carin-bb.r4b-2.1.0.tgz","date":"2025-10-29T00:01:53.000Z","description":"CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) (built Tue, Feb 18, 2025 18:08+0000+00:00)"},{"name":"hl7.fhir.us.ccda.r4","version":"2.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/ccda","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.ccda.r4-2.0.0-ballot.tgz","date":"2025-10-29T00:02:03.000Z","description":"Consolidated CDA (C-CDA) is one of the most widely implemented implementation guides for CDA and covers a significant scope of clinical care. Its target of the 'common/essential' elements of healthcare is closely aligned with FHIR's focus on the '80%'. There is significant interest in industry and government in the ability to interoperate between CDA and FHIR and C-CDA is a logical starting point. Implementers and regulators have both expressed an interest in the ability to map between FHIR and C-CDA.\n\nThis Implementation Guide (IG) defines a series of FHIR profiles on the Composition resource to represent the various document types in C-CDA. This release does not directly map every C-CDA template to FHIR profiles, rather tries to accomplish the C-CDA use case using Composition resource profiles created under this project (the equivalent of Level 2 CDA documents), and begins by linking to the profiles created under the US Core project for any coded entries that would normally be included in C-CDA sections. To have a simpler, more streamlined standard that reuses existing work and focuses on the 80% that implementers actually need in production systems, the resources of US Core represents a portion of the 80% needed for coded entries for coded entries of CCD, Care Plan & Discharge Summary).\n\nThe Composition profiles in this IG do not require coded data in any section. This is a departure from C-CDA, which requires coded data for Problems, Results, Medications, etc. This departure is intentional, as the C-CDA requirement for one or more coded entries in these sections resulted in some very complicated workarounds using nullFlavors to handle the fact that sometimes a patient is not on any medications, or has no current problems. In general, FHIR takes the approach that if something is nullable, it should simply be optional to ease the burden on implementers, thus C-CDA on FHIR does not require any coded entries, but rather uses the \"required if known\" approach, meaning that if an implementer's system has data for a section that requires data under Meaningful Use, they need to send it, but if they have no data there is no need for a null entry.\n\nWe encourage feedback on these Composition profiles, and the general approach to the project as a whole. We also encourage implementers who wish to see more of the coded data from C-CDA mapped to FHIR to comment on the US Core project and make their requests known there. Once US Core creates new profiles, this project can reference them.\n\n### Scope\n\nTo represent Consolidated CDA Templates for Clinical Notes (C-CDA) 2.1 templates using FHIR profiles.\n\nThis first stage of the project defines all the C-CDA document-level profiles on the Composition resource and contained sections.\n\nAny coded data used by sections will be represented using relevant U.S. Core FHIR profiles where they exist. FHIR profiles defined by other work groups or unconstrained FHIR resources may also be referenced if no appropriate US Core Profile exist.\n\nFor further information see the C-CDA specification here: http://www.hl7.org/implement/standards/product_brief.cfm?product_id=408. (built Tue, Dec 17, 2024 21:40+0000+00:00)"},{"name":"hl7.fhir.us.ccda.r4b","version":"2.0.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/ccda","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.ccda.r4b-2.0.0-ballot.tgz","date":"2025-10-29T00:02:10.000Z","description":"Consolidated CDA (C-CDA) is one of the most widely implemented implementation guides for CDA and covers a significant scope of clinical care. Its target of the 'common/essential' elements of healthcare is closely aligned with FHIR's focus on the '80%'. There is significant interest in industry and government in the ability to interoperate between CDA and FHIR and C-CDA is a logical starting point. Implementers and regulators have both expressed an interest in the ability to map between FHIR and C-CDA.\n\nThis Implementation Guide (IG) defines a series of FHIR profiles on the Composition resource to represent the various document types in C-CDA. This release does not directly map every C-CDA template to FHIR profiles, rather tries to accomplish the C-CDA use case using Composition resource profiles created under this project (the equivalent of Level 2 CDA documents), and begins by linking to the profiles created under the US Core project for any coded entries that would normally be included in C-CDA sections. To have a simpler, more streamlined standard that reuses existing work and focuses on the 80% that implementers actually need in production systems, the resources of US Core represents a portion of the 80% needed for coded entries for coded entries of CCD, Care Plan & Discharge Summary).\n\nThe Composition profiles in this IG do not require coded data in any section. This is a departure from C-CDA, which requires coded data for Problems, Results, Medications, etc. This departure is intentional, as the C-CDA requirement for one or more coded entries in these sections resulted in some very complicated workarounds using nullFlavors to handle the fact that sometimes a patient is not on any medications, or has no current problems. In general, FHIR takes the approach that if something is nullable, it should simply be optional to ease the burden on implementers, thus C-CDA on FHIR does not require any coded entries, but rather uses the \"required if known\" approach, meaning that if an implementer's system has data for a section that requires data under Meaningful Use, they need to send it, but if they have no data there is no need for a null entry.\n\nWe encourage feedback on these Composition profiles, and the general approach to the project as a whole. We also encourage implementers who wish to see more of the coded data from C-CDA mapped to FHIR to comment on the US Core project and make their requests known there. Once US Core creates new profiles, this project can reference them.\n\n### Scope\n\nTo represent Consolidated CDA Templates for Clinical Notes (C-CDA) 2.1 templates using FHIR profiles.\n\nThis first stage of the project defines all the C-CDA document-level profiles on the Composition resource and contained sections.\n\nAny coded data used by sections will be represented using relevant U.S. Core FHIR profiles where they exist. FHIR profiles defined by other work groups or unconstrained FHIR resources may also be referenced if no appropriate US Core Profile exist.\n\nFor further information see the C-CDA specification here: http://www.hl7.org/implement/standards/product_brief.cfm?product_id=408. (built Tue, Dec 17, 2024 21:40+0000+00:00)"},{"name":"hl7.fhir.us.cdc-opioid-cpg.r4","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/cdc-opioid-cpg","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.cdc-opioid-cpg.r4-1.0.0-ballot.tgz","date":"2025-10-29T00:02:13.000Z","description":"Defines exchange expectations for systems that implement the 2022 CDC Clinical Practice Guideline for Prescribing Opioids, both in terms of the data required to evaluate whether recommendations are applicable, as well as the data required to represent proposals resulting from those recommendations. (built Fri, Aug 1, 2025 20:38+0000+00:00)"},{"name":"hl7.fhir.us.cdc-opioid-cpg.r4b","version":"1.0.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/cdc-opioid-cpg","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.cdc-opioid-cpg.r4b-1.0.0-ballot.tgz","date":"2025-10-29T00:02:16.000Z","description":"Defines exchange expectations for systems that implement the 2022 CDC Clinical Practice Guideline for Prescribing Opioids, both in terms of the data required to evaluate whether recommendations are applicable, as well as the data required to represent proposals resulting from those recommendations. (built Fri, Aug 1, 2025 20:38+0000+00:00)"},{"name":"hl7.fhir.us.central-cancer-registry-reporting.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/central-cancer-registry-reporting","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.central-cancer-registry-reporting.r4-1.0.0.tgz","date":"2025-10-29T00:02:20.000Z","description":"The Central Cancer Registry Reporting Content IG provides healthcare organizations the necessary data exchange mechanisms to report cancer data to public health agencies. (built Fri, May 31, 2024 13:10+0000+00:00)"},{"name":"hl7.fhir.us.central-cancer-registry-reporting.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/central-cancer-registry-reporting","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.central-cancer-registry-reporting.r4b-1.0.0.tgz","date":"2025-10-29T00:02:22.000Z","description":"The Central Cancer Registry Reporting Content IG provides healthcare organizations the necessary data exchange mechanisms to report cancer data to public health agencies. (built Fri, May 31, 2024 13:10+0000+00:00)"},{"name":"hl7.fhir.us.codex-radiation-therapy.r4","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/codex-radiation-therapy","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.codex-radiation-therapy.r4-2.0.0.tgz","date":"2025-10-29T00:02:28.000Z","description":"CodeX™ Radiation Therapy is an initiative intended to assemble a core set of structured data elements for radiation therapy electronic health records. (built Mon, Feb 17, 2025 23:55+0000+00:00)"},{"name":"hl7.fhir.us.codex-radiation-therapy.r4b","version":"2.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/codex-radiation-therapy","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.codex-radiation-therapy.r4b-2.0.0.tgz","date":"2025-10-29T00:02:35.000Z","description":"CodeX™ Radiation Therapy is an initiative intended to assemble a core set of structured data elements for radiation therapy electronic health records. (built Mon, Feb 17, 2025 23:55+0000+00:00)"},{"name":"hl7.fhir.us.core.3.1.1","version":"3.1.1","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/core/3.1.1","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.core.3.1.1-3.1.1.tgz","date":"2025-10-29T00:02:38.000Z"},{"name":"hl7.fhir.us.core.r4","version":"8.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.core.r4-8.0.0.tgz","date":"2025-10-29T00:03:08.000Z","description":"The US Core Implementation Guide is based on FHIR Version R4 and defines the minimum conformance requirements for accessing patient data. The Argonaut pilot implementations, ONC 2015 Edition Common Clinical Data Set (CCDS), and ONC U.S. Core Data for Interoperability (USCDI) v1 provided the requirements for this guide. The prior Argonaut search and vocabulary requirements, based on FHIR DSTU2, are updated in this guide to support FHIR Version R4. This guide was used as the basis for further testing and guidance by the Argonaut Project Team to provide additional content and guidance specific to Data Query Access for purpose of ONC Certification testing. These profiles are the foundation for future US Realm FHIR implementation guides. In addition to Argonaut, they are used by DAF-Research, QI-Core, and CIMI. Under the guidance of HL7 and the HL7 US Realm Steering Committee, the content will expand in future versions to meet the needs specific to the US Realm.\nThese requirements were originally developed, balloted, and published in FHIR DSTU2 as part of the Office of the National Coordinator for Health Information Technology (ONC) sponsored Data Access Framework (DAF) project. For more information on how DAF became US Core see the US Core change notes. (built Tue, Jun 10, 2025 18:27+0000+00:00)"},{"name":"hl7.fhir.us.core.r4b","version":"8.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.core.r4b-8.0.0.tgz","date":"2025-10-29T00:03:33.000Z","description":"The US Core Implementation Guide is based on FHIR Version R4 and defines the minimum conformance requirements for accessing patient data. The Argonaut pilot implementations, ONC 2015 Edition Common Clinical Data Set (CCDS), and ONC U.S. Core Data for Interoperability (USCDI) v1 provided the requirements for this guide. The prior Argonaut search and vocabulary requirements, based on FHIR DSTU2, are updated in this guide to support FHIR Version R4. This guide was used as the basis for further testing and guidance by the Argonaut Project Team to provide additional content and guidance specific to Data Query Access for purpose of ONC Certification testing. These profiles are the foundation for future US Realm FHIR implementation guides. In addition to Argonaut, they are used by DAF-Research, QI-Core, and CIMI. Under the guidance of HL7 and the HL7 US Realm Steering Committee, the content will expand in future versions to meet the needs specific to the US Realm.\nThese requirements were originally developed, balloted, and published in FHIR DSTU2 as part of the Office of the National Coordinator for Health Information Technology (ONC) sponsored Data Access Framework (DAF) project. For more information on how DAF became US Core see the US Core change notes. (built Tue, Jun 10, 2025 18:27+0000+00:00)"},{"name":"hl7.fhir.us.core.v700","version":"7.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/core/v700","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.core.v700-7.0.0.tgz","date":"2025-10-29T00:03:36.000Z"},{"name":"hl7.fhir.us.cqfmeasures.r4","version":"5.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/cqfmeasures","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.cqfmeasures.r4-5.0.0.tgz","date":"2025-10-29T00:03:46.000Z","description":"The Fast Healthcare Interoperability Resource (FHIR) Quality Measure Implementation Guide (this IG) describes an approach to representing Quality Measures (QMs) using the FHIR Clinical Reasoning Module and Clinical Quality Language (CQL) in the US Realm. However, this Implementation Guide can be usable for multiple use cases across domains, and much of the content is likely to be usable outside the US Realm. (built Mon, Nov 4, 2024 20:29+0000+00:00)"},{"name":"hl7.fhir.us.cqfmeasures.r4b","version":"5.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/cqfmeasures","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.cqfmeasures.r4b-5.0.0.tgz","date":"2025-10-29T00:04:12.000Z","description":"The Fast Healthcare Interoperability Resource (FHIR) Quality Measure Implementation Guide (this IG) describes an approach to representing Quality Measures (QMs) using the FHIR Clinical Reasoning Module and Clinical Quality Language (CQL) in the US Realm. However, this Implementation Guide can be usable for multiple use cases across domains, and much of the content is likely to be usable outside the US Realm. (built Mon, Nov 4, 2024 20:29+0000+00:00)"},{"name":"hl7.fhir.us.cql.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/cql","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.cql.r4-1.0.0.tgz","date":"2025-10-29T00:04:16.000Z","description":"This implementation guide contains architectural guidance and re-usable libraries that facilitate the use of Clinical Quality Language (CQL) with FHIR in the US Realm, with an initial use case of Prior Authorization Support Questionnaires as described in the DaVinci Documentation Templates and Rules (DTR) implementation guide. Much of the guidance and content presented here is built on work done in the quality measurement domain, including patterns established by measure developers as part of testing and developing quality measures for use with FHIR. These patterns have been generalized to support US Core as well as harmonized to be usable across use cases. (built Wed, Oct 22, 2025 20:47+0000+00:00)"},{"name":"hl7.fhir.us.cql.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/cql","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.cql.r4b-1.0.0.tgz","date":"2025-10-29T00:04:19.000Z","description":"This implementation guide contains architectural guidance and re-usable libraries that facilitate the use of Clinical Quality Language (CQL) with FHIR in the US Realm, with an initial use case of Prior Authorization Support Questionnaires as described in the DaVinci Documentation Templates and Rules (DTR) implementation guide. Much of the guidance and content presented here is built on work done in the quality measurement domain, including patterns established by measure developers as part of testing and developing quality measures for use with FHIR. These patterns have been generalized to support US Core as well as harmonized to be usable across use cases. (built Wed, Oct 22, 2025 20:47+0000+00:00)"},{"name":"hl7.fhir.us.dafresearch","version":"1.0.0","fhirVersion":"3.0.1","canonical":"http://hl7.org/fhir/us/daf-research","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.dafresearch-1.0.0.tgz","date":"2025-10-29T00:04:20.000Z"},{"name":"hl7.fhir.us.davinci-alerts.r4","version":"1.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-alerts","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-alerts.r4-1.1.0.tgz","date":"2025-10-29T00:04:27.000Z","description":"This implementation guide describes a method for the communication of relevant notifications to support the real-time exchange of information that impacts patient care and value based or risk based services. Providers and Payers may need to be notified when activities occur that impact a patient’s care. This may be as traditional as a notification of an admission or transfer to or discharge from a care setting. It also includes notifications about changes in treatment such as a new or different medication, or changes in patient status like a new diagnosis. These notifications provide information that can improve care management and care coordination as well as act as the trigger for quality programs and other patient focused activities (for example, risk adjustment). By allowing the patient’s healthcare providers to be better informed and able to take actions and intervene earlier, the twin goals of better patient care and reduced cost of care may be met. (built Tue, Apr 8, 2025 19:04+0000+00:00)"},{"name":"hl7.fhir.us.davinci-alerts.r4b","version":"1.1.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/davinci-alerts","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-alerts.r4b-1.1.0.tgz","date":"2025-10-29T00:04:30.000Z","description":"This implementation guide describes a method for the communication of relevant notifications to support the real-time exchange of information that impacts patient care and value based or risk based services. Providers and Payers may need to be notified when activities occur that impact a patient’s care. This may be as traditional as a notification of an admission or transfer to or discharge from a care setting. It also includes notifications about changes in treatment such as a new or different medication, or changes in patient status like a new diagnosis. These notifications provide information that can improve care management and care coordination as well as act as the trigger for quality programs and other patient focused activities (for example, risk adjustment). By allowing the patient’s healthcare providers to be better informed and able to take actions and intervene earlier, the twin goals of better patient care and reduced cost of care may be met. (built Tue, Apr 8, 2025 18:46+0000+00:00)"},{"name":"hl7.fhir.us.davinci-atr.r4","version":"2.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-atr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-atr.r4-2.1.0.tgz","date":"2025-10-29T00:04:37.000Z","description":"Exchange of member attribution list between payers and providers (built Fri, May 16, 2025 17:34+0000+00:00)"},{"name":"hl7.fhir.us.davinci-atr.r4b","version":"2.1.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/davinci-atr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-atr.r4b-2.1.0.tgz","date":"2025-10-29T00:04:45.000Z","description":"Exchange of member attribution list between payers and providers (built Fri, May 16, 2025 17:34+0000+00:00)"},{"name":"hl7.fhir.us.davinci-cdex.r4","version":"2.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-cdex","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-cdex.r4-2.1.0.tgz","date":"2025-10-29T00:04:53.000Z","description":"This IG provides detailed guidance that helps implementers use FHIR-based interactions to support specific exchanges of clinical data between providers and payers (or other providers). (built Tue, Feb 11, 2025 03:51+1100+11:00)"},{"name":"hl7.fhir.us.davinci-cdex.r4b","version":"2.1.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/davinci-cdex","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-cdex.r4b-2.1.0.tgz","date":"2025-10-29T00:04:59.000Z","description":"This IG provides detailed guidance that helps implementers use FHIR-based interactions to support specific exchanges of clinical data between providers and payers (or other providers). (built Tue, Feb 11, 2025 03:51+1100+11:00)"},{"name":"hl7.fhir.us.davinci-crd.r4","version":"2.2.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-crd","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-crd.r4-2.2.0-ballot.tgz","date":"2025-10-29T00:05:08.000Z","description":"Guidelines for conveying coverage requirements to clinicians when planning treatment (built Wed, Aug 6, 2025 17:27+0000+00:00)"},{"name":"hl7.fhir.us.davinci-crd.r4b","version":"2.2.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/davinci-crd","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-crd.r4b-2.2.0-ballot.tgz","date":"2025-10-29T00:05:16.000Z","description":"Guidelines for conveying coverage requirements to clinicians when planning treatment (built Wed, Aug 6, 2025 17:27+0000+00:00)"},{"name":"hl7.fhir.us.davinci-crd.stu3","version":"0.1.0","fhirVersion":"3.0.1","canonical":"http://hl7.org/fhir/us/davinci-crd/STU3","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-crd.stu3-0.1.0.tgz","date":"2025-10-29T00:05:23.000Z","description":"Guidelines for conveying coverage requirements to clinicians when planning treatment"},{"name":"hl7.fhir.us.davinci-deqm.r4","version":"5.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-deqm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-deqm.r4-5.0.0.tgz","date":"2025-10-29T00:05:41.000Z"},{"name":"hl7.fhir.us.davinci-deqm.r4b","version":"5.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/davinci-deqm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-deqm.r4b-5.0.0.tgz","date":"2025-10-29T00:05:49.000Z"},{"name":"hl7.fhir.us.davinci-deqm.stu3","version":"0.2.0","fhirVersion":"3.0.1","canonical":"http://hl7.org/fhir/us/davinci-deqm/STU3","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-deqm.stu3-0.2.0.tgz","date":"2025-10-29T00:05:53.000Z"},{"name":"hl7.fhir.us.davinci-drug-formulary.r4","version":"2.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-drug-formulary","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-drug-formulary.r4-2.1.0.tgz","date":"2025-10-29T00:05:58.000Z","description":"DaVinci Payer Data Exchange (PDex) US Drug Formulary\" (built Wed, Feb 26, 2025 18:01+0000+00:00)"},{"name":"hl7.fhir.us.davinci-drug-formulary.r4b","version":"2.1.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/davinci-drug-formulary","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-drug-formulary.r4b-2.1.0.tgz","date":"2025-10-29T00:06:10.000Z","description":"DaVinci Payer Data Exchange (PDex) US Drug Formulary\" (built Wed, Feb 26, 2025 18:01+0000+00:00)"},{"name":"hl7.fhir.us.davinci-dtr.r4","version":"2.2.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-dtr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-dtr.r4-2.2.0-ballot.tgz","date":"2025-10-29T00:06:19.000Z","description":"The Documentation Templates and Rules (DTR) Implementation Guide (IG) specifies how payer rules can be executed in a provider context to ensure that documentation requirements are met. The IG is a companion to the Coverage Requirements Discovery (CRD) IG, which uses CDS Hooks to query payers to determine if there are documentation requirements for a proposed medication, procedure or other service. (built Mon, Aug 4, 2025 15:40+0000+00:00)"},{"name":"hl7.fhir.us.davinci-dtr.r4b","version":"2.2.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/davinci-dtr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-dtr.r4b-2.2.0-ballot.tgz","date":"2025-10-29T00:06:31.000Z","description":"The Documentation Templates and Rules (DTR) Implementation Guide (IG) specifies how payer rules can be executed in a provider context to ensure that documentation requirements are met. The IG is a companion to the Coverage Requirements Discovery (CRD) IG, which uses CDS Hooks to query payers to determine if there are documentation requirements for a proposed medication, procedure or other service. (built Mon, Aug 4, 2025 15:40+0000+00:00)"},{"name":"hl7.fhir.us.davinci-hrex.r4","version":"1.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-hrex","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-hrex.r4-1.1.0.tgz","date":"2025-10-29T00:06:42.000Z","description":"The Da Vinci Payer Health Record exchange (HRex) Framework/library specifies the FHIR elements used in multiple Da Vinci implementation guides. This includes FHIR profiles, functions, operations, and constraints on other specifications such as CDS-Hooks and other aspects of Da Vinci Use Cases that are common across more than a single use case.\\n\\nDa Vinci HRex Implementation Guide (IG) will make use of US Core profiles that are based on the FHIR R4 specification wherever practical. The HRex IG will use the HL7 FHIR Release 4/US Core STU3 specification as its base but will provide additional guidance and documentation to support implementations that follow the HL7 FHIR STU3/US Core STU2 and HL7 FHIR DSTU2/Argonaut specifications.\\n\\nThe HRex profiles documented in this IG will be used to exchange data between providers systems (e.g. EHRs) and other providers, payers, and third-party applications where appropriate. In addition, exchanges from payer systems to providers, other payers, and third-party applications are supported by the HRex profiles and operations.\\n\\nHRex may define new extensions, profiles, value sets, constraints/extension to other specification (e.g. specific CDS-Hooks) that are specific Da Vinci requirements. Where appropriate these Da Vinci specific artifacts will be promoted for incorporation into the future versions of existing standards (e.g. R4 US Core profiles) and deprecated in this guide on publication in the updated standard. (built Tue, Dec 10, 2024 17:09+0000+00:00)"},{"name":"hl7.fhir.us.davinci-hrex.r4b","version":"1.1.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/davinci-hrex","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-hrex.r4b-1.1.0.tgz","date":"2025-10-29T00:06:47.000Z","description":"The Da Vinci Payer Health Record exchange (HRex) Framework/library specifies the FHIR elements used in multiple Da Vinci implementation guides. This includes FHIR profiles, functions, operations, and constraints on other specifications such as CDS-Hooks and other aspects of Da Vinci Use Cases that are common across more than a single use case.\\n\\nDa Vinci HRex Implementation Guide (IG) will make use of US Core profiles that are based on the FHIR R4 specification wherever practical. The HRex IG will use the HL7 FHIR Release 4/US Core STU3 specification as its base but will provide additional guidance and documentation to support implementations that follow the HL7 FHIR STU3/US Core STU2 and HL7 FHIR DSTU2/Argonaut specifications.\\n\\nThe HRex profiles documented in this IG will be used to exchange data between providers systems (e.g. EHRs) and other providers, payers, and third-party applications where appropriate. In addition, exchanges from payer systems to providers, other payers, and third-party applications are supported by the HRex profiles and operations.\\n\\nHRex may define new extensions, profiles, value sets, constraints/extension to other specification (e.g. specific CDS-Hooks) that are specific Da Vinci requirements. Where appropriate these Da Vinci specific artifacts will be promoted for incorporation into the future versions of existing standards (e.g. R4 US Core profiles) and deprecated in this guide on publication in the updated standard. (built Tue, Dec 10, 2024 17:09+0000+00:00)"},{"name":"hl7.fhir.us.davinci-pas.r4","version":"2.2.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-pas","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-pas.r4-2.2.0-ballot.tgz","date":"2025-10-29T00:06:55.000Z","description":"Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Wed, Jul 30, 2025 00:50+0000+00:00)"},{"name":"hl7.fhir.us.davinci-pas.r4b","version":"2.2.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/davinci-pas","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-pas.r4b-2.2.0-ballot.tgz","date":"2025-10-29T00:07:09.000Z","description":"Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Wed, Jul 30, 2025 00:50+0000+00:00)"},{"name":"hl7.fhir.us.davinci-pct.r4","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-pct","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-pct.r4-2.0.0.tgz","date":"2025-10-29T00:07:18.000Z","description":"To support the request for cost information for specific items and services from the payer and return them in near real-time to allow effective decision making by the patient in consultation with the 'ordering' provider. (built Wed, Oct 8, 2025 20:40+0000+00:00)"},{"name":"hl7.fhir.us.davinci-pct.r4b","version":"2.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/davinci-pct","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-pct.r4b-2.0.0.tgz","date":"2025-10-29T00:07:26.000Z","description":"To support the request for cost information for specific items and services from the payer and return them in near real-time to allow effective decision making by the patient in consultation with the 'ordering' provider. (built Wed, Oct 8, 2025 20:40+0000+00:00)"},{"name":"hl7.fhir.us.davinci-pdex-plan-net.r4","version":"1.2.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-pdex-plan-net","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-pdex-plan-net.r4-1.2.0.tgz","date":"2025-10-29T00:07:29.000Z","description":"Da Vinci PDex Plan Net (built Tue, Feb 25, 2025 20:09+0000+00:00)"},{"name":"hl7.fhir.us.davinci-pdex-plan-net.r4b","version":"1.2.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/davinci-pdex-plan-net","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-pdex-plan-net.r4b-1.2.0.tgz","date":"2025-10-29T00:07:31.000Z","description":"Da Vinci PDex Plan Net (built Tue, Feb 25, 2025 20:09+0000+00:00)"},{"name":"hl7.fhir.us.davinci-pdex.r4","version":"2.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-pdex","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-pdex.r4-2.1.0.tgz","date":"2025-10-29T00:07:38.000Z","description":"This specification has undergone ballot and connectathon testing. It is expected to continue to evolve, possibly significantly, as part of that process.\nFeedback is welcome and may be submitted through the FHIR JIRA tracker indicating US Da Vinci PDex as the specification. If balloting on this IG, please submit your comments via the tracker and reference them in your ballot submission implementation guide.\n\nThis guide can be reviewed offline. Go to the Downloads section. Click on the link to download the full Implementation Guide as a zip file. Expand the zip file and use a web browser to launch the index.html file in the directory created by the zip extract process. External hyperlinks in the guide will not be available unless you have an active internet connection. \n\n[Financial Management](https://confluence.hl7.org/display/FM/Financial+Management+Home) is the Sponsoring Work Group for this Implementation Guide.\n\n**The Payer Data Exchange (PDex) Implementation Guide (IG) is provided for Payers/Health Plans to enable them to create a Member's Health History using clinical resources (based on US Core 3.1.1 and 6.1.0 Profiles based on FHIR R4) which can be understood by providers and, if they choose to, committed to their Electronic Medical Records (EMR) System.**\n\nThe PDex work group has made changes to the original version of the IG following the publication of the final CMS Interoperability and Patient Access Rule (CMS-9115_ and in STU 2.1 the IG has been expanded to meet the requirements of the CMS Prior Authorization Rule (CMS-0057).\n\nThis IG uses the same Member Health History \"payload\" for member-authorized exchange of information with other Health Plans, with Providers and with Third-Party Applications. It describes the interaction patterns that, when followed, allow the various parties involved in managing healthcare and payer data to more easily integrate and exchange data securely and effectively.\n\nThis IG covers the exchange of:\n- Claims-based information (without financials)\n- Clinical Information (such as Lab Results, Allergies and Conditions)\n- Prior Authorization information\n\nThis IG covers the exchange of this information using US Core and Da Vinci Health Record Exchange (HRex) Profiles. This superset of clinical profiles forms the Health Plan Member's Health History. \n\nThis IG covers the exchange of a Member's Health History in the following scenarios:\n- Provider requested exchange using SMART-on-FHIR Bulk exchange\n- Health Plan Exchange using SMART-on-FHIR\n- Member-authorized Health Plan to Health Plan exchange\n- Member-authorized Health Plan to Third-Party Application exchange\n\nThe latter two scenarios are provided to meet the requirements identified in the CMS Interoperability and Patient Access Final Rule.\n\n**There are items in this guide that are subject to update**. This includes:\n- Value Sets\n- Vocabularies (X12, NUBC etc.)\n- Examples\n\n**The Vocabulary, Value Sets and codings used to express data in this IG are subject to review and will be reconciled with** [X12](http://www.x12.org).\n\nSee the [Table of Contents](toc.html) for more information.\n (built Wed, Jun 18, 2025 03:12+0000+00:00)"},{"name":"hl7.fhir.us.davinci-pdex.r4b","version":"2.1.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/davinci-pdex","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-pdex.r4b-2.1.0.tgz","date":"2025-10-29T00:07:53.000Z","description":"This specification has undergone ballot and connectathon testing. It is expected to continue to evolve, possibly significantly, as part of that process.\nFeedback is welcome and may be submitted through the FHIR JIRA tracker indicating US Da Vinci PDex as the specification. If balloting on this IG, please submit your comments via the tracker and reference them in your ballot submission implementation guide.\n\nThis guide can be reviewed offline. Go to the Downloads section. Click on the link to download the full Implementation Guide as a zip file. Expand the zip file and use a web browser to launch the index.html file in the directory created by the zip extract process. External hyperlinks in the guide will not be available unless you have an active internet connection. \n\n[Financial Management](https://confluence.hl7.org/display/FM/Financial+Management+Home) is the Sponsoring Work Group for this Implementation Guide.\n\n**The Payer Data Exchange (PDex) Implementation Guide (IG) is provided for Payers/Health Plans to enable them to create a Member's Health History using clinical resources (based on US Core 3.1.1 and 6.1.0 Profiles based on FHIR R4) which can be understood by providers and, if they choose to, committed to their Electronic Medical Records (EMR) System.**\n\nThe PDex work group has made changes to the original version of the IG following the publication of the final CMS Interoperability and Patient Access Rule (CMS-9115_ and in STU 2.1 the IG has been expanded to meet the requirements of the CMS Prior Authorization Rule (CMS-0057).\n\nThis IG uses the same Member Health History \"payload\" for member-authorized exchange of information with other Health Plans, with Providers and with Third-Party Applications. It describes the interaction patterns that, when followed, allow the various parties involved in managing healthcare and payer data to more easily integrate and exchange data securely and effectively.\n\nThis IG covers the exchange of:\n- Claims-based information (without financials)\n- Clinical Information (such as Lab Results, Allergies and Conditions)\n- Prior Authorization information\n\nThis IG covers the exchange of this information using US Core and Da Vinci Health Record Exchange (HRex) Profiles. This superset of clinical profiles forms the Health Plan Member's Health History. \n\nThis IG covers the exchange of a Member's Health History in the following scenarios:\n- Provider requested exchange using SMART-on-FHIR Bulk exchange\n- Health Plan Exchange using SMART-on-FHIR\n- Member-authorized Health Plan to Health Plan exchange\n- Member-authorized Health Plan to Third-Party Application exchange\n\nThe latter two scenarios are provided to meet the requirements identified in the CMS Interoperability and Patient Access Final Rule.\n\n**There are items in this guide that are subject to update**. This includes:\n- Value Sets\n- Vocabularies (X12, NUBC etc.)\n- Examples\n\n**The Vocabulary, Value Sets and codings used to express data in this IG are subject to review and will be reconciled with** [X12](http://www.x12.org).\n\nSee the [Table of Contents](toc.html) for more information.\n (built Wed, Jun 18, 2025 03:12+0000+00:00)"},{"name":"hl7.fhir.us.davinci-pr.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-pr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-pr.r4-1.0.0.tgz","date":"2025-10-29T00:07:58.000Z"},{"name":"hl7.fhir.us.davinci-pr.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/davinci-pr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-pr.r4b-1.0.0.tgz","date":"2025-10-29T00:08:03.000Z"},{"name":"hl7.fhir.us.davinci-ra.r4","version":"2.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-ra","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-ra.r4-2.1.0.tgz","date":"2025-10-29T00:08:08.000Z","description":"The Da Vinci Fast Healthcare Interoperability Resource (FHIR) Risk Adjustment Implementation Guide (this IG) describes exchange of risk-based coding gaps among stakeholders such as payers, providers, and government care programs in support of driving towards accurate and complete documentation of health conditions that would lead to more accurate risk-adjustment payment calculations. (built Wed, Jul 2, 2025 02:58+0000+00:00)"},{"name":"hl7.fhir.us.davinci-ra.r4b","version":"2.1.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/davinci-ra","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-ra.r4b-2.1.0.tgz","date":"2025-10-29T00:08:18.000Z","description":"The Da Vinci Fast Healthcare Interoperability Resource (FHIR) Risk Adjustment Implementation Guide (this IG) describes exchange of risk-based coding gaps among stakeholders such as payers, providers, and government care programs in support of driving towards accurate and complete documentation of health conditions that would lead to more accurate risk-adjustment payment calculations. (built Wed, Jul 2, 2025 02:58+0000+00:00)"},{"name":"hl7.fhir.us.davinci-vbpr.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-vbpr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-vbpr.r4-1.0.0.tgz","date":"2025-10-29T00:08:23.000Z","description":"The Da Vinci Fast Healthcare Interoperability Resource (FHIR) Value-Based Performance Reporting Implementation Guide (this IG) specifies standard representations of value-based performance reports that are exchanged payers and providers, which include performance metrics on financial, utilization, etc. and quality measures for varies types of value-based contracts. (built Mon, Jun 17, 2024 14:00+0000+00:00)"},{"name":"hl7.fhir.us.davinci-vbpr.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/davinci-vbpr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-vbpr.r4b-1.0.0.tgz","date":"2025-10-29T00:08:27.000Z","description":"The Da Vinci Fast Healthcare Interoperability Resource (FHIR) Value-Based Performance Reporting Implementation Guide (this IG) specifies standard representations of value-based performance reports that are exchanged payers and providers, which include performance metrics on financial, utilization, etc. and quality measures for varies types of value-based contracts. (built Mon, Jun 17, 2024 14:00+0000+00:00)"},{"name":"hl7.fhir.us.ecr.r4","version":"2.1.2","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/ecr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.ecr.r4-2.1.2.tgz","date":"2025-10-29T00:08:37.000Z","description":"# Introduction and Purpose\n\nWith the adoption and maturing of Electronic Health Records (EHRs) there are opportunities to better support public health surveillance as well as to better support the delivery of relevant public health information to clinical care. Electronic Case Reporting (eCR) can provide more complete and timely case data, support disease / condition monitoring, and assist in outbreak management and control. It can also improve bidirectional communications through the delivery of public health information in the context of a patient's condition and local disease trends and by facilitating ad hoc communications. eCR will also reduce healthcare provider burden by automating the completion of legal reporting requirements.\n\nWith the advent of FHIR standards, there is a need for FHIR implementation guidance to specify appropriate resources and transactions needed for the eCR process. FHIR offers opportunities to further enable automated triggering and reporting of cases from EHRs, to ease implementation and integration, to support the acquisition of public health investigation supplemental data, and to connect public health information (e.g., guidelines) with clinical workflows. Over time, FHIR may also support the distribution of reporting rules to clinical care to better align data authorities and make broader clinical data available to public health decision support services inside the clinical care environment.\n\nFor more supporting information, use cases, and other background context and material, see Volume 1 of both the [HL7 CDA R2 Electronic Initial Case Report (eICR) Standard for Trial Use (STU) IG](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=436) (see the link under \"STU Documents\" for STU 2.0) and the [HL7 CDA R2 Reportability Response (RR) STU IG](https://www.hl7.org/implement/standards/product_brief.cfm?product_id=470).\n\nFor Clinical Safety Information please refer to the [FHIR Implementer’s Safety Checklist](http://hl7.org/fhir/safety.html).\n\n
\n

Known Issue:

\n

The following issue is related to a publication tooling issue. A technical correction is planned once the tooling issue has been addressed.

\n \n
\n\n# Stakeholders\n* Regulatory Agencies\n* Standards Development Organizations\n* Vendors: EHR, PHR; Health Care IT; Clinical Decision Support Systems, Public Health Surveillance Systems\n* Providers: Ambulatory and Healthcare Institutions (hospitals, long term care, mental health)\n* Local, State, Tribal and Federal Public Health Agencies (built Wed, Oct 30, 2024 20:32+0000+00:00)"},{"name":"hl7.fhir.us.ecr.r4b","version":"2.1.2","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/ecr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.ecr.r4b-2.1.2.tgz","date":"2025-10-29T00:08:42.000Z","description":"# Introduction and Purpose\n\nWith the adoption and maturing of Electronic Health Records (EHRs) there are opportunities to better support public health surveillance as well as to better support the delivery of relevant public health information to clinical care. Electronic Case Reporting (eCR) can provide more complete and timely case data, support disease / condition monitoring, and assist in outbreak management and control. It can also improve bidirectional communications through the delivery of public health information in the context of a patient's condition and local disease trends and by facilitating ad hoc communications. eCR will also reduce healthcare provider burden by automating the completion of legal reporting requirements.\n\nWith the advent of FHIR standards, there is a need for FHIR implementation guidance to specify appropriate resources and transactions needed for the eCR process. FHIR offers opportunities to further enable automated triggering and reporting of cases from EHRs, to ease implementation and integration, to support the acquisition of public health investigation supplemental data, and to connect public health information (e.g., guidelines) with clinical workflows. Over time, FHIR may also support the distribution of reporting rules to clinical care to better align data authorities and make broader clinical data available to public health decision support services inside the clinical care environment.\n\nFor more supporting information, use cases, and other background context and material, see Volume 1 of both the [HL7 CDA R2 Electronic Initial Case Report (eICR) Standard for Trial Use (STU) IG](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=436) (see the link under \"STU Documents\" for STU 2.0) and the [HL7 CDA R2 Reportability Response (RR) STU IG](https://www.hl7.org/implement/standards/product_brief.cfm?product_id=470).\n\nFor Clinical Safety Information please refer to the [FHIR Implementer’s Safety Checklist](http://hl7.org/fhir/safety.html).\n\n
\n

Known Issue:

\n

The following issue is related to a publication tooling issue. A technical correction is planned once the tooling issue has been addressed.

\n \n
\n\n# Stakeholders\n* Regulatory Agencies\n* Standards Development Organizations\n* Vendors: EHR, PHR; Health Care IT; Clinical Decision Support Systems, Public Health Surveillance Systems\n* Providers: Ambulatory and Healthcare Institutions (hospitals, long term care, mental health)\n* Local, State, Tribal and Federal Public Health Agencies (built Wed, Oct 30, 2024 20:32+0000+00:00)"},{"name":"hl7.fhir.us.eltss.r4","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/eltss","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.eltss.r4-2.0.0.tgz","date":"2025-10-29T00:08:47.000Z","description":"Provides guidance to US Realm implementers to use the FHIR for implementing access and exchange Electronic Long-Term Services and Supports (eLTSS) Dataset data elements (built Mon, May 27, 2024 02:49+0000+00:00)"},{"name":"hl7.fhir.us.eltss.r4b","version":"2.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/eltss","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.eltss.r4b-2.0.0.tgz","date":"2025-10-29T00:08:52.000Z","description":"Provides guidance to US Realm implementers to use the FHIR for implementing access and exchange Electronic Long-Term Services and Supports (eLTSS) Dataset data elements (built Mon, May 27, 2024 02:49+0000+00:00)"},{"name":"hl7.fhir.us.hai-ltcf.r4","version":"1.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/hai-ltcf","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.hai-ltcf.r4-1.1.0.tgz","date":"2025-10-29T00:08:57.000Z","description":"This implementation guide (IG) specifies standards for electronic submission of Healthcare Associated Infection (HAI) Long Term Care Facilities (LTCF) reports to the National Healthcare Safety Network (NHSN) of the Centers for Disease Control and Prevention (CDC). This IG contains a library of FHIR profiles for electronic submission of HAI LTCF reports to the NHSN.\n\nAs reports are modified and new report types are defined, CDC and Health Level Seven (HL7) will develop and publish additional constraints.\n\nThroughout this process, CDC remains the authority on NHSN data collection protocols. When healthcare enterprises choose to participate in NHSN, they must report to CDC reportable events such as identified MDRO (multidrug-resistant organism) or CDI (C. difficile infection) occurrences such as specific reportable procedures, even those without complications, and events such as a bloodstream infection, either confirmed by a positive blood culture or supported by a patients clinical symptoms. This specification opens the channel for data submission by all applications compliant with the data coding requirements defined here.\n\nNote that participation in the NHSN requires enrollment and filing of reporting plans, which are not defined by this specification. For an overview of NHSN and full information on NHSN participation requirements, see: [http://www.cdc.gov/nhsn](http://www.cdc.gov/nhsn). Provisions of the Public Health Service Act protect all data reported to NHSN from discovery through the Freedom of Information Act (FOIA).\n\n\n### Relationship to Another Standard\n\nHL7 has developed this FHIR implementation guide in parallel with the CDA implementation guide. We anticipate several STU releases on the path to a Normative Release 1 of the HL7 implementation guides for CDA and FHIR for Healthcare Associated Infection (HAI) Reports from Long Term Care Facilities (LTCF). The FHIR and CDA implementation guides will align. A change to one standard will require the same change in the other standard. \n\nIn this release, the new forms included in both the CDA and FHIR standards are:\n* **NHSN HAI LTCF Population Summary Report**: MDRO and CDI LabID Event Reporting Monthly Summary Data for LTCF\n* **NHSN HAI LTCF Single-Person Event Report**: Laboratory-identified MDRO or CDI Event for LTCF\n\nFor further details see the [NHSN website](https://www.cdc.gov/nhsn/) for reporting healthcare-associated infections in long-term care facilities.\n\n\n### Audience\n\nThe audience for this work is all developers of software systems who want to enable their systems for reporting HAI data to the NHSN.\n\n### Change Notification Process\n\nCDC maintains an e-mail list of contacts at organizations interested in or responsible for implementations of FHIR for LTCF HAI reporting to NHSN. To be added to the list, send a request with your contact information to nhsncda@cdc.gov. CDC uses the list for e-mail notifications of changes, including new data requirements. Changes may apply to this IG and to other documents such as business rules that are needed to implement and support FHIR for LTCF HAI reporting to NHSN. NHSN CDA related information may be found at https://www.cdc.gov/nhsn/cdaportal/index.html. \n\n### Acknowledgements\n\nThis implementation guide was produced and developed by Lantana Consulting Group in conjunction with the Division of Healthcare Quality Promotion in the National Center for Emerging and Zoonotic Infectious Diseases (NCEZID) at the Centers for Disease Control and Prevention (CDC). Its development and deployment are results of the dedication of the team—led by Daniel A. Pollock, M.D., Surveillance Branch Chief, Division of Healthcare Quality Promotion, NCEZID, CDC and Jeneita Bell, MD, MPH, Long-term Care Team Lead, DHQP, NCEZID, CDC—and their support of the development of interoperable data standards for the CDC’s National Healthcare Safety Network (NHSN). \n\nSpecial thanks and acknowledgment to stakeholders who participated in calls and provided feedback. Specifically, we would like to thank Cindy Frakes, Steve Herron, Jamie Gatzke, Kelly Luden, Prasath Govindarajulu from Cerner; Laura Ditz, Nancy Chi, Nichole (Nicki) Fetterman, Michael Furman, Patti Barton, Aga Lee from Point Click Care; Donna Doneski from NASL; and Denise Wassenaar, Doc DeVore, Rob Price from Matrix Care. \n\nThe best standards are those driven by business requirements. A strong set of Healthcare Associated Infection (HAI) surveillance application vendors monitor, evaluate, and test each release of this guide. \n\n\n|-----|-----|-----|-----| \n\n|Primary Editor:|Sarah Gaunt|Lantana Consulting Group|sarah.gaunt@lantanagroup.com| \n|Primary Editor:|Zabrina Gonzaga|Lantana Consulting Group|zabrina.gonzaga@lantanagroup.com| \n|Primary Editor:|Dave deRoode|Lantana Consulting Group|david.deroode@lantanagroup.com| \n|Co-Editor:|Jeneita Bell, MD, MPH|CDC|hpq8@cdc.gov| \n|Co-Editor:|Angella Antilla PhD, MSN|CDC|vtb9@cdc.gov| \n|Co-Editor:|Daniel Pollock, M.D.|CDC|DPollock@cdc.gov| \n|Co-Editor:|Ahmed Tahir|Leidos Consultant to CDC/NHSN|nmn8@cdc.gov| \n|Co-Editor:|Mindy Durrance|Leidos Consultant to CDC/NHSN|mdq1@cdc.gov| \n|Co-Editor:|Sheri Chernetsky Tejedor, MD|CDC|yei9@cdc.gov| \n|Co-Editor:|Sheila Abner|CDC|sha8@cdc.gov| \n|Co-Chair:|Erin Holt MPH|Tennessee Department of Health|erin.holt@tn.gov| \n|Co-Chair:|Laura Rappleye|Altarum|laura.rappleye@altarum.org| \n|Co-Chair:|Craig Newman|Altarum|craig.newman@altarum.org| \n|Co-Chair:|Danny Wise|Allscripts|danny.wise@allscripts.com| \n|Co-Chair:|Joginder Madra|Madra Consulting Inc.|hl7@madraconsulting.com| \n|Co-Chair:|Gaye Dolin M.S.N., R.N. |Intelligent Medical Objects |gdolin@imo-online.com| \n|Co-Chair:|Calvin Beebe|Mayo Clinic|cbeebe@mayo.edu| \n|Co-Chair:|Austin Kreisler|Leidos Consultant to CDC/NHSN|duz1@cdc.gov| \n|Co-Chair:|Andrew Statler|Cerner Corp|andrew.statler@cerner.com| \n|Co-Chair:|Sean McIlvenna| Lantana Consulting Group|sean.mcilvenna@lantanagroup.com| \n|Co-Chair:|Benjamin Flessner|Redox|benjamin@redoxengine.com| \n|Co-Editor:|Beau Bannerman|Lantana Consulting Group|beau.bannerman@lantanagroup.com| \n|Technical Editor:|Diana Wright|Lantana Consulting Group|diana.wright@lantanagroup.com| \n|Technical Editor:|Chris Hannigan|Lantana Consulting Group|chris.hannigan@lantanagroup.com| \n (built Wed, Apr 19, 2023 15:05+0000+00:00)"},{"name":"hl7.fhir.us.hai-ltcf.r4b","version":"1.1.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/hai-ltcf","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.hai-ltcf.r4b-1.1.0.tgz","date":"2025-10-29T00:09:01.000Z","description":"This implementation guide (IG) specifies standards for electronic submission of Healthcare Associated Infection (HAI) Long Term Care Facilities (LTCF) reports to the National Healthcare Safety Network (NHSN) of the Centers for Disease Control and Prevention (CDC). This IG contains a library of FHIR profiles for electronic submission of HAI LTCF reports to the NHSN.\n\nAs reports are modified and new report types are defined, CDC and Health Level Seven (HL7) will develop and publish additional constraints.\n\nThroughout this process, CDC remains the authority on NHSN data collection protocols. When healthcare enterprises choose to participate in NHSN, they must report to CDC reportable events such as identified MDRO (multidrug-resistant organism) or CDI (C. difficile infection) occurrences such as specific reportable procedures, even those without complications, and events such as a bloodstream infection, either confirmed by a positive blood culture or supported by a patients clinical symptoms. This specification opens the channel for data submission by all applications compliant with the data coding requirements defined here.\n\nNote that participation in the NHSN requires enrollment and filing of reporting plans, which are not defined by this specification. For an overview of NHSN and full information on NHSN participation requirements, see: [http://www.cdc.gov/nhsn](http://www.cdc.gov/nhsn). Provisions of the Public Health Service Act protect all data reported to NHSN from discovery through the Freedom of Information Act (FOIA).\n\n\n### Relationship to Another Standard\n\nHL7 has developed this FHIR implementation guide in parallel with the CDA implementation guide. We anticipate several STU releases on the path to a Normative Release 1 of the HL7 implementation guides for CDA and FHIR for Healthcare Associated Infection (HAI) Reports from Long Term Care Facilities (LTCF). The FHIR and CDA implementation guides will align. A change to one standard will require the same change in the other standard. \n\nIn this release, the new forms included in both the CDA and FHIR standards are:\n* **NHSN HAI LTCF Population Summary Report**: MDRO and CDI LabID Event Reporting Monthly Summary Data for LTCF\n* **NHSN HAI LTCF Single-Person Event Report**: Laboratory-identified MDRO or CDI Event for LTCF\n\nFor further details see the [NHSN website](https://www.cdc.gov/nhsn/) for reporting healthcare-associated infections in long-term care facilities.\n\n\n### Audience\n\nThe audience for this work is all developers of software systems who want to enable their systems for reporting HAI data to the NHSN.\n\n### Change Notification Process\n\nCDC maintains an e-mail list of contacts at organizations interested in or responsible for implementations of FHIR for LTCF HAI reporting to NHSN. To be added to the list, send a request with your contact information to nhsncda@cdc.gov. CDC uses the list for e-mail notifications of changes, including new data requirements. Changes may apply to this IG and to other documents such as business rules that are needed to implement and support FHIR for LTCF HAI reporting to NHSN. NHSN CDA related information may be found at https://www.cdc.gov/nhsn/cdaportal/index.html. \n\n### Acknowledgements\n\nThis implementation guide was produced and developed by Lantana Consulting Group in conjunction with the Division of Healthcare Quality Promotion in the National Center for Emerging and Zoonotic Infectious Diseases (NCEZID) at the Centers for Disease Control and Prevention (CDC). Its development and deployment are results of the dedication of the team—led by Daniel A. Pollock, M.D., Surveillance Branch Chief, Division of Healthcare Quality Promotion, NCEZID, CDC and Jeneita Bell, MD, MPH, Long-term Care Team Lead, DHQP, NCEZID, CDC—and their support of the development of interoperable data standards for the CDC’s National Healthcare Safety Network (NHSN). \n\nSpecial thanks and acknowledgment to stakeholders who participated in calls and provided feedback. Specifically, we would like to thank Cindy Frakes, Steve Herron, Jamie Gatzke, Kelly Luden, Prasath Govindarajulu from Cerner; Laura Ditz, Nancy Chi, Nichole (Nicki) Fetterman, Michael Furman, Patti Barton, Aga Lee from Point Click Care; Donna Doneski from NASL; and Denise Wassenaar, Doc DeVore, Rob Price from Matrix Care. \n\nThe best standards are those driven by business requirements. A strong set of Healthcare Associated Infection (HAI) surveillance application vendors monitor, evaluate, and test each release of this guide. \n\n\n|-----|-----|-----|-----| \n\n|Primary Editor:|Sarah Gaunt|Lantana Consulting Group|sarah.gaunt@lantanagroup.com| \n|Primary Editor:|Zabrina Gonzaga|Lantana Consulting Group|zabrina.gonzaga@lantanagroup.com| \n|Primary Editor:|Dave deRoode|Lantana Consulting Group|david.deroode@lantanagroup.com| \n|Co-Editor:|Jeneita Bell, MD, MPH|CDC|hpq8@cdc.gov| \n|Co-Editor:|Angella Antilla PhD, MSN|CDC|vtb9@cdc.gov| \n|Co-Editor:|Daniel Pollock, M.D.|CDC|DPollock@cdc.gov| \n|Co-Editor:|Ahmed Tahir|Leidos Consultant to CDC/NHSN|nmn8@cdc.gov| \n|Co-Editor:|Mindy Durrance|Leidos Consultant to CDC/NHSN|mdq1@cdc.gov| \n|Co-Editor:|Sheri Chernetsky Tejedor, MD|CDC|yei9@cdc.gov| \n|Co-Editor:|Sheila Abner|CDC|sha8@cdc.gov| \n|Co-Chair:|Erin Holt MPH|Tennessee Department of Health|erin.holt@tn.gov| \n|Co-Chair:|Laura Rappleye|Altarum|laura.rappleye@altarum.org| \n|Co-Chair:|Craig Newman|Altarum|craig.newman@altarum.org| \n|Co-Chair:|Danny Wise|Allscripts|danny.wise@allscripts.com| \n|Co-Chair:|Joginder Madra|Madra Consulting Inc.|hl7@madraconsulting.com| \n|Co-Chair:|Gaye Dolin M.S.N., R.N. |Intelligent Medical Objects |gdolin@imo-online.com| \n|Co-Chair:|Calvin Beebe|Mayo Clinic|cbeebe@mayo.edu| \n|Co-Chair:|Austin Kreisler|Leidos Consultant to CDC/NHSN|duz1@cdc.gov| \n|Co-Chair:|Andrew Statler|Cerner Corp|andrew.statler@cerner.com| \n|Co-Chair:|Sean McIlvenna| Lantana Consulting Group|sean.mcilvenna@lantanagroup.com| \n|Co-Chair:|Benjamin Flessner|Redox|benjamin@redoxengine.com| \n|Co-Editor:|Beau Bannerman|Lantana Consulting Group|beau.bannerman@lantanagroup.com| \n|Technical Editor:|Diana Wright|Lantana Consulting Group|diana.wright@lantanagroup.com| \n|Technical Editor:|Chris Hannigan|Lantana Consulting Group|chris.hannigan@lantanagroup.com| \n (built Wed, Apr 19, 2023 15:05+0000+00:00)"},{"name":"hl7.fhir.us.hai.r4","version":"2.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/hai","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.hai.r4-2.1.0.tgz","date":"2025-10-29T00:09:02.000Z","description":"This implementation guide (IG) specifies standards for electronic submission of Healthcare Associated Infection (HAI) reports to the National Healthcare Safety Network (NHSN) of the Centers for Disease Control and Prevention (CDC). This IG contains a library of FHIR profiles for electronic submission of HAI reports to the NHSN.\n\nAs reports are modified and new report types are defined, CDC and Health Level Seven (HL7) will develop and publish additional constraints.\n\nThroughout this process, CDC remains the authority on NHSN data collection protocols. When healthcare enterprises choose to participate in NHSN, they must report to CDC occurrences such as specific reportable procedures, even those without complications, and events such as a bloodstream infection, either confirmed by a positive blood culture or supported by a patients clinical symptoms. This specification opens the channel for data submission by all applications compliant with the data coding requirements defined here.\n\nNote that participation in the NHSN requires enrollment and filing of reporting plans, which are not defined by this specification. For an overview of NHSN and full information on NHSN participation requirements, see: [http://www.cdc.gov/nhsn](http://www.cdc.gov/nhsn). Provisions of the Public Health Service Act protect all data reported to NHSN from discovery through the Freedom of Information Act (FOIA). (built Wed, Sep 6, 2023 20:07+0000+00:00)"},{"name":"hl7.fhir.us.hai.r4b","version":"2.1.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/hai","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.hai.r4b-2.1.0.tgz","date":"2025-10-29T00:09:04.000Z","description":"This implementation guide (IG) specifies standards for electronic submission of Healthcare Associated Infection (HAI) reports to the National Healthcare Safety Network (NHSN) of the Centers for Disease Control and Prevention (CDC). This IG contains a library of FHIR profiles for electronic submission of HAI reports to the NHSN.\n\nAs reports are modified and new report types are defined, CDC and Health Level Seven (HL7) will develop and publish additional constraints.\n\nThroughout this process, CDC remains the authority on NHSN data collection protocols. When healthcare enterprises choose to participate in NHSN, they must report to CDC occurrences such as specific reportable procedures, even those without complications, and events such as a bloodstream infection, either confirmed by a positive blood culture or supported by a patients clinical symptoms. This specification opens the channel for data submission by all applications compliant with the data coding requirements defined here.\n\nNote that participation in the NHSN requires enrollment and filing of reporting plans, which are not defined by this specification. For an overview of NHSN and full information on NHSN participation requirements, see: [http://www.cdc.gov/nhsn](http://www.cdc.gov/nhsn). Provisions of the Public Health Service Act protect all data reported to NHSN from discovery through the Freedom of Information Act (FOIA). (built Wed, Sep 6, 2023 20:07+0000+00:00)"},{"name":"hl7.fhir.us.health-care-surveys-reporting.r4","version":"2.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/health-care-surveys-reporting","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.health-care-surveys-reporting.r4-2.0.0-ballot.tgz","date":"2025-10-29T00:09:09.000Z","description":"This implementation guide (IG) provides Health Level Seven (HL7 FHIR) resources to define standards. This guide contains a library of FHIR profiles and is compliant with FHIR Release 4.\n (built Thu, Jul 31, 2025 23:11+0000+00:00)"},{"name":"hl7.fhir.us.health-care-surveys-reporting.r4b","version":"2.0.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/health-care-surveys-reporting","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.health-care-surveys-reporting.r4b-2.0.0-ballot.tgz","date":"2025-10-29T00:09:17.000Z","description":"This implementation guide (IG) provides Health Level Seven (HL7 FHIR) resources to define standards. This guide contains a library of FHIR profiles and is compliant with FHIR Release 4.\n (built Thu, Jul 31, 2025 23:11+0000+00:00)"},{"name":"hl7.fhir.us.home-lab-report.r4","version":"1.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/home-lab-report","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.home-lab-report.r4-1.1.0.tgz","date":"2025-10-29T00:09:26.000Z"},{"name":"hl7.fhir.us.home-lab-report.r4b","version":"1.1.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/home-lab-report","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.home-lab-report.r4b-1.1.0.tgz","date":"2025-10-29T00:09:31.000Z"},{"name":"hl7.fhir.us.hsds.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/hsds","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.hsds.r4-1.0.0.tgz","date":"2025-10-29T00:09:35.000Z","description":"fhir-human-services-directory (built Wed, Oct 4, 2023 18:49+0000+00:00)"},{"name":"hl7.fhir.us.hsds.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/hsds","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.hsds.r4b-1.0.0.tgz","date":"2025-10-29T00:09:39.000Z","description":"fhir-human-services-directory (built Wed, Oct 4, 2023 18:49+0000+00:00)"},{"name":"hl7.fhir.us.icsr-ae-reporting.r4","version":"1.0.1","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/icsr-ae-reporting","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.icsr-ae-reporting.r4-1.0.1.tgz","date":"2025-10-29T00:09:40.000Z","description":"A set of profiles that define the data elements needed to detect conditions and observations arising from transfusions or vaccinations that are candidates for Adverse Events as well as profiles that allow the reporting of Adverse Events (built Tue, Aug 29, 2023 21:36+0000+00:00)"},{"name":"hl7.fhir.us.icsr-ae-reporting.r4b","version":"1.0.1","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/icsr-ae-reporting","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.icsr-ae-reporting.r4b-1.0.1.tgz","date":"2025-10-29T00:09:42.000Z","description":"A set of profiles that define the data elements needed to detect conditions and observations arising from transfusions or vaccinations that are candidates for Adverse Events as well as profiles that allow the reporting of Adverse Events (built Tue, Aug 29, 2023 21:36+0000+00:00)"},{"name":"hl7.fhir.us.identity-matching.r4","version":"2.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/identity-matching","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.identity-matching.r4-2.0.0-ballot.tgz","date":"2025-10-29T00:09:50.000Z"},{"name":"hl7.fhir.us.identity-matching.r4b","version":"2.0.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/identity-matching","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.identity-matching.r4b-2.0.0-ballot.tgz","date":"2025-10-29T00:09:58.000Z"},{"name":"hl7.fhir.us.insurance-card.r4","version":"1.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/insurance-card","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.insurance-card.r4-1.1.0.tgz","date":"2025-10-29T00:10:01.000Z","description":"CARIN Digital Insurance Card (built Tue, Apr 16, 2024 17:35+0000+00:00)"},{"name":"hl7.fhir.us.insurance-card.r4b","version":"1.1.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/insurance-card","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.insurance-card.r4b-1.1.0.tgz","date":"2025-10-29T00:10:03.000Z","description":"CARIN Digital Insurance Card (built Tue, Apr 16, 2024 17:35+0000+00:00)"},{"name":"hl7.fhir.us.mcc.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/mcc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.mcc.r4-1.0.0.tgz","date":"2025-10-29T00:10:09.000Z","description":"### Introduction\nThis HL7® Multiple Chronic Condition (MCC) Care Plan Implementation Guide (IG) defines FHIR R4 profiles, structures, extensions, transactions and value sets needed to represent, query for, and exchange Care Plan information. It defines how to represent coded content used to support the care planning activities focusing on the needs of patients with multiple chronic conditions. This initial version focuses on Chronic Kidney Disease Type 2 diabetes mellitus, common cardiovascular disease (hypertension, ischemic heart disease and heart failure), chronic pain and Long Covid.The profiles defined within this IG were based on data elements of importance identified by the National Institute of Health's (NIH) National Institute of Diabetes and Digestive and Kidney Disease technical expert panels.\n\nA Care Plan is a consensus-driven dynamic plan that represents a patient’s and Care Team Members’ prioritized concerns, goals, planned and actual interventions and the resultant care outcomes. It serves as a blueprint shared by all Care Team Members (including the patient, their caregivers, and providers), to guide the patient’s care. A Care Plan integrates multiple interventions proposed by multiple providers and disciplines for multiple conditions. A Care Plan may represent one or more Care Plans and serves to reconcile and resolve conflicts between the various plans developed for a specific patient by different providers. It supports the following use cases:\n \n1. Query for patient data across providers and compile into a consolidated care plan representation.\n2. Encourage capture of and communication of a patient's health concerns and related goals, interventions, and outcomes.\n3. Gather and aggregate patient data for uses beyond the point of care (e.g. public health, population health, quality measurement, risk adjustment, quality improvement, and research.)\n\nThis FHIR IG addresses the needs of multiple audiences. It provides technical artifacts that assist programmers when implementing standards-based FHIR application program interfaces (APIs) for specific purposes. It provides instructive material that explains how FHIR is used to accomplish specific use cases. It also provides general information that helps business analysts and technology decision-makers understand the use cases and benefits associated with achieving specific data exchange capabilities. A FHIR IG is as much a business planning tool as it is an educational resource and a technical specification.\n\n### How to Read this Guide and Cautions\nThis Guide is divided into several pages which are listed in the navigation bar at the top each page. The contents of each page are listed in a yellow \"Contents\" box at the top right of each page.\n\n### Value Set Library\n\nRather than creating nearly 1000 profiles covering important concepts for chronic care coordination for use within the MCC FHIR Care Plan profile, we have created 21 foundation profiles which conform to US Core Profiles (where available) adding constraints or extensions pertinent to their representation within a dynamic FHIR care plan and then creating libraries of value sets pertinent to the base profiles for representing chronic conditions, and their related interventions and goals and outcomes. \nThis project has built and houses its value sets in the National Library of Medicine's (NLM) Value Set Authority Center (VSAC). The value sets are not directly bound within the foundation profiles, but value set library pages are provided with links to the value sets in VSAC and descriptions of where within the profile each value set may be used. Because the value sets are housed in VSAC, it is necessary for implementation sites to obtain a free (for the US) UMLS license. In addition, HL7 FHIR Policies requiring everything to be open source in all realms, may present some implementation validation issues when interfacing with a value set housed in VSAC. This IG will provide guidance for this issue.\n\n### History of the Care Plan and Electronic Care Plans\n\nThe concept of a care plan began as a teaching tool for nursing students to research and document the medical conditions their patients had and identify the associated nursing care and family support needed. This was documented in a structured paper format that fostered the nursing process. The nursing process is the identification of health concerns and related goals, and the interventions needed to meet those goals and then evaluating the meeting of those goals – the outcomes. Over the years, the care plan evolved from a student teaching tool to something required for most patients in some format by various regulating or certifying bodies, and further, from a nursing care based plan, to an interdisciplinary patient focused tool.\n\nMost major vendors have electronic Care Plan modules, but the degree to which the modules are implemented and actively used is unknown. Few, if any, are exchange standards ready or mapped to exchange standards. The first HL7 standard representing Care Plan was the C-CDA Care Plan document designed to represent an instance of an EHR Care Plan similar to the Continuity of Care (CCD) CDA. Many of the learnings and designs for the FHIR Care Plan Resource and this IG were derived from the C-CDA Care Plan. There is also an IHE [Dynamic Care Planning (DCP)](https://wiki.ihe.net/index.php/Dynamic_Care_Planning_(DCP)) that provides the structures and transactions for care planning, creating, updating and sharing Care Plans that meet the needs of many, such as providers, patients and payers.. The Office of the National Coordinator (ONC) has put into regulation requirements around goals and health concerns which can currently be met by free text. The Dynamic Care Planning (DCP) Profile provides leveraged FHIR Resources to provide the structures and transactions for care planning and sharing Care Plans that meet the needs of many, such as providers, patients and payers. The DCP profile leverages the FHIR Care Plan resource, but does not specify, describe or define the use of it for representing specific conditions or multiple conditions. We are unaware of any real world implementations of it at this time.\n\nWe believe that this IG will be the first fully defined HL7 FHIR IG leveraging the FHIR Care Plan resources as its backbone structure for representing a dynamic care plan and testing its ability to bring together aggregated patient care plan data including patient outcomes.\n\n### Project Overview\n\nMore than 25 percent of Americans have MCC, accounting for more than 65 percent of U.S. healthcare spending. These individuals have complex health needs handled by diverse providers, across multiple settings of care. As a result, their care is often fragmented, poorly coordinated, and inefficient. Therefore, data aggregation is particularly important and challenging for people with MCC. These challenges will increasingly strain the U.S. health system, with the aging of the U.S. population. Projections suggest numbers of adults aged 65 and older will more than double and numbers of those aged 85 and older will triple by 2050.\n \nCare plans are a prominent part of multifaceted, care coordination interventions that reduce mortality and hospitalizations and improve disease management and satisfaction. In addition, proactive care planning promotes person-centeredness, improves outcomes, and reduces the cost of care. By design, care plans take a patient-centered approach, both by making comprehensive health data available across providers and settings and through the incorporation of data elements that have not traditionally been included in health IT systems (e.g., social determinants of health SDOH, patient health and life goals, patient preferences). While Care Plans have been developed, they remain paper-based in many U.S. healthcare settings and are not standardized and interoperable across care settings when electronic. While care plans focused on a single disease or condition are unlikely to be tenable for patients with MCC or their providers, existing care plans infrequently address individuals with MCC. The development of care plans based on structured data has been proposed as a method for enabling electronic systems to pull together and share data elements automatically and dynamically. Such aggregated data would not only provide actionable information to identify and achieve health and wellness goals for individuals with MCC, but also would reduce missingness and improve quality of point-of-care data for use in pragmatic research.\n \nThe Fast Healthcare Interoperability Resources (FHIR) specification is an open-source standard for exchanging healthcare information electronically based on emerging industry approaches. The FHIR workflow specification includes a CarePlan request resource that may facilitate transfer of data for an e-care plan across healthcare settings. SMART (https://smarthealthit.org/) and SMART on FHIR standards include open specifications to integrate applications with health IT systems and may enable the development of an e-care plan application that can integrate with a variety of electronic health record (EHR) systems.\n\nInitiated by the National Institute of Diabetes and Digestive and Kidney Diseases (NIDDK), the multiple chronic conditions (MCC) electronic care (eCare) Plan Project aims to develop, test, and pilot an interoperable eCare plan that will facilitate aggregation and sharing of critical patient-centered data across home, community, clinic, and research-based settings for persons with MCC, including chronic kidney disease (CKD), type 2 diabetes mellitus (T2D), cardiovascular disease (CVD), pain with opioid use disorder (OUD), and long COVID. \n\nThe HL7-based activities of the MCC eCare Plan Project include:\n \n - Identified use cases to support the documentation and exchange of MCC eCare plan data within EHRs and related systems.\n - Identified, developed, and prioritized the necessary MCC data elements and clinical terminology standards and FHIR® mappings that will enable the standardized transfer of data across health settings.\n - Develop, test, and ballot an HL7® Fast Health Interoperability Resources (FHIR®) Implementation Guide based on the defined use cases and MCC data elements.\n \nNon-HL7 related activities of the MCC eCare Plan project will be facilitated through the [AHRQ eCare Plan Project Confluence](https://ecareplan.ahrq.gov/collaborate):\n - The project includes the develoment and testing of an open-source clinician and patient facing SMART-on-FHIR eCare plan application for managing persons with MCC.\n\n#### Project Timelines\n - January 2024: A For comment ballot to gather community input prior to the formal STU Ballot\n - September 2024: Formal STU Ballot\n - May 2025 Formal HL7 Publication\n\n\n### Guidance\nThe guidance section provides general implementation guidance and best practices. It describes the relation to and reuse of the US Core Implementation Guide profiles and reuse of its conformance requirements and expectations for the servers and client applications. Vocabulary use and value set binding heuristics are described.\n\n#### Relationship to US Core\n\nThis Implementation Guide reuses US Core profiles either through direct use or by constraining select profiles for representation within a FHIR Care Plan profile. Where US Core does not have a profile or function that is needed for the use cases or data elements, the IG constrains or directly reuses other resources, or profiles defined in other FHIR IGs. \nThis guide will reuse the US Core Care Plan. However, the required US Core CarePlan.text and the required Care.Plan.category:AssessPlan may be limiting factors for this context of use: aggregation of multiple chronic condition care plans and the ability to query for structured data within a structured Care Plan. As such, we recommend adding additional Care Plan categories if deemed more informational to reflect multiple chronic condition care coordination and plans and to hard code “Multiple Chronic Condition Care Coordination Plan” at CarePlan.text\n\n\n##### General US Core IG Conformance\n\nThis guide will adhere to or build on US conformance requirements, most of its [General Guidance](https://www.hl7.org/fhir/us/core/general-guidance.html), and its [Capability Statements](https://www.hl7.org/fhir/us/core/capstatements.html) where applicable. \n\n##### Provenance\n\nThis IG recommends implementers adhere to guidelines and definitions provided in US Core’s [Basic Provenance Guidance](https://www.hl7.org/fhir/us/core/basic-provenance.html). \n\n##### Must Support\n\nThis IG will adhere to the US Core [Must Support](https://www.hl7.org/fhir/us/core/general-guidance.html#must-support) concept and rules.\n\n### Acknowledgements\nThis Implementation Guide was made possible through the visionary leadership of the [National Institute of Diabetes and Digestive and Kidney Diseases (NIDDK) ](https://www.niddk.nih.gov/)and the [Agency for Healthcare Research and Quality (AHRQ) ](https://www.ahrq.gov/)with funding from the [Office of the Assistant Secretary for Planning and Evaluation (ASPE)](https://aspe.hhs.gov/collaborations-committees-advisory-groups/os-pcortf/explore-portfolio). The joint NIDDK-AHRQ project team can be found [here](https://cmext.ahrq.gov/confluence/display/EC/Project+Team). We would also like to thank the many clinicians, patients, caregivers, researchers, advocates, and subject matter experts who served on our [Technical Expert Panels](https://cmext.ahrq.gov/confluence/display/EC/Technical+Expert+Panels) and [Contract Monitoring Board ](https://cmext.ahrq.gov/confluence/display/EC/Contract+Monitoring+Board) for their time, insight, and support. \n\nThis Implementation Guide was created under the supervision and review of the [HL7 Patient Care Work Group](https://www.hl7.org/Special/committees/patientcare/index.cfm). This is the HL7 project page for the [Multiple Chronic Conditions e-Care Project.](https://confluence.hl7.org/display/PC/Multiple+Chronic+Conditions+%28MCC%29+eCare+Plan)\n\n (built Tue, Aug 13, 2024 21:18+0000+00:00)"},{"name":"hl7.fhir.us.mcc.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/mcc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.mcc.r4b-1.0.0.tgz","date":"2025-10-29T00:10:14.000Z","description":"### Introduction\nThis HL7® Multiple Chronic Condition (MCC) Care Plan Implementation Guide (IG) defines FHIR R4 profiles, structures, extensions, transactions and value sets needed to represent, query for, and exchange Care Plan information. It defines how to represent coded content used to support the care planning activities focusing on the needs of patients with multiple chronic conditions. This initial version focuses on Chronic Kidney Disease Type 2 diabetes mellitus, common cardiovascular disease (hypertension, ischemic heart disease and heart failure), chronic pain and Long Covid.The profiles defined within this IG were based on data elements of importance identified by the National Institute of Health's (NIH) National Institute of Diabetes and Digestive and Kidney Disease technical expert panels.\n\nA Care Plan is a consensus-driven dynamic plan that represents a patient’s and Care Team Members’ prioritized concerns, goals, planned and actual interventions and the resultant care outcomes. It serves as a blueprint shared by all Care Team Members (including the patient, their caregivers, and providers), to guide the patient’s care. A Care Plan integrates multiple interventions proposed by multiple providers and disciplines for multiple conditions. A Care Plan may represent one or more Care Plans and serves to reconcile and resolve conflicts between the various plans developed for a specific patient by different providers. It supports the following use cases:\n \n1. Query for patient data across providers and compile into a consolidated care plan representation.\n2. Encourage capture of and communication of a patient's health concerns and related goals, interventions, and outcomes.\n3. Gather and aggregate patient data for uses beyond the point of care (e.g. public health, population health, quality measurement, risk adjustment, quality improvement, and research.)\n\nThis FHIR IG addresses the needs of multiple audiences. It provides technical artifacts that assist programmers when implementing standards-based FHIR application program interfaces (APIs) for specific purposes. It provides instructive material that explains how FHIR is used to accomplish specific use cases. It also provides general information that helps business analysts and technology decision-makers understand the use cases and benefits associated with achieving specific data exchange capabilities. A FHIR IG is as much a business planning tool as it is an educational resource and a technical specification.\n\n### How to Read this Guide and Cautions\nThis Guide is divided into several pages which are listed in the navigation bar at the top each page. The contents of each page are listed in a yellow \"Contents\" box at the top right of each page.\n\n### Value Set Library\n\nRather than creating nearly 1000 profiles covering important concepts for chronic care coordination for use within the MCC FHIR Care Plan profile, we have created 21 foundation profiles which conform to US Core Profiles (where available) adding constraints or extensions pertinent to their representation within a dynamic FHIR care plan and then creating libraries of value sets pertinent to the base profiles for representing chronic conditions, and their related interventions and goals and outcomes. \nThis project has built and houses its value sets in the National Library of Medicine's (NLM) Value Set Authority Center (VSAC). The value sets are not directly bound within the foundation profiles, but value set library pages are provided with links to the value sets in VSAC and descriptions of where within the profile each value set may be used. Because the value sets are housed in VSAC, it is necessary for implementation sites to obtain a free (for the US) UMLS license. In addition, HL7 FHIR Policies requiring everything to be open source in all realms, may present some implementation validation issues when interfacing with a value set housed in VSAC. This IG will provide guidance for this issue.\n\n### History of the Care Plan and Electronic Care Plans\n\nThe concept of a care plan began as a teaching tool for nursing students to research and document the medical conditions their patients had and identify the associated nursing care and family support needed. This was documented in a structured paper format that fostered the nursing process. The nursing process is the identification of health concerns and related goals, and the interventions needed to meet those goals and then evaluating the meeting of those goals – the outcomes. Over the years, the care plan evolved from a student teaching tool to something required for most patients in some format by various regulating or certifying bodies, and further, from a nursing care based plan, to an interdisciplinary patient focused tool.\n\nMost major vendors have electronic Care Plan modules, but the degree to which the modules are implemented and actively used is unknown. Few, if any, are exchange standards ready or mapped to exchange standards. The first HL7 standard representing Care Plan was the C-CDA Care Plan document designed to represent an instance of an EHR Care Plan similar to the Continuity of Care (CCD) CDA. Many of the learnings and designs for the FHIR Care Plan Resource and this IG were derived from the C-CDA Care Plan. There is also an IHE [Dynamic Care Planning (DCP)](https://wiki.ihe.net/index.php/Dynamic_Care_Planning_(DCP)) that provides the structures and transactions for care planning, creating, updating and sharing Care Plans that meet the needs of many, such as providers, patients and payers.. The Office of the National Coordinator (ONC) has put into regulation requirements around goals and health concerns which can currently be met by free text. The Dynamic Care Planning (DCP) Profile provides leveraged FHIR Resources to provide the structures and transactions for care planning and sharing Care Plans that meet the needs of many, such as providers, patients and payers. The DCP profile leverages the FHIR Care Plan resource, but does not specify, describe or define the use of it for representing specific conditions or multiple conditions. We are unaware of any real world implementations of it at this time.\n\nWe believe that this IG will be the first fully defined HL7 FHIR IG leveraging the FHIR Care Plan resources as its backbone structure for representing a dynamic care plan and testing its ability to bring together aggregated patient care plan data including patient outcomes.\n\n### Project Overview\n\nMore than 25 percent of Americans have MCC, accounting for more than 65 percent of U.S. healthcare spending. These individuals have complex health needs handled by diverse providers, across multiple settings of care. As a result, their care is often fragmented, poorly coordinated, and inefficient. Therefore, data aggregation is particularly important and challenging for people with MCC. These challenges will increasingly strain the U.S. health system, with the aging of the U.S. population. Projections suggest numbers of adults aged 65 and older will more than double and numbers of those aged 85 and older will triple by 2050.\n \nCare plans are a prominent part of multifaceted, care coordination interventions that reduce mortality and hospitalizations and improve disease management and satisfaction. In addition, proactive care planning promotes person-centeredness, improves outcomes, and reduces the cost of care. By design, care plans take a patient-centered approach, both by making comprehensive health data available across providers and settings and through the incorporation of data elements that have not traditionally been included in health IT systems (e.g., social determinants of health SDOH, patient health and life goals, patient preferences). While Care Plans have been developed, they remain paper-based in many U.S. healthcare settings and are not standardized and interoperable across care settings when electronic. While care plans focused on a single disease or condition are unlikely to be tenable for patients with MCC or their providers, existing care plans infrequently address individuals with MCC. The development of care plans based on structured data has been proposed as a method for enabling electronic systems to pull together and share data elements automatically and dynamically. Such aggregated data would not only provide actionable information to identify and achieve health and wellness goals for individuals with MCC, but also would reduce missingness and improve quality of point-of-care data for use in pragmatic research.\n \nThe Fast Healthcare Interoperability Resources (FHIR) specification is an open-source standard for exchanging healthcare information electronically based on emerging industry approaches. The FHIR workflow specification includes a CarePlan request resource that may facilitate transfer of data for an e-care plan across healthcare settings. SMART (https://smarthealthit.org/) and SMART on FHIR standards include open specifications to integrate applications with health IT systems and may enable the development of an e-care plan application that can integrate with a variety of electronic health record (EHR) systems.\n\nInitiated by the National Institute of Diabetes and Digestive and Kidney Diseases (NIDDK), the multiple chronic conditions (MCC) electronic care (eCare) Plan Project aims to develop, test, and pilot an interoperable eCare plan that will facilitate aggregation and sharing of critical patient-centered data across home, community, clinic, and research-based settings for persons with MCC, including chronic kidney disease (CKD), type 2 diabetes mellitus (T2D), cardiovascular disease (CVD), pain with opioid use disorder (OUD), and long COVID. \n\nThe HL7-based activities of the MCC eCare Plan Project include:\n \n - Identified use cases to support the documentation and exchange of MCC eCare plan data within EHRs and related systems.\n - Identified, developed, and prioritized the necessary MCC data elements and clinical terminology standards and FHIR® mappings that will enable the standardized transfer of data across health settings.\n - Develop, test, and ballot an HL7® Fast Health Interoperability Resources (FHIR®) Implementation Guide based on the defined use cases and MCC data elements.\n \nNon-HL7 related activities of the MCC eCare Plan project will be facilitated through the [AHRQ eCare Plan Project Confluence](https://ecareplan.ahrq.gov/collaborate):\n - The project includes the develoment and testing of an open-source clinician and patient facing SMART-on-FHIR eCare plan application for managing persons with MCC.\n\n#### Project Timelines\n - January 2024: A For comment ballot to gather community input prior to the formal STU Ballot\n - September 2024: Formal STU Ballot\n - May 2025 Formal HL7 Publication\n\n\n### Guidance\nThe guidance section provides general implementation guidance and best practices. It describes the relation to and reuse of the US Core Implementation Guide profiles and reuse of its conformance requirements and expectations for the servers and client applications. Vocabulary use and value set binding heuristics are described.\n\n#### Relationship to US Core\n\nThis Implementation Guide reuses US Core profiles either through direct use or by constraining select profiles for representation within a FHIR Care Plan profile. Where US Core does not have a profile or function that is needed for the use cases or data elements, the IG constrains or directly reuses other resources, or profiles defined in other FHIR IGs. \nThis guide will reuse the US Core Care Plan. However, the required US Core CarePlan.text and the required Care.Plan.category:AssessPlan may be limiting factors for this context of use: aggregation of multiple chronic condition care plans and the ability to query for structured data within a structured Care Plan. As such, we recommend adding additional Care Plan categories if deemed more informational to reflect multiple chronic condition care coordination and plans and to hard code “Multiple Chronic Condition Care Coordination Plan” at CarePlan.text\n\n\n##### General US Core IG Conformance\n\nThis guide will adhere to or build on US conformance requirements, most of its [General Guidance](https://www.hl7.org/fhir/us/core/general-guidance.html), and its [Capability Statements](https://www.hl7.org/fhir/us/core/capstatements.html) where applicable. \n\n##### Provenance\n\nThis IG recommends implementers adhere to guidelines and definitions provided in US Core’s [Basic Provenance Guidance](https://www.hl7.org/fhir/us/core/basic-provenance.html). \n\n##### Must Support\n\nThis IG will adhere to the US Core [Must Support](https://www.hl7.org/fhir/us/core/general-guidance.html#must-support) concept and rules.\n\n### Acknowledgements\nThis Implementation Guide was made possible through the visionary leadership of the [National Institute of Diabetes and Digestive and Kidney Diseases (NIDDK) ](https://www.niddk.nih.gov/)and the [Agency for Healthcare Research and Quality (AHRQ) ](https://www.ahrq.gov/)with funding from the [Office of the Assistant Secretary for Planning and Evaluation (ASPE)](https://aspe.hhs.gov/collaborations-committees-advisory-groups/os-pcortf/explore-portfolio). The joint NIDDK-AHRQ project team can be found [here](https://cmext.ahrq.gov/confluence/display/EC/Project+Team). We would also like to thank the many clinicians, patients, caregivers, researchers, advocates, and subject matter experts who served on our [Technical Expert Panels](https://cmext.ahrq.gov/confluence/display/EC/Technical+Expert+Panels) and [Contract Monitoring Board ](https://cmext.ahrq.gov/confluence/display/EC/Contract+Monitoring+Board) for their time, insight, and support. \n\nThis Implementation Guide was created under the supervision and review of the [HL7 Patient Care Work Group](https://www.hl7.org/Special/committees/patientcare/index.cfm). This is the HL7 project page for the [Multiple Chronic Conditions e-Care Project.](https://confluence.hl7.org/display/PC/Multiple+Chronic+Conditions+%28MCC%29+eCare+Plan)\n\n (built Tue, Aug 13, 2024 21:18+0000+00:00)"},{"name":"hl7.fhir.us.mcode.r4","version":"4.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/mcode","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.mcode.r4-4.0.0.tgz","date":"2025-10-29T00:10:26.000Z","description":"mCODE™ (short for Minimal Common Oncology Data Elements) is an initiative intended to assemble a core set of structured data elements for oncology electronic health records. (built Sun, Feb 16, 2025 20:00+0000+00:00)"},{"name":"hl7.fhir.us.mcode.r4b","version":"4.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/mcode","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.mcode.r4b-4.0.0.tgz","date":"2025-10-29T00:10:44.000Z","description":"mCODE™ (short for Minimal Common Oncology Data Elements) is an initiative intended to assemble a core set of structured data elements for oncology electronic health records. (built Sun, Feb 16, 2025 20:00+0000+00:00)"},{"name":"hl7.fhir.us.mdi.r4","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/mdi","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.mdi.r4-2.0.0.tgz","date":"2025-10-29T00:10:55.000Z"},{"name":"hl7.fhir.us.mdi.r4b","version":"2.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/mdi","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.mdi.r4b-2.0.0.tgz","date":"2025-10-29T00:11:10.000Z"},{"name":"hl7.fhir.us.medication-rems.r4","version":"2.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/medication-rems","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.medication-rems.r4-2.0.0-ballot.tgz","date":"2025-10-29T00:11:19.000Z","description":"FHIR implementation options and guidance for medication REMS participants (built Thu, Jul 31, 2025 17:49+0000+00:00)"},{"name":"hl7.fhir.us.medication-rems.r4b","version":"2.0.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/medication-rems","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.medication-rems.r4b-2.0.0-ballot.tgz","date":"2025-10-29T00:11:25.000Z","description":"FHIR implementation options and guidance for medication REMS participants (built Thu, Jul 31, 2025 17:49+0000+00:00)"},{"name":"hl7.fhir.us.medmorph.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/medmorph","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.medmorph.r4-1.0.0.tgz","date":"2025-10-29T00:11:30.000Z","description":"MedMorph describes a framework to enable submission of data from healthcare organizations to public health and research organizations. (built Thu, Jun 8, 2023 19:04+0000+00:00)"},{"name":"hl7.fhir.us.medmorph.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/medmorph","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.medmorph.r4b-1.0.0.tgz","date":"2025-10-29T00:11:32.000Z","description":"MedMorph describes a framework to enable submission of data from healthcare organizations to public health and research organizations. (built Thu, Jun 8, 2023 19:04+0000+00:00)"},{"name":"hl7.fhir.us.meds","version":"2.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/meds","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.meds-2.1.0.tgz","date":"2025-10-29T00:11:34.000Z"},{"name":"hl7.fhir.us.mihr.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/mihr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.mihr.r4-1.0.0.tgz","date":"2025-10-29T00:11:37.000Z","description":"### Scope\nThe Longitudinal Maternal & Child Health Information for Research FHIR R4 implementation guide (IG) defines a framework to enable maternal health researchers to aggregate, calculate, and analyze clinical information of research populations to explore the root causes for maternal and child morbidity and mortality. It uses Clinical Quality Language (CQL) expressions to assist researchers in capturing clinical data based on population study cohort criteria. This IG focuses on information relevant to longitudinal maternal care, which includes antepartum (including pre-pregnancy), intrapartum, and postpartum care of a pregnant woman. It includes how to link maternal longitudinal record with associated child/children records. \n\nThis US Realm IG supports the use of US Core profiles where possible, as well as base FHIR and Vital Records Common Profiles FHIR IG data model for the structural linkage of mother and child clinical records. \n\n\n### Background\nThe rates of maternal mortality have been rising in the United States since 1987. Clinical data relevant to understanding this trend are not standardized, and data exchange is not interoperable across many relevant settings. Maternal health and associated child health are inextricably linked – what happens during gestation, delivery, and after informs health outcomes of both mother and child – but relevant data is often held in separate, unconnected records. These issues impede research on maternal morbidity and longitudinal maternal care and associated impacts to infant health. Research on root causes of maternal mortality, pediatric developmental problems, and effective treatments requires exchange of information stored in disparate sources, such as electronic health record (EHR) systems, registries, and public health agencies (PHAs).\n\nThe types of information needed to research maternal health and morbidity include social determinants of health (SDOH) and associated clinical data such as antepartum, intrapartum, and postpartum care of a pregnant woman; pregnancy-related conditions and outcomes; maternal co-morbidities; child health data; and procedures. The goal of this FHIR IG is to define a model to support data exchange for predictive analysis, risk assessment, and retrospective maternal health research across the spectrum and duration of care. \n\nFuture users may include health departments using EHR data to inform public health interventions (e.g., case identification for reportable conditions, identifying persons lost to care, etc.) and maternal and child health researchers. The standards development effort will also examine options for data exchange mechanisms, including point-in-time query (data pull) and research population creation, i.e., patient enrollment in a study.\n\n### Maternal Research Use Cases\n\nThis IG will eventually support mapping maternal data across health records from specialty care and linking mother and child data harmonized across a broad set of use cases. This will support researchers in identifying root causes of maternal mortality and pediatric developmental problems, including SDOH such as limited income, poor nutrition, lack of medical coverage, etc. The goal of the project is to create a method to standardize data capture for comparative analysis over time to improve health outcomes and define a framework for studying additional research populations in the future.\n\nInitial use cases of this IG focus on hypertensive disorders of pregnancy pre, ante, and postpartum and pregnancy and subsequent death within a specific timeframe. The intent is to specify the consistent capture of clinical data of interest to maternal health researchers and outline implementing FHIR resources for that capture. Currently, the IG defines two initial, separate research use case populations: \n\n* Pregnancy and subsequent death within a specific time frame: This cohort includes women who died within a year (365 days) of a pregnancy regardless of cause of death or pregnancy outcome.\n* Hypertensive Disorders of pregnancy: This use case focuses on women with a diagnosis of hypertensive disorders of pregnancy.\n\nIn both instances, the IG will establish linkages via the US Core Related Person profile to collect associated child health data that may inform maternal health research outcomes. \n\nIn the future, the IG will expand this framework to a range of use cases including:\n* Risks for children related to maternal exposure to medications taken during pregnancy\n* Potential adverse maternal obstetric history impacts on child outcomes\n* Access to relevant sensitive health information\n* Retrospective population-based analysis of inherited disorders\n* The impacts of [work habits, work environment, and work-associated health insurance](http://hl7.org/fhir/us/odh/) impacts to pregnancy and maternal health\n\nThis guide fundamentally relies on creating structural relationships between:\n* Maternal and child records to effectively diagnose and treat otherwise fatal child outcomes\n* Maternal and child birth records and/or maternal and child death records\n* Maternal and child records in multiple disparate systems\n\n### Audience \nThe audience for this IG includes EHR vendors, developers of software tooling researchers, and associated information management systems. Researchers, business analysts, and policy managers can also benefit from a basic understanding of the use of this guide to support measure calculation for research purposes.\n\n### Authors & Project Team\nThis table lists the authors, subject matter experts, and the affiliations which contributed to this standard. \n\n\n\n\n \n \n \n \n \n\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\n
Name & AffiliationRoleContact
Lantana Consulting Group
Courtney Panaia-Rodi Project Executivecourtney.panaia-rodi@lantanagroup.com
Wendy WiseProject Managerwendy.wise@lantanagroup.com
Lani JohnsonAssociate Project Managerlani.johnson@lantanagroup.com
Rick GeimerFHIR Subject Matter Expertrick.geimer@lantanagroup.com
Zabrina GonzagaTerminology Subject Matter Expertzabrina.gonzaga@lantanagroup.com
Sarah GauntSenior FHIR/CDA Analystsarah.gaunt@lantanagroup.com
Dave deRoodeFHIR/CDA Analystdavid.deroode@lantanagroup.com
Ming DunajickFHIR/CDA Analystming.dunajick@lantanagroup.com
Ruby NashFHIR Analystruby.nash@lantanagroup.com
Office of the Assistant Secretary for Planning and Evaluation (ASPE)
Violanda Grigorescu, MD, MSPHSenior Health Scientist
Division of Healthcare Quality and Outcomes, Office of Health Policy		violanda.grigorescu@hhs.gov
Centers for Disease Control and Prevention (CDC)
Margaret Lampe, RN, MPHNurse Epidemiologist & Project Officer
Perinatal HIV Prevention Program		mol0@cdc.gov
Lisa Romero, DrPHHealth Scientist
Division of Adolescent School Health		eon1@cdc.gov
National Institutes of Health (NIH)
Eunice Kennedy Shriver National Institute of Child Health and Human Development (NICHD)
National Information Center on Health Services Research and Health Care Technology (NICHSR)
Alison CernichNICHD Deputy Directoralison.cernich@nih.hhs.gov
John (Jack) Moye, Jr., MDActing Director - National Children's Study
NICHD Medical Officer - Maternal & Pediatric Infectious Disease Branch		moyej@exchange.nih.gov
Nahida Chakhtoura, MD, MsGHNICHD Medical Officer
Maternal and Pediatric Infectious Disease Branch		nahida.chakhtoura@nih.gov
Juanita Chinn, PhDNICHD Program Director
Population Dynamics Branch		juanita.chinn@nih.gov
Valerie CottonNICHD Deputy Director
Office of Data Science and Sharing		valerie.cotton@nih.gov
Liz Amos, MLISSpecial Assistant to the Chief Health Data Standards Officer
National Library of Medicine		liz.amos@nih.gov
Office of the National Coordinator for Health IT (ONC)
Carmen SmileyIT Specialist (Systems Analysis)carmen.smiley@hhs.gov
Rachel AbbeyPublic Health Analyst & Program Officerrachel.abbey@hhs.gov
Stephanie GarciaSenior Program Analyststephanie.garcia@hhs.gov
Brittney Boakye, MPHProgram Assistant
Scientific Advancement Branch		brittney.boakye@hhs.gov
Alan TaylorMedical Informatics Officer, Standards and Terminologyalbert.taylor@hhs.gov
\n\n### Acknowledgements\nThis guide was developed and produced through the efforts of Health Level Seven (HL7) and created using the Trifolia-on-FHIR tool, provided by Lantana Consulting Group. The HL7 Project Insight reference number for this project is 1736.\nThe editors appreciate the support and sponsorship of the HL7 Public Health Workgroup, and all volunteers and staff associated with the creation of this document. This guide would not have been possible without the support of the following groups.\nHealth Level Seven, HL7, CDA, CCD, FHIR and the [FLAME DESIGN] are registered trademarks of Health Level Seven International, registered in the US Trademark Office.\n\nThis IG includes content from SNOMED CT, which is copyright © 2002+ International Health Terminology Standards Development Organisation (IHTSDO), and distributed by agreement between IHTSDO and HL7. Implementer use of SNOMED CT is not covered by this agreement.\n\nThis material contains content from [LOINC](http://loinc.org). LOINC is copyright © 1995-2021, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license at https://loinc.org/kb/license/. LOINC® is a registered United States trademark of Regenstrief Institute, Inc. (built Wed, Mar 29, 2023 19:33+0000+00:00)"},{"name":"hl7.fhir.us.mihr.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/mihr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.mihr.r4b-1.0.0.tgz","date":"2025-10-29T00:11:38.000Z","description":"### Scope\nThe Longitudinal Maternal & Child Health Information for Research FHIR R4 implementation guide (IG) defines a framework to enable maternal health researchers to aggregate, calculate, and analyze clinical information of research populations to explore the root causes for maternal and child morbidity and mortality. It uses Clinical Quality Language (CQL) expressions to assist researchers in capturing clinical data based on population study cohort criteria. This IG focuses on information relevant to longitudinal maternal care, which includes antepartum (including pre-pregnancy), intrapartum, and postpartum care of a pregnant woman. It includes how to link maternal longitudinal record with associated child/children records. \n\nThis US Realm IG supports the use of US Core profiles where possible, as well as base FHIR and Vital Records Common Profiles FHIR IG data model for the structural linkage of mother and child clinical records. \n\n\n### Background\nThe rates of maternal mortality have been rising in the United States since 1987. Clinical data relevant to understanding this trend are not standardized, and data exchange is not interoperable across many relevant settings. Maternal health and associated child health are inextricably linked – what happens during gestation, delivery, and after informs health outcomes of both mother and child – but relevant data is often held in separate, unconnected records. These issues impede research on maternal morbidity and longitudinal maternal care and associated impacts to infant health. Research on root causes of maternal mortality, pediatric developmental problems, and effective treatments requires exchange of information stored in disparate sources, such as electronic health record (EHR) systems, registries, and public health agencies (PHAs).\n\nThe types of information needed to research maternal health and morbidity include social determinants of health (SDOH) and associated clinical data such as antepartum, intrapartum, and postpartum care of a pregnant woman; pregnancy-related conditions and outcomes; maternal co-morbidities; child health data; and procedures. The goal of this FHIR IG is to define a model to support data exchange for predictive analysis, risk assessment, and retrospective maternal health research across the spectrum and duration of care. \n\nFuture users may include health departments using EHR data to inform public health interventions (e.g., case identification for reportable conditions, identifying persons lost to care, etc.) and maternal and child health researchers. The standards development effort will also examine options for data exchange mechanisms, including point-in-time query (data pull) and research population creation, i.e., patient enrollment in a study.\n\n### Maternal Research Use Cases\n\nThis IG will eventually support mapping maternal data across health records from specialty care and linking mother and child data harmonized across a broad set of use cases. This will support researchers in identifying root causes of maternal mortality and pediatric developmental problems, including SDOH such as limited income, poor nutrition, lack of medical coverage, etc. The goal of the project is to create a method to standardize data capture for comparative analysis over time to improve health outcomes and define a framework for studying additional research populations in the future.\n\nInitial use cases of this IG focus on hypertensive disorders of pregnancy pre, ante, and postpartum and pregnancy and subsequent death within a specific timeframe. The intent is to specify the consistent capture of clinical data of interest to maternal health researchers and outline implementing FHIR resources for that capture. Currently, the IG defines two initial, separate research use case populations: \n\n* Pregnancy and subsequent death within a specific time frame: This cohort includes women who died within a year (365 days) of a pregnancy regardless of cause of death or pregnancy outcome.\n* Hypertensive Disorders of pregnancy: This use case focuses on women with a diagnosis of hypertensive disorders of pregnancy.\n\nIn both instances, the IG will establish linkages via the US Core Related Person profile to collect associated child health data that may inform maternal health research outcomes. \n\nIn the future, the IG will expand this framework to a range of use cases including:\n* Risks for children related to maternal exposure to medications taken during pregnancy\n* Potential adverse maternal obstetric history impacts on child outcomes\n* Access to relevant sensitive health information\n* Retrospective population-based analysis of inherited disorders\n* The impacts of [work habits, work environment, and work-associated health insurance](http://hl7.org/fhir/us/odh/) impacts to pregnancy and maternal health\n\nThis guide fundamentally relies on creating structural relationships between:\n* Maternal and child records to effectively diagnose and treat otherwise fatal child outcomes\n* Maternal and child birth records and/or maternal and child death records\n* Maternal and child records in multiple disparate systems\n\n### Audience \nThe audience for this IG includes EHR vendors, developers of software tooling researchers, and associated information management systems. Researchers, business analysts, and policy managers can also benefit from a basic understanding of the use of this guide to support measure calculation for research purposes.\n\n### Authors & Project Team\nThis table lists the authors, subject matter experts, and the affiliations which contributed to this standard. \n\n\n\n\n \n \n \n \n \n\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\n
Name & AffiliationRoleContact
Lantana Consulting Group
Courtney Panaia-Rodi Project Executivecourtney.panaia-rodi@lantanagroup.com
Wendy WiseProject Managerwendy.wise@lantanagroup.com
Lani JohnsonAssociate Project Managerlani.johnson@lantanagroup.com
Rick GeimerFHIR Subject Matter Expertrick.geimer@lantanagroup.com
Zabrina GonzagaTerminology Subject Matter Expertzabrina.gonzaga@lantanagroup.com
Sarah GauntSenior FHIR/CDA Analystsarah.gaunt@lantanagroup.com
Dave deRoodeFHIR/CDA Analystdavid.deroode@lantanagroup.com
Ming DunajickFHIR/CDA Analystming.dunajick@lantanagroup.com
Ruby NashFHIR Analystruby.nash@lantanagroup.com
Office of the Assistant Secretary for Planning and Evaluation (ASPE)
Violanda Grigorescu, MD, MSPHSenior Health Scientist
Division of Healthcare Quality and Outcomes, Office of Health Policy		violanda.grigorescu@hhs.gov
Centers for Disease Control and Prevention (CDC)
Margaret Lampe, RN, MPHNurse Epidemiologist & Project Officer
Perinatal HIV Prevention Program		mol0@cdc.gov
Lisa Romero, DrPHHealth Scientist
Division of Adolescent School Health		eon1@cdc.gov
National Institutes of Health (NIH)
Eunice Kennedy Shriver National Institute of Child Health and Human Development (NICHD)
National Information Center on Health Services Research and Health Care Technology (NICHSR)
Alison CernichNICHD Deputy Directoralison.cernich@nih.hhs.gov
John (Jack) Moye, Jr., MDActing Director - National Children's Study
NICHD Medical Officer - Maternal & Pediatric Infectious Disease Branch		moyej@exchange.nih.gov
Nahida Chakhtoura, MD, MsGHNICHD Medical Officer
Maternal and Pediatric Infectious Disease Branch		nahida.chakhtoura@nih.gov
Juanita Chinn, PhDNICHD Program Director
Population Dynamics Branch		juanita.chinn@nih.gov
Valerie CottonNICHD Deputy Director
Office of Data Science and Sharing		valerie.cotton@nih.gov
Liz Amos, MLISSpecial Assistant to the Chief Health Data Standards Officer
National Library of Medicine		liz.amos@nih.gov
Office of the National Coordinator for Health IT (ONC)
Carmen SmileyIT Specialist (Systems Analysis)carmen.smiley@hhs.gov
Rachel AbbeyPublic Health Analyst & Program Officerrachel.abbey@hhs.gov
Stephanie GarciaSenior Program Analyststephanie.garcia@hhs.gov
Brittney Boakye, MPHProgram Assistant
Scientific Advancement Branch		brittney.boakye@hhs.gov
Alan TaylorMedical Informatics Officer, Standards and Terminologyalbert.taylor@hhs.gov
\n\n### Acknowledgements\nThis guide was developed and produced through the efforts of Health Level Seven (HL7) and created using the Trifolia-on-FHIR tool, provided by Lantana Consulting Group. The HL7 Project Insight reference number for this project is 1736.\nThe editors appreciate the support and sponsorship of the HL7 Public Health Workgroup, and all volunteers and staff associated with the creation of this document. This guide would not have been possible without the support of the following groups.\nHealth Level Seven, HL7, CDA, CCD, FHIR and the [FLAME DESIGN] are registered trademarks of Health Level Seven International, registered in the US Trademark Office.\n\nThis IG includes content from SNOMED CT, which is copyright © 2002+ International Health Terminology Standards Development Organisation (IHTSDO), and distributed by agreement between IHTSDO and HL7. Implementer use of SNOMED CT is not covered by this agreement.\n\nThis material contains content from [LOINC](http://loinc.org). LOINC is copyright © 1995-2021, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license at https://loinc.org/kb/license/. LOINC® is a registered United States trademark of Regenstrief Institute, Inc. (built Wed, Mar 29, 2023 19:33+0000+00:00)"},{"name":"hl7.fhir.us.military-service.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/military-service","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.military-service.r4-1.0.0.tgz","date":"2025-10-29T00:11:41.000Z","description":"Military Service History and Status is an implementation guide for military service history and veteran status verification/confirmation. (built Tue, May 30, 2023 15:08+0000+00:00)"},{"name":"hl7.fhir.us.military-service.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/military-service","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.military-service.r4b-1.0.0.tgz","date":"2025-10-29T00:11:43.000Z","description":"Military Service History and Status is an implementation guide for military service history and veteran status verification/confirmation. (built Tue, May 30, 2023 15:08+0000+00:00)"},{"name":"hl7.fhir.us.ndh.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/ndh","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.ndh.r4-1.0.0.tgz","date":"2025-10-29T00:11:55.000Z"},{"name":"hl7.fhir.us.ndh.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/ndh","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.ndh.r4b-1.0.0.tgz","date":"2025-10-29T00:11:59.000Z"},{"name":"hl7.fhir.us.nhsn-dqm.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/nhsn-dqm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.nhsn-dqm.r4-1.0.0.tgz","date":"2025-10-29T00:12:05.000Z","description":"This content describes the specifications for the for the Health Level Seven International® (HL7) Fast Healthcare Interoperability Resources® (FHIR) digital quality measures (dQMs) reported to the National Healthcare Safety Network (NHSN). (built Wed, Jul 9, 2025 20:38+0000+00:00)"},{"name":"hl7.fhir.us.nhsn-dqm.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/nhsn-dqm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.nhsn-dqm.r4b-1.0.0.tgz","date":"2025-10-29T00:12:10.000Z","description":"This content describes the specifications for the for the Health Level Seven International® (HL7) Fast Healthcare Interoperability Resources® (FHIR) digital quality measures (dQMs) reported to the National Healthcare Safety Network (NHSN). (built Wed, Jul 9, 2025 20:38+0000+00:00)"},{"name":"hl7.fhir.us.odh.r4","version":"1.3.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/odh","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.odh.r4-1.3.0.tgz","date":"2025-10-29T00:12:13.000Z","description":"**HL7 FHIR Profile: Occupational Data for Health (ODH), Release 1.3 (Standard for Trial Use)**\n\nThis Implementation Guide is a reconciled version, containing changes in response to comments received in the Sept. 2018 ballot. It has been updated to FHIR R4.0.1.\n\n**Introduction and Guidance**\n\nThis Implementation Guide (IG) contains profiles to implement support for Occupational Data for Health (ODH). ODH describes structured work information primarily designed to facilitate clinical care, including population health and value-based care. ODH also can be used to support public health reporting. ODH is not designed to support billing activities. \nThis set of FHIR profiles is specified as a composition resource, but it is not intended to be used as a stand-alone composition. Rather, the desired content should be included in broader IGs and available as a response to requests for ODH information. Some use cases may leverage only a subset of the ODH profiles, and these should be specified within those work products. For instance, in the Vital Records Death Reporting (VRDR) IG, the data requirements for work information are limited to those in the Usual Work profile.\nWhile this profile is specified for the US Realm, the design is intended to also support international needs. Three of the referenced value sets—Occupation, Industry, and Supervisory Level— are necessarily US specific. The remaining three value sets—Work Schedule, Employment Status, and Work Classification—use international concepts. Input is requested regarding whether these should be specified as ‘extensible’, ‘required’ (using ‘text only’ where a concept does not yet exist such as a new occupation), or as an ‘example’ for those US specific concepts.\n\n**Background**\n\nThe majority of adults in the U.S. spend more than half their waking hours at work. Therefore, health and work are inextricably inter-related. For example, the management of chronic conditions requires taking the patient’s work environment into consideration. Work-related conditions are often first brought to the attention of a primary care provider. Some conditions related to exposure to hazards in the workplace can have a long latency, requiring knowledge of a person’s work history for recognition, diagnosis, and treatment. The recognition of new conditions related to previously unknown workplace hazards has often come from astute clinicians, which requires knowledge of the patient’s work. ONC has indicated recognition of the value of work information for health care.\nThe incorporation of ODH into Electronic Health Records (EHRs) and other health IT systems presents an opportunity to improve health in relation to work. ODH provides a structure and standardization for work information that can be used across systems to take advantage of system tools for clinical decision support, population health, and public health. Research has been conducted and guidance is available to support clinicians, and the use of ODH by health IT systems can support identification of patients that would benefit the most from this knowledge.\n\n**Scope**\n\nThe Occupational Data for Health (ODH) FHIR IG covers information about a patient’s work, including some voluntary work, or a patient’s household members’ work. ODH is designed for the social history section of a medical record, to facilitate clinical care in multiple disciplines and delivery environments. ODH can be used for clinical decision support, population health activities and value-based care, and public health reporting. The scope of the work information in ODH includes:\n\n• Employment Status\n\n• Retirement Date\n\n• Combat Zone Period\n\n• Past or Present Job for the patient or a household member, which includes:\n \n o Past or Present Job Occupation\n \n o Past or Present Job Industry\n \n o Work Classification\n \n o Work Schedule, which includes:\n \n - Weekly Work Days\n \n - Daily Work Hours\n \n o Job Duty\n \n o Occupational Hazard\n \n o Employer name\n \n o Employer address\n \n o Related Subject (when it is Past or Present Job of a household member of the person)\n \n o Start/End Dates\n\n• Usual Work of the patient or a household member, which includes:\n \n o Usual Occupation\n \n o Usual Industry\n \n o Usual Occupation Duration\n \n o Related Subject (when it is Usual Work of a household member of the person)\n \n o Start Date\n\n**Known Issues and Limitations**\n\nThis IG includes more extensive occupational data than typically collected in current systems. The content and structure of this IG is intended to inform clinical care, support population health, and contribute to public health activities. While there may be some overlap with administrative and billing information maintained by some systems, the information in this IG is not designed to support billing and administrative needs.\nWhile multiple retirement dates are supported, the retirement date is not linked to any specific job, or usual occupation.\n\n**Credits**\n\nCo-Editor:\nLori Reed-Fourquet\ne-HealthSign, LLC\nlfourquet@ehealthsign.com\n\nCo-Editor:\nRob Hausam\nHausam Consulting\nrob@hausamconsulting.com\n\nCo-Editor:\nMark Kramer\nMITRE Corporation\nmkramer@mitre.org\n\nThis set of FHIR profiles was produced and developed through the efforts of a project of the National Institute of Occupational Safety and Health (NIOSH), the U.S. federal agency responsible for conducting research and making recommendations for the prevention of work-related injury and illness. NIOSH is a part of the U.S. Centers for Disease Control and Prevention (CDC). NIOSH consulted stakeholders in clinical care, public health, health IT, health informatics and U.S. government agencies to develop ODH. The HL7® Public Health and Emergency Response Work Group sponsored development of this set of FHIR profiles. Co-sponsoring HL7® Work Groups were Orders and Observations (OO), Patient Administration (PA), and Clinical Quality Initiative (CQI).\nThe following individuals provided subject matter expertise for this set of FHIR profiles: Genevieve Barkocy Luensman, NIOSH; Eileen Storey, Professional Services Partners, formerly NIOSH; Margaret S. Filios, NIOSH; Christina Socias-Morales, NIOSH; Lauren Brewer, NIOSH; Barbara Wallace, Professional Services Partners.\n\n**Authors**\n\nName Email/URL\nHL7 International - Public Health http://www.hl7.org/Special/committees/pher (built Mon, Mar 27, 2023 09:54+1100+11:00)"},{"name":"hl7.fhir.us.odh.r4b","version":"1.3.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/odh","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.odh.r4b-1.3.0.tgz","date":"2025-10-29T00:12:14.000Z","description":"**HL7 FHIR Profile: Occupational Data for Health (ODH), Release 1.3 (Standard for Trial Use)**\n\nThis Implementation Guide is a reconciled version, containing changes in response to comments received in the Sept. 2018 ballot. It has been updated to FHIR R4.0.1.\n\n**Introduction and Guidance**\n\nThis Implementation Guide (IG) contains profiles to implement support for Occupational Data for Health (ODH). ODH describes structured work information primarily designed to facilitate clinical care, including population health and value-based care. ODH also can be used to support public health reporting. ODH is not designed to support billing activities. \nThis set of FHIR profiles is specified as a composition resource, but it is not intended to be used as a stand-alone composition. Rather, the desired content should be included in broader IGs and available as a response to requests for ODH information. Some use cases may leverage only a subset of the ODH profiles, and these should be specified within those work products. For instance, in the Vital Records Death Reporting (VRDR) IG, the data requirements for work information are limited to those in the Usual Work profile.\nWhile this profile is specified for the US Realm, the design is intended to also support international needs. Three of the referenced value sets—Occupation, Industry, and Supervisory Level— are necessarily US specific. The remaining three value sets—Work Schedule, Employment Status, and Work Classification—use international concepts. Input is requested regarding whether these should be specified as ‘extensible’, ‘required’ (using ‘text only’ where a concept does not yet exist such as a new occupation), or as an ‘example’ for those US specific concepts.\n\n**Background**\n\nThe majority of adults in the U.S. spend more than half their waking hours at work. Therefore, health and work are inextricably inter-related. For example, the management of chronic conditions requires taking the patient’s work environment into consideration. Work-related conditions are often first brought to the attention of a primary care provider. Some conditions related to exposure to hazards in the workplace can have a long latency, requiring knowledge of a person’s work history for recognition, diagnosis, and treatment. The recognition of new conditions related to previously unknown workplace hazards has often come from astute clinicians, which requires knowledge of the patient’s work. ONC has indicated recognition of the value of work information for health care.\nThe incorporation of ODH into Electronic Health Records (EHRs) and other health IT systems presents an opportunity to improve health in relation to work. ODH provides a structure and standardization for work information that can be used across systems to take advantage of system tools for clinical decision support, population health, and public health. Research has been conducted and guidance is available to support clinicians, and the use of ODH by health IT systems can support identification of patients that would benefit the most from this knowledge.\n\n**Scope**\n\nThe Occupational Data for Health (ODH) FHIR IG covers information about a patient’s work, including some voluntary work, or a patient’s household members’ work. ODH is designed for the social history section of a medical record, to facilitate clinical care in multiple disciplines and delivery environments. ODH can be used for clinical decision support, population health activities and value-based care, and public health reporting. The scope of the work information in ODH includes:\n\n• Employment Status\n\n• Retirement Date\n\n• Combat Zone Period\n\n• Past or Present Job for the patient or a household member, which includes:\n \n o Past or Present Job Occupation\n \n o Past or Present Job Industry\n \n o Work Classification\n \n o Work Schedule, which includes:\n \n - Weekly Work Days\n \n - Daily Work Hours\n \n o Job Duty\n \n o Occupational Hazard\n \n o Employer name\n \n o Employer address\n \n o Related Subject (when it is Past or Present Job of a household member of the person)\n \n o Start/End Dates\n\n• Usual Work of the patient or a household member, which includes:\n \n o Usual Occupation\n \n o Usual Industry\n \n o Usual Occupation Duration\n \n o Related Subject (when it is Usual Work of a household member of the person)\n \n o Start Date\n\n**Known Issues and Limitations**\n\nThis IG includes more extensive occupational data than typically collected in current systems. The content and structure of this IG is intended to inform clinical care, support population health, and contribute to public health activities. While there may be some overlap with administrative and billing information maintained by some systems, the information in this IG is not designed to support billing and administrative needs.\nWhile multiple retirement dates are supported, the retirement date is not linked to any specific job, or usual occupation.\n\n**Credits**\n\nCo-Editor:\nLori Reed-Fourquet\ne-HealthSign, LLC\nlfourquet@ehealthsign.com\n\nCo-Editor:\nRob Hausam\nHausam Consulting\nrob@hausamconsulting.com\n\nCo-Editor:\nMark Kramer\nMITRE Corporation\nmkramer@mitre.org\n\nThis set of FHIR profiles was produced and developed through the efforts of a project of the National Institute of Occupational Safety and Health (NIOSH), the U.S. federal agency responsible for conducting research and making recommendations for the prevention of work-related injury and illness. NIOSH is a part of the U.S. Centers for Disease Control and Prevention (CDC). NIOSH consulted stakeholders in clinical care, public health, health IT, health informatics and U.S. government agencies to develop ODH. The HL7® Public Health and Emergency Response Work Group sponsored development of this set of FHIR profiles. Co-sponsoring HL7® Work Groups were Orders and Observations (OO), Patient Administration (PA), and Clinical Quality Initiative (CQI).\nThe following individuals provided subject matter expertise for this set of FHIR profiles: Genevieve Barkocy Luensman, NIOSH; Eileen Storey, Professional Services Partners, formerly NIOSH; Margaret S. Filios, NIOSH; Christina Socias-Morales, NIOSH; Lauren Brewer, NIOSH; Barbara Wallace, Professional Services Partners.\n\n**Authors**\n\nName Email/URL\nHL7 International - Public Health http://www.hl7.org/Special/committees/pher (built Mon, Mar 27, 2023 09:54+1100+11:00)"},{"name":"hl7.fhir.us.pacio-adi.r4","version":"2.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/pacio-adi","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.pacio-adi.r4-2.0.0-ballot.tgz","date":"2025-10-29T00:12:18.000Z","description":"PACIO Advance Directive Interoperability Implementation Guide (built Mon, Aug 4, 2025 21:33+0000+00:00)"},{"name":"hl7.fhir.us.pacio-adi.r4b","version":"2.0.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/pacio-adi","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.pacio-adi.r4b-2.0.0-ballot.tgz","date":"2025-10-29T00:12:25.000Z","description":"PACIO Advance Directive Interoperability Implementation Guide (built Mon, Aug 4, 2025 21:33+0000+00:00)"},{"name":"hl7.fhir.us.pacio-pfe.r4","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/pacio-pfe","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.pacio-pfe.r4-2.0.0.tgz","date":"2025-10-29T00:12:34.000Z","description":"FHIR Implementation Guide to exchange assessments of and data on a person's functioning, including body functions, activities, and participation, between post-acute care (PAC) and other providers, patients, and key stakeholders (built Wed, Jul 23, 2025 17:23+0000+00:00)"},{"name":"hl7.fhir.us.pacio-pfe.r4b","version":"2.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/pacio-pfe","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.pacio-pfe.r4b-2.0.0.tgz","date":"2025-10-29T00:12:41.000Z","description":"FHIR Implementation Guide to exchange assessments of and data on a person's functioning, including body functions, activities, and participation, between post-acute care (PAC) and other providers, patients, and key stakeholders (built Wed, Jul 23, 2025 17:23+0000+00:00)"},{"name":"hl7.fhir.us.pacio-toc.r4","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/pacio-toc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.pacio-toc.r4-1.0.0-ballot.tgz","date":"2025-10-29T00:12:44.000Z","description":"Implementation Guide for exchanging Transitions of Care minimum data set for patients transitioning between health organizations. (built Fri, Mar 28, 2025 13:46+0000+00:00)"},{"name":"hl7.fhir.us.pacio-toc.r4b","version":"1.0.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/pacio-toc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.pacio-toc.r4b-1.0.0-ballot.tgz","date":"2025-10-29T00:12:51.000Z","description":"Implementation Guide for exchanging Transitions of Care minimum data set for patients transitioning between health organizations. (built Fri, Mar 28, 2025 13:46+0000+00:00)"},{"name":"hl7.fhir.us.pco.r4","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/pco","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.pco.r4-1.0.0-ballot.tgz","date":"2025-10-29T00:12:55.000Z","description":"Person-Centered Outcomes (PCO) FHIR Implementation Guide (built Fri, Mar 28, 2025 21:02+0000+00:00)"},{"name":"hl7.fhir.us.pco.r4b","version":"1.0.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/pco","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.pco.r4b-1.0.0-ballot.tgz","date":"2025-10-29T00:12:57.000Z","description":"Person-Centered Outcomes (PCO) FHIR Implementation Guide (built Fri, Mar 28, 2025 21:02+0000+00:00)"},{"name":"hl7.fhir.us.pdmp.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/pdmp","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.pdmp.r4-1.0.0.tgz","date":"2025-10-29T00:13:01.000Z","description":"US Prescription Drug Monitoring Program (PDMP) FHIR IG (built Tue, Oct 15, 2024 18:35+0000+00:00)"},{"name":"hl7.fhir.us.pdmp.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/pdmp","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.pdmp.r4b-1.0.0.tgz","date":"2025-10-29T00:13:05.000Z","description":"US Prescription Drug Monitoring Program (PDMP) FHIR IG (built Tue, Oct 15, 2024 18:35+0000+00:00)"},{"name":"hl7.fhir.us.ph-library.r4","version":"2.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/ph-library","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.ph-library.r4-2.0.0-ballot.tgz","date":"2025-10-29T00:13:11.000Z","description":"The US Public Health Profiles Library (USPHPL) is a collection of reusable architecture and content profiles representing common public health concepts and patterns. (built Wed, Jul 30, 2025 14:31+0000+00:00)"},{"name":"hl7.fhir.us.ph-library.r4b","version":"2.0.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/ph-library","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.ph-library.r4b-2.0.0-ballot.tgz","date":"2025-10-29T00:13:16.000Z","description":"The US Public Health Profiles Library (USPHPL) is a collection of reusable architecture and content profiles representing common public health concepts and patterns. (built Wed, Jul 30, 2025 14:31+0000+00:00)"},{"name":"hl7.fhir.us.physical-activity.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/physical-activity","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.physical-activity.r4-1.0.0.tgz","date":"2025-10-29T00:13:22.000Z","description":"This implementation guide provides standardization around patient physical activity, including: * measures for recording a patient's level of physical activity; * measures to support assertions of physical activity, including device-based measures; * goals and care plans related to improving a patient's physical activity level; * orders for interventions seeking to improve a patient's physical activity level; and * processes to support closing the loop and evaluating the success of such interventions. (built Fri, Aug 25, 2023 15:58+0000+00:00)"},{"name":"hl7.fhir.us.physical-activity.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/physical-activity","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.physical-activity.r4b-1.0.0.tgz","date":"2025-10-29T00:13:27.000Z","description":"This implementation guide provides standardization around patient physical activity, including: * measures for recording a patient's level of physical activity; * measures to support assertions of physical activity, including device-based measures; * goals and care plans related to improving a patient's physical activity level; * orders for interventions seeking to improve a patient's physical activity level; and * processes to support closing the loop and evaluating the success of such interventions. (built Fri, Aug 25, 2023 15:58+0000+00:00)"},{"name":"hl7.fhir.us.qicore.r4","version":"8.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/qicore","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.qicore.r4-8.0.0-ballot.tgz","date":"2025-10-29T00:13:45.000Z","description":"The QICore Implementation Guide defines a set of FHIR profiles with extensions and bindings needed to create interoperable, quality-focused applications. The profiles in this implementation guide derive from and extend the [US Core](http://hl7.org/fhir/us/core) profiles to provide a common foundation for building, sharing, and evaluating knowledge artifacts across quality improvement efforts in the US Realm. (built Fri, Aug 1, 2025 15:30+0000+00:00)"},{"name":"hl7.fhir.us.qicore.r4b","version":"8.0.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/qicore","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.qicore.r4b-8.0.0-ballot.tgz","date":"2025-10-29T00:13:57.000Z","description":"The QICore Implementation Guide defines a set of FHIR profiles with extensions and bindings needed to create interoperable, quality-focused applications. The profiles in this implementation guide derive from and extend the [US Core](http://hl7.org/fhir/us/core) profiles to provide a common foundation for building, sharing, and evaluating knowledge artifacts across quality improvement efforts in the US Realm. (built Fri, Aug 1, 2025 15:30+0000+00:00)"},{"name":"hl7.fhir.us.registry-protocols.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/registry-protocols","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.registry-protocols.r4-1.0.0.tgz","date":"2025-10-29T00:14:05.000Z","description":"The IG demonstrates a process and workflow to support the needs of clinical registries to define how registry submissions can be automatically extracted from multiple data sources and combined into a registry submission. (built Tue, Nov 14, 2023 18:48+0000+00:00)"},{"name":"hl7.fhir.us.registry-protocols.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/registry-protocols","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.registry-protocols.r4b-1.0.0.tgz","date":"2025-10-29T00:14:16.000Z","description":"The IG demonstrates a process and workflow to support the needs of clinical registries to define how registry submissions can be automatically extracted from multiple data sources and combined into a registry submission. (built Tue, Nov 14, 2023 18:48+0000+00:00)"},{"name":"hl7.fhir.us.resp-net.r4","version":"2.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/resp-net","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.resp-net.r4-2.0.0-ballot.tgz","date":"2025-10-29T00:14:22.000Z","description":"The RESP-NET Content IG focuses on the respiratory virus surveillance data that will be extracted from EHRs via FHIR and APIs and sent to RESP-NET sites. (built Mon, Aug 4, 2025 13:36+0000+00:00)"},{"name":"hl7.fhir.us.resp-net.r4b","version":"2.0.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/resp-net","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.resp-net.r4b-2.0.0-ballot.tgz","date":"2025-10-29T00:14:27.000Z","description":"The RESP-NET Content IG focuses on the respiratory virus surveillance data that will be extracted from EHRs via FHIR and APIs and sent to RESP-NET sites. (built Mon, Aug 4, 2025 13:36+0000+00:00)"},{"name":"hl7.fhir.us.safr.r4","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/safr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.safr.r4-1.0.0-ballot.tgz","date":"2025-10-29T00:14:30.000Z","description":"US Situational Awareness Framework for Reporting (US SAFR) (built Fri, Mar 28, 2025 19:37+0000+00:00)"},{"name":"hl7.fhir.us.safr.r4b","version":"1.0.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/safr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.safr.r4b-1.0.0-ballot.tgz","date":"2025-10-29T00:14:31.000Z","description":"US Situational Awareness Framework for Reporting (US SAFR) (built Fri, Mar 28, 2025 19:37+0000+00:00)"},{"name":"hl7.fhir.us.sdoh-clinicalcare.r4","version":"2.3.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/sdoh-clinicalcare","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.sdoh-clinicalcare.r4-2.3.0.tgz","date":"2025-10-29T00:14:47.000Z","description":"This HL7 Implementation Guide (IG) defines how to exchange Social Determinants of Health (SDOH) content defined by the Gravity Project using the HL7 FHIR standard.. (built Thu, May 15, 2025 21:43+0000+00:00)"},{"name":"hl7.fhir.us.sdoh-clinicalcare.r4b","version":"2.3.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/sdoh-clinicalcare","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.sdoh-clinicalcare.r4b-2.3.0.tgz","date":"2025-10-29T00:14:57.000Z","description":"This HL7 Implementation Guide (IG) defines how to exchange Social Determinants of Health (SDOH) content defined by the Gravity Project using the HL7 FHIR standard.. (built Thu, May 15, 2025 21:43+0000+00:00)"},{"name":"hl7.fhir.us.sirb.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/sirb","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.sirb.r4-1.0.0.tgz","date":"2025-10-29T00:15:00.000Z","description":"Data standards to move data and documents from clinical research sites to a single ethics review board in support of the \"NIH Policy on the Use of a Single Institutional Review Board for Multi-Site Research. (built Thu, Apr 20, 2023 13:43+0000+00:00)"},{"name":"hl7.fhir.us.sirb.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/sirb","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.sirb.r4b-1.0.0.tgz","date":"2025-10-29T00:15:01.000Z","description":"Data standards to move data and documents from clinical research sites to a single ethics review board in support of the \"NIH Policy on the Use of a Single Institutional Review Board for Multi-Site Research. (built Thu, Apr 20, 2023 13:43+0000+00:00)"},{"name":"hl7.fhir.us.smp.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/smp","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.smp.r4-1.0.0.tgz","date":"2025-10-29T00:15:06.000Z","description":"Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Fri, May 16, 2025 20:17+0000+00:00)"},{"name":"hl7.fhir.us.smp.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/smp","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.smp.r4b-1.0.0.tgz","date":"2025-10-29T00:15:10.000Z","description":"Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Fri, May 16, 2025 20:17+0000+00:00)"},{"name":"hl7.fhir.us.specialty-rx.r4","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/specialty-rx","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.specialty-rx.r4-2.0.0.tgz","date":"2025-10-29T00:15:12.000Z","description":"This implementation guide describes the exchange of information needed to dispense specialty medications and enroll patients in associated programs offered by pharmaceutical manufacturers and others. (built Thu, May 4, 2023 14:33+0000+00:00)"},{"name":"hl7.fhir.us.specialty-rx.r4b","version":"2.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/specialty-rx","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.specialty-rx.r4b-2.0.0.tgz","date":"2025-10-29T00:15:14.000Z","description":"This implementation guide describes the exchange of information needed to dispense specialty medications and enroll patients in associated programs offered by pharmaceutical manufacturers and others. (built Thu, May 4, 2023 14:33+0000+00:00)"},{"name":"hl7.fhir.us.udap-security.r4","version":"2.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/udap-security","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.udap-security.r4-2.0.0-ballot.tgz","date":"2025-10-29T00:15:29.000Z","description":"This implementation guide describes how to extend OAuth 2.0 to support secure and scalable workflows for business-to-business (B2B) apps that implement the client credentials flow or authorization code flow. (built Tue, Dec 17, 2024 15:02+0000+00:00)"},{"name":"hl7.fhir.us.udap-security.r4b","version":"2.0.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/udap-security","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.udap-security.r4b-2.0.0-ballot.tgz","date":"2025-10-29T00:15:32.000Z","description":"This implementation guide describes how to extend OAuth 2.0 to support secure and scalable workflows for business-to-business (B2B) apps that implement the client credentials flow or authorization code flow. (built Tue, Dec 17, 2024 15:02+0000+00:00)"},{"name":"hl7.fhir.us.vr-common-library.r4","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/vr-common-library","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.vr-common-library.r4-2.0.0.tgz","date":"2025-10-29T00:15:43.000Z"},{"name":"hl7.fhir.us.vr-common-library.r4b","version":"2.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/vr-common-library","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.vr-common-library.r4b-2.0.0.tgz","date":"2025-10-29T00:15:47.000Z"},{"name":"hl7.fhir.us.vrdr.r4","version":"3.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/vrdr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.vrdr.r4-3.0.0.tgz","date":"2025-10-29T00:16:04.000Z"},{"name":"hl7.fhir.us.vrdr.r4b","version":"3.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/us/vrdr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.vrdr.r4b-3.0.0.tgz","date":"2025-10-29T00:16:15.000Z"},{"name":"hl7.fhir.uv.ae-research-backport-ig.r4","version":"1.0.1","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/ae-research-backport-ig","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.ae-research-backport-ig.r4-1.0.1.tgz","date":"2025-10-29T00:16:25.000Z","description":"### Intent The intent of this guide is to provide a profile on the FHIR AdverseEvent Resource suitable for Clinical Research. ### Overview A single Adverse Event (AE) may need to be reported in multiple ways. Choosing the appropriate form of the reporting is dependent upon workflow patterns. In particular, the implementation guides for Clinical Care adverse events and Clinical Research adverse events provide important extensions, value-sets and examples for implementing AdverseEvent. This guide, the Clinical Research adverse event implementation guide, is for the clinical research setting. In this setting, the event is tracked and evaluated as part of the clinical research process for the research study. In the research setting an adverse event is the result of an intervention that caused unintentional harm to a specific subject or group of subjects (this is surfaced in the profile as a constraint of ‘actual’ for the value of ‘actuality’). An example of an adverse event in the clinical research setting would be a patient develops renal failure while on a study drug. These events are characterized by the need to capture cause-and-effect (although they might not be known at the time of the event), severity, and outcome. The context of an adverse event is also important, and captured in the AdverseEvent Clinical Research Profile data elements. A subject may have condition(s) or current treatments (medications, diet, devices) that impact their response to a newly introduced medication, device or procedure. Knowledge of these variables is essential in establishing a cause-and-effect relationship for an adverse event. This information is represented with corresponding resources (e.g. Procedure Resource for procedures, etc.) and referenced. A potential adverse event may also be called a near miss or an error, these are not reported with the AdverseEvent Clinical Research Profile. ### Scope This FHIR IG enables the collection of adverse events in real-world data (RWD) sources such as electronic health records (EHR) and personal health records (PHR) that occur during clinical trials. It ensures the appropriate AE representation required to support clinical research trials within a regulated environment. As the AEs are collected in RWD sources, the data can be transmitted via FHIR to clinical trial management systems, regulatory agencies, sponsors, and clinical research organizations for further processing and reporting. In the pre-market clinical research setting, serious adverse events must be reported to the sponsor, clinical research organization, and regulatory agencies within a specific time frame for Institutional Review Boards (IRBs) and Data Safety Monitoring Board (DSMB) review. By using this IG, a clinical investigator can document an AE in the EHR, it can be received by a secondary clinical trial management system for triage and then forwarded to the sponsor and regulatory agencies. Similarly, a patient on a clinical trial can record an adverse event in their PHR that is then shared with the clinical investigator and reported to the sponsor and regulatory agencies as necessary. In a post-market situation, a patient, provider, or manufacturer can record the adverse event in a system and then report it to the FDA as a FHIR based MedWatch form. Within this guide are several examples. Every effort has been made to capture the most important details of the use of the AdverseEvent profile. However, some examples may provide only a stub to referenced resources (e.g. instances of Patient Resource will be referenced using logical ids but are not resolvable, implementation of Patient is left for other guidance and is not the subject of this guide). Connectathons are ideal opportunities to create, compare and consider the holistic implementation of all FHIR Resources. (built Tue, Apr 30, 2024 20:50+0000+00:00)"},{"name":"hl7.fhir.uv.ae-research-backport-ig.r4b","version":"1.0.1","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/ae-research-backport-ig","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.ae-research-backport-ig.r4b-1.0.1.tgz","date":"2025-10-29T00:16:28.000Z","description":"### Intent The intent of this guide is to provide a profile on the FHIR AdverseEvent Resource suitable for Clinical Research. ### Overview A single Adverse Event (AE) may need to be reported in multiple ways. Choosing the appropriate form of the reporting is dependent upon workflow patterns. In particular, the implementation guides for Clinical Care adverse events and Clinical Research adverse events provide important extensions, value-sets and examples for implementing AdverseEvent. This guide, the Clinical Research adverse event implementation guide, is for the clinical research setting. In this setting, the event is tracked and evaluated as part of the clinical research process for the research study. In the research setting an adverse event is the result of an intervention that caused unintentional harm to a specific subject or group of subjects (this is surfaced in the profile as a constraint of ‘actual’ for the value of ‘actuality’). An example of an adverse event in the clinical research setting would be a patient develops renal failure while on a study drug. These events are characterized by the need to capture cause-and-effect (although they might not be known at the time of the event), severity, and outcome. The context of an adverse event is also important, and captured in the AdverseEvent Clinical Research Profile data elements. A subject may have condition(s) or current treatments (medications, diet, devices) that impact their response to a newly introduced medication, device or procedure. Knowledge of these variables is essential in establishing a cause-and-effect relationship for an adverse event. This information is represented with corresponding resources (e.g. Procedure Resource for procedures, etc.) and referenced. A potential adverse event may also be called a near miss or an error, these are not reported with the AdverseEvent Clinical Research Profile. ### Scope This FHIR IG enables the collection of adverse events in real-world data (RWD) sources such as electronic health records (EHR) and personal health records (PHR) that occur during clinical trials. It ensures the appropriate AE representation required to support clinical research trials within a regulated environment. As the AEs are collected in RWD sources, the data can be transmitted via FHIR to clinical trial management systems, regulatory agencies, sponsors, and clinical research organizations for further processing and reporting. In the pre-market clinical research setting, serious adverse events must be reported to the sponsor, clinical research organization, and regulatory agencies within a specific time frame for Institutional Review Boards (IRBs) and Data Safety Monitoring Board (DSMB) review. By using this IG, a clinical investigator can document an AE in the EHR, it can be received by a secondary clinical trial management system for triage and then forwarded to the sponsor and regulatory agencies. Similarly, a patient on a clinical trial can record an adverse event in their PHR that is then shared with the clinical investigator and reported to the sponsor and regulatory agencies as necessary. In a post-market situation, a patient, provider, or manufacturer can record the adverse event in a system and then report it to the FDA as a FHIR based MedWatch form. Within this guide are several examples. Every effort has been made to capture the most important details of the use of the AdverseEvent profile. However, some examples may provide only a stub to referenced resources (e.g. instances of Patient Resource will be referenced using logical ids but are not resolvable, implementation of Patient is left for other guidance and is not the subject of this guide). Connectathons are ideal opportunities to create, compare and consider the holistic implementation of all FHIR Resources. (built Tue, Apr 30, 2024 20:50+0000+00:00)"},{"name":"hl7.fhir.uv.application-feature.r4","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/application-feature","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.application-feature.r4-1.0.0-ballot.tgz","date":"2025-10-29T00:16:33.000Z"},{"name":"hl7.fhir.uv.application-feature.r4b","version":"1.0.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/application-feature","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.application-feature.r4b-1.0.0-ballot.tgz","date":"2025-10-29T00:16:34.000Z"},{"name":"hl7.fhir.uv.bulkdata.r4","version":"3.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/bulkdata","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.bulkdata.r4-3.0.0-ballot.tgz","date":"2025-10-29T00:16:44.000Z","description":"FHIR based approach for exporting large data sets from a FHIR server to a client application (built Mon, Aug 4, 2025 20:07+0000+00:00)"},{"name":"hl7.fhir.uv.bulkdata.r4b","version":"3.0.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/bulkdata","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.bulkdata.r4b-3.0.0-ballot.tgz","date":"2025-10-29T00:16:45.000Z","description":"FHIR based approach for exporting large data sets from a FHIR server to a client application (built Mon, Aug 4, 2025 20:07+0000+00:00)"},{"name":"hl7.fhir.uv.cardx-htn-mng.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/cardx-htn-mng","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.cardx-htn-mng.r4-1.0.0.tgz","date":"2025-10-29T00:16:51.000Z"},{"name":"hl7.fhir.uv.cardx-htn-mng.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/cardx-htn-mng","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.cardx-htn-mng.r4b-1.0.0.tgz","date":"2025-10-29T00:16:54.000Z"},{"name":"hl7.fhir.uv.cgm.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/cgm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.cgm.r4-1.0.0.tgz","date":"2025-10-29T00:17:03.000Z","description":"Communicate Continuous Glucose Monitoring (CGM) data using FHIR (built Wed, Sep 24, 2025 19:39+0000+00:00)"},{"name":"hl7.fhir.uv.cgm.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/cgm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.cgm.r4b-1.0.0.tgz","date":"2025-10-29T00:17:07.000Z","description":"Communicate Continuous Glucose Monitoring (CGM) data using FHIR (built Wed, Sep 24, 2025 19:39+0000+00:00)"},{"name":"hl7.fhir.uv.cow.r4","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/cow","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.cow.r4-1.0.0-ballot.tgz","date":"2025-10-29T00:17:10.000Z","description":"An Implementation Guide providing the foundational guidance for order-based workflow FHIR interoperability (built Mon, Apr 7, 2025 15:35+0000+00:00)"},{"name":"hl7.fhir.uv.cow.r4b","version":"1.0.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/cow","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.cow.r4b-1.0.0-ballot.tgz","date":"2025-10-29T00:17:11.000Z","description":"An Implementation Guide providing the foundational guidance for order-based workflow FHIR interoperability (built Mon, Apr 7, 2025 15:35+0000+00:00)"},{"name":"hl7.fhir.uv.cpg.r4","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/cpg","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.cpg.r4-2.0.0.tgz","date":"2025-10-29T00:17:22.000Z","description":"Implementation guidance for creating Clinical Practice Guidelines with formal artifacts to facilitate sharing and implementation of the guideline (built Tue, Nov 26, 2024 17:23+0000+00:00)"},{"name":"hl7.fhir.uv.cpg.r4b","version":"2.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/cpg","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.cpg.r4b-2.0.0.tgz","date":"2025-10-29T00:17:27.000Z","description":"Implementation guidance for creating Clinical Practice Guidelines with formal artifacts to facilitate sharing and implementation of the guideline (built Tue, Nov 26, 2024 17:23+0000+00:00)"},{"name":"hl7.fhir.uv.cql.r4","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/cql","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.cql.r4-2.0.0.tgz","date":"2025-10-29T00:17:40.000Z","description":"This 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. (built Tue, Jul 8, 2025 14:56+0000+00:00)"},{"name":"hl7.fhir.uv.cql.r4b","version":"2.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/cql","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.cql.r4b-2.0.0.tgz","date":"2025-10-29T00:17:49.000Z","description":"This 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. (built Tue, Jul 8, 2025 14:56+0000+00:00)"},{"name":"hl7.fhir.uv.cqm.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/cqm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.cqm.r4-1.0.0.tgz","date":"2025-10-29T00:17:56.000Z","description":"The Fast Healthcare Interoperability Resource (FHIR) Quality Measure Implementation Guide (this IG) describes an approach to representing Quality Measures (QMs) using the FHIR Clinical Reasoning Module and Clinical Quality Language (CQL) in the US Realm. However, this Implementation Guide can be usable for multiple use cases across domains, and much of the content is likely to be usable outside the US Realm. (built Thu, Sep 11, 2025 19:16+0000+00:00)"},{"name":"hl7.fhir.uv.cqm.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/cqm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.cqm.r4b-1.0.0.tgz","date":"2025-10-29T00:18:01.000Z","description":"The Fast Healthcare Interoperability Resource (FHIR) Quality Measure Implementation Guide (this IG) describes an approach to representing Quality Measures (QMs) using the FHIR Clinical Reasoning Module and Clinical Quality Language (CQL) in the US Realm. However, this Implementation Guide can be usable for multiple use cases across domains, and much of the content is likely to be usable outside the US Realm. (built Thu, Sep 11, 2025 19:16+0000+00:00)"},{"name":"hl7.fhir.uv.crmi.r4","version":"2.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/crmi","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.crmi.r4-2.0.0-ballot.tgz","date":"2025-10-29T00:18:18.000Z","description":"This 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. (built Fri, Aug 1, 2025 18:39+0000+00:00)"},{"name":"hl7.fhir.uv.crmi.r4b","version":"2.0.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/crmi","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.crmi.r4b-2.0.0-ballot.tgz","date":"2025-10-29T00:18:30.000Z","description":"This 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. (built Fri, Aug 1, 2025 18:39+0000+00:00)"},{"name":"hl7.fhir.uv.ehrs-rle.r4","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/ehrs-rle","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.ehrs-rle.r4-1.0.0-ballot.tgz","date":"2025-10-29T00:18:43.000Z","description":"EHRS Functional Model - Record Lifecycle Events - FHIR Implementation Guide (built Wed, Dec 7, 2022 16:55+0000+00:00)"},{"name":"hl7.fhir.uv.ehrs-rle.r4b","version":"1.0.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/ehrs-rle","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.ehrs-rle.r4b-1.0.0-ballot.tgz","date":"2025-10-29T00:18:44.000Z","description":"EHRS Functional Model - Record Lifecycle Events - FHIR Implementation Guide (built Wed, Dec 7, 2022 16:55+0000+00:00)"},{"name":"hl7.fhir.uv.extensions","version":"5.3.0-ballot-tc","fhirVersion":"5.0.0","canonical":"http://hl7.org/fhir/extensions","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.extensions-5.3.0-ballot-tc.tgz","date":"2025-10-29T00:18:57.000Z","description":"This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sat, Aug 2, 2025 21:12+1000+10:00)"},{"name":"hl7.fhir.uv.extensions.r4b","version":"5.3.0-ballot-tc","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/extensions","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.extensions.r4b-5.3.0-ballot-tc.tgz","date":"2025-10-29T00:19:25.000Z","description":"This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sat, Aug 2, 2025 21:12+1000+10:00)"},{"name":"hl7.fhir.uv.fhir-clinical-document.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/fhir-clinical-document","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.fhir-clinical-document.r4-1.0.0.tgz","date":"2025-10-29T00:19:44.000Z"},{"name":"hl7.fhir.uv.fhir-clinical-document.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/fhir-clinical-document","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.fhir-clinical-document.r4b-1.0.0.tgz","date":"2025-10-29T00:19:47.000Z"},{"name":"hl7.fhir.uv.fhircast.r4","version":"3.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/fhircast","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.fhircast.r4-3.0.0-ballot.tgz","date":"2025-10-29T00:19:54.000Z","description":"FHIRcast synchronizes healthcare applications in real time to show the same clinical content to a common user. (built Wed, Apr 10, 2024 15:14+0000+00:00)"},{"name":"hl7.fhir.uv.fhircast.r4b","version":"3.0.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/fhircast","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.fhircast.r4b-3.0.0-ballot.tgz","date":"2025-10-29T00:19:55.000Z","description":"FHIRcast synchronizes healthcare applications in real time to show the same clinical content to a common user. (built Wed, Apr 10, 2024 15:14+0000+00:00)"},{"name":"hl7.fhir.uv.genomics-reporting.r4","version":"3.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/genomics-reporting","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.genomics-reporting.r4-3.0.0.tgz","date":"2025-10-29T00:20:04.000Z","description":"Guidelines for reporting of clinical genomics results using HL7 FHIR. (built Thu, Dec 12, 2024 21:07+0000+00:00)"},{"name":"hl7.fhir.uv.genomics-reporting.r4b","version":"3.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/genomics-reporting","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.genomics-reporting.r4b-3.0.0.tgz","date":"2025-10-29T00:20:06.000Z","description":"Guidelines for reporting of clinical genomics results using HL7 FHIR. (built Thu, Dec 12, 2024 21:07+0000+00:00)"},{"name":"hl7.fhir.uv.ichom-breast-cancer.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/ichom-breast-cancer","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.ichom-breast-cancer.r4-1.0.0.tgz","date":"2025-10-29T00:20:14.000Z"},{"name":"hl7.fhir.uv.ichom-breast-cancer.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/ichom-breast-cancer","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.ichom-breast-cancer.r4b-1.0.0.tgz","date":"2025-10-29T00:20:18.000Z"},{"name":"hl7.fhir.uv.ihe-sdc-ecc.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/ihe-sdc-ecc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.ihe-sdc-ecc.r4-1.0.0.tgz","date":"2025-10-29T00:20:22.000Z","description":"Integrating the Healthcare Enterprise (IHE) Structured Data Capture (SDC) on FHIR uses a form-driven workflow to capture and transmit encoded data by creating FHIR Observations (built Tue, Dec 12, 2023 21:56+0000+00:00)"},{"name":"hl7.fhir.uv.ihe-sdc-ecc.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/ihe-sdc-ecc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.ihe-sdc-ecc.r4b-1.0.0.tgz","date":"2025-10-29T00:20:25.000Z","description":"Integrating the Healthcare Enterprise (IHE) Structured Data Capture (SDC) on FHIR uses a form-driven workflow to capture and transmit encoded data by creating FHIR Observations (built Tue, Dec 12, 2023 21:56+0000+00:00)"},{"name":"hl7.fhir.uv.ipa.r4","version":"1.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/ipa","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.ipa.r4-1.1.0.tgz","date":"2025-10-29T00:20:35.000Z","description":"This IG describes how an application acting on behalf of a patient can access information about the patient from an clinical records system using a FHIR based API. The clinical records system may be supporting a clinical care provider (e.g. a hospital, or a general practitioner), or a health data exchange, including a national health record system. (built Wed, Mar 19, 2025 14:43+0000+00:00)"},{"name":"hl7.fhir.uv.ipa.r4b","version":"1.1.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/ipa","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.ipa.r4b-1.1.0.tgz","date":"2025-10-29T00:20:38.000Z","description":"This IG describes how an application acting on behalf of a patient can access information about the patient from an clinical records system using a FHIR based API. The clinical records system may be supporting a clinical care provider (e.g. a hospital, or a general practitioner), or a health data exchange, including a national health record system. (built Wed, Mar 19, 2025 14:34+0000+00:00)"},{"name":"hl7.fhir.uv.ips.r4","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/ips","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.ips.r4-2.0.0.tgz","date":"2025-10-29T00:20:55.000Z"},{"name":"hl7.fhir.uv.ips.r4b","version":"2.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/ips","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.ips.r4b-2.0.0.tgz","date":"2025-10-29T00:21:01.000Z"},{"name":"hl7.fhir.uv.lab-report.r4","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/lab-report","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.lab-report.r4-1.0.0-ballot.tgz","date":"2025-10-29T00:21:03.000Z","description":"This guide describes how the Laboratory Report can be represented in the UV REALM. (built Wed, Aug 14, 2024 20:47+0000+00:00)"},{"name":"hl7.fhir.uv.lab-report.r4b","version":"1.0.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/lab-report","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.lab-report.r4b-1.0.0-ballot.tgz","date":"2025-10-29T00:21:04.000Z","description":"This guide describes how the Laboratory Report can be represented in the UV REALM. (built Wed, Aug 14, 2024 20:47+0000+00:00)"},{"name":"hl7.fhir.uv.livd.r4","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/livd","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.livd.r4-1.0.0-ballot.tgz","date":"2025-10-29T00:21:12.000Z","description":"Recommended LOINC mappings for IVD Devices (built Thu, Dec 21, 2023 20:53+0000+00:00)"},{"name":"hl7.fhir.uv.livd.r4b","version":"1.0.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/livd","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.livd.r4b-1.0.0-ballot.tgz","date":"2025-10-29T00:21:14.000Z","description":"Recommended LOINC mappings for IVD Devices (built Thu, Dec 21, 2023 20:53+0000+00:00)"},{"name":"hl7.fhir.uv.patient-corrections.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/patient-corrections","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.patient-corrections.r4-1.0.0.tgz","date":"2025-10-29T00:21:22.000Z","description":"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. (built Thu, Jul 10, 2025 15:54+0000+00:00)"},{"name":"hl7.fhir.uv.patient-corrections.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/patient-corrections","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.patient-corrections.r4b-1.0.0.tgz","date":"2025-10-29T00:21:24.000Z","description":"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. (built Thu, Jul 10, 2025 15:54+0000+00:00)"},{"name":"hl7.fhir.uv.pddi.r4","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/pddi","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.pddi.r4-1.0.0-ballot.tgz","date":"2025-10-29T00:21:29.000Z"},{"name":"hl7.fhir.uv.pddi.r4b","version":"1.0.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/pddi","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.pddi.r4b-1.0.0-ballot.tgz","date":"2025-10-29T00:21:31.000Z"},{"name":"hl7.fhir.uv.phd.r4","version":"2.0.0-ballot2","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/phd","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.phd.r4-2.0.0-ballot2.tgz","date":"2025-10-29T00:21:49.000Z"},{"name":"hl7.fhir.uv.phd.r4b","version":"2.0.0-ballot2","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/phd","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.phd.r4b-2.0.0-ballot2.tgz","date":"2025-10-29T00:21:53.000Z"},{"name":"hl7.fhir.uv.phr.r4","version":"1.0.0-ballot2","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/phr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.phr.r4-1.0.0-ballot2.tgz","date":"2025-10-29T00:21:55.000Z","description":"Guidance on how to create longitudinal personal health records using FHIR. Exporting, file formats, patient examples, and more. (built Thu, Apr 3, 2025 14:45+0000+00:00)"},{"name":"hl7.fhir.uv.phr.r4b","version":"1.0.0-ballot2","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/phr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.phr.r4b-1.0.0-ballot2.tgz","date":"2025-10-29T00:21:57.000Z","description":"Guidance on how to create longitudinal personal health records using FHIR. Exporting, file formats, patient examples, and more. (built Thu, Apr 3, 2025 14:45+0000+00:00)"},{"name":"hl7.fhir.uv.rtls.r4","version":"1.0.0-ballot2","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/rtls","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.rtls.r4-1.0.0-ballot2.tgz","date":"2025-10-29T00:22:04.000Z","description":"Description of IG (built Thu, Aug 7, 2025 17:38+0000+00:00)"},{"name":"hl7.fhir.uv.rtls.r4b","version":"1.0.0-ballot2","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/rtls","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.rtls.r4b-1.0.0-ballot2.tgz","date":"2025-10-29T00:22:05.000Z","description":"Description of IG (built Thu, Aug 7, 2025 17:38+0000+00:00)"},{"name":"hl7.fhir.uv.sdc.r4","version":"4.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/sdc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.sdc.r4-4.0.0-ballot.tgz","date":"2025-10-29T00:22:18.000Z","description":"The SDC specification provides an infrastructure to standardize the capture and expanded use of patient-level data collected within an EHR. (built Tue, Dec 17, 2024 01:47+0000+00:00)"},{"name":"hl7.fhir.uv.sdc.r4b","version":"4.0.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/sdc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.sdc.r4b-4.0.0-ballot.tgz","date":"2025-10-29T00:22:20.000Z","description":"The SDC specification provides an infrastructure to standardize the capture and expanded use of patient-level data collected within an EHR. (built Tue, Dec 17, 2024 01:47+0000+00:00)"},{"name":"hl7.fhir.uv.security-label-ds4p.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/security-label-ds4p","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.security-label-ds4p.r4-1.0.0.tgz","date":"2025-10-29T00:22:25.000Z","description":"FHIR data segmentation for privacy security label implementation guide (built Mon, Apr 17, 2023 19:19+0000+00:00)"},{"name":"hl7.fhir.uv.security-label-ds4p.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/security-label-ds4p","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.security-label-ds4p.r4b-1.0.0.tgz","date":"2025-10-29T00:22:26.000Z","description":"FHIR data segmentation for privacy security label implementation guide (built Mon, Apr 17, 2023 19:19+0000+00:00)"},{"name":"hl7.fhir.uv.shorthand.r4","version":"3.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/shorthand","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.shorthand.r4-3.0.0.tgz","date":"2025-10-29T00:22:33.000Z","description":"Describes FHIR Shorthand (FSH), a domain-specific language (DSL) for defining the content of FHIR Implementation Guides (IG). (built Mon, Aug 19, 2024 15:20+0000+00:00)"},{"name":"hl7.fhir.uv.shorthand.r4b","version":"3.0.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/shorthand","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.shorthand.r4b-3.0.0-ballot.tgz","date":"2025-10-29T00:22:33.000Z","description":"Describes FHIR Shorthand (FSH), a domain-specific language (DSL) for defining the content of FHIR Implementation Guides (IG). (built Sun, Jul 30, 2023 19:27+0000+00:00)"},{"name":"hl7.fhir.uv.smart-app-launch.r4","version":"2.2.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/smart-app-launch","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.smart-app-launch.r4-2.2.0.tgz","date":"2025-10-29T00:22:43.000Z"},{"name":"hl7.fhir.uv.smart-app-launch.r4b","version":"2.2.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/smart-app-launch","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.smart-app-launch.r4b-2.2.0.tgz","date":"2025-10-29T00:22:49.000Z"},{"name":"hl7.fhir.uv.smart-health-cards-and-links.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/smart-health-cards-and-links","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.smart-health-cards-and-links.r4-1.0.0.tgz","date":"2025-10-29T00:22:55.000Z","description":"FHIR Implementation Guide for SMART Health Cards and Links (built Tue, Jul 22, 2025 13:19+0000+00:00)"},{"name":"hl7.fhir.uv.smart-health-cards-and-links.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/smart-health-cards-and-links","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.smart-health-cards-and-links.r4b-1.0.0.tgz","date":"2025-10-29T00:22:59.000Z","description":"FHIR Implementation Guide for SMART Health Cards and Links (built Tue, Jul 22, 2025 13:19+0000+00:00)"},{"name":"hl7.fhir.uv.subscriptions-backport.r4","version":"1.2.0-ballot","fhirVersion":"4.0.0","canonical":"http://hl7.org/fhir/uv/subscriptions-backport","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.subscriptions-backport.r4-1.2.0-ballot.tgz","date":"2025-10-29T00:23:19.000Z","description":"The Subscription R5 Backport Implementation Guide enables servers running versions of FHIR earlier than R5 to implement a subset of R5 Subscriptions in a standardized way. (built Mon, Dec 18, 2023 22:14+0000+00:00)"},{"name":"hl7.fhir.uv.subscriptions-backport.r4b","version":"1.2.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/subscriptions-backport","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.subscriptions-backport.r4b-1.2.0-ballot.tgz","date":"2025-10-29T00:23:20.000Z","description":"The Subscription R5 Backport Implementation Guide enables servers running versions of FHIR earlier than R5 to implement a subset of R5 Subscriptions in a standardized way. (built Mon, Dec 18, 2023 22:14+0000+00:00)"},{"name":"hl7.fhir.uv.termchangeset.r4","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/termchangeset","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.termchangeset.r4-1.0.0-ballot.tgz","date":"2025-10-29T00:23:22.000Z","description":"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 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). (built Wed, Aug 14, 2024 14:50+0000+00:00)"},{"name":"hl7.fhir.uv.termchangeset.r4b","version":"1.0.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/termchangeset","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.termchangeset.r4b-1.0.0-ballot.tgz","date":"2025-10-29T00:23:23.000Z","description":"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 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). (built Wed, Aug 14, 2024 14:50+0000+00:00)"},{"name":"hl7.fhir.uv.v2mappings.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/v2mappings","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.v2mappings.r4-1.0.0.tgz","date":"2025-10-29T00:24:06.000Z","description":"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. (built Tue, Oct 7, 2025 19:42+0000+00:00)"},{"name":"hl7.fhir.uv.v2mappings.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/v2mappings","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.v2mappings.r4b-1.0.0.tgz","date":"2025-10-29T00:24:08.000Z","description":"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. (built Tue, Oct 7, 2025 19:42+0000+00:00)"},{"name":"hl7.fhir.uv.vhdir.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/vhdir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.vhdir.r4-1.0.0.tgz","date":"2025-10-29T00:24:14.000Z","description":"This is a Healthedata1 sandbox for creation of resources and examples (built Tue, Feb 18, 2025 15:41+0000+00:00)"},{"name":"hl7.fhir.uv.vhdir.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/vhdir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.vhdir.r4b-1.0.0.tgz","date":"2025-10-29T00:24:16.000Z","description":"This is a Healthedata1 sandbox for creation of resources and examples (built Tue, Feb 18, 2025 15:41+0000+00:00)"},{"name":"hl7.fhir.uv.vulcan-rwd.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/vulcan-rwd","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.vulcan-rwd.r4-1.0.0.tgz","date":"2025-10-29T00:24:24.000Z","description":"A FHIR Implementation Guide that provides profiles and use cases that show how real world data can be exposed in such a way that it can be used for research purposes. (built Fri, May 26, 2023 22:52+1000+10:00)"},{"name":"hl7.fhir.uv.vulcan-rwd.r4b","version":"1.0.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/vulcan-rwd","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.vulcan-rwd.r4b-1.0.0.tgz","date":"2025-10-29T00:24:26.000Z","description":"A FHIR Implementation Guide that provides profiles and use cases that show how real world data can be exposed in such a way that it can be used for research purposes. (built Fri, May 26, 2023 22:52+1000+10:00)"},{"name":"tw.ntunhs.dhcm.fhir.phimr","version":"0.1.0","fhirVersion":"4.0.1","canonical":"https://hitstdio.ntunhs.edu.tw/phimr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/tw.ntunhs.dhcm.fhir.phimr-0.1.0.tgz","date":"2025-10-29T03:29:59.000Z","description":"公共衛生指標測量報告實作指引"},{"name":"hl7.fhir.uv.xver-r4.r4b.r4b","version":"0.0.1-snapshot-2","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/4.0","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r4.r4b.r4b-0.0.1-snapshot-2.tgz","date":"2025-10-30T18:01:41.000Z","description":"The cross-version extensions available in FHIR R4B from FHIR R4 (built Sat, Sep 13, 2025 16:11-0400-04:00)"},{"name":"kl.dk.fhir.ltt","version":"1.0.1","fhirVersion":"4.0.1","canonical":"http://fhir.kl.dk/ltt","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kl.dk.fhir.ltt-1.0.1.tgz","date":"2025-10-31T00:09:10.000Z","description":"LTT provides the specification for reporting selected data on the use of easily accessible services (lettilgængelige tilbud) offered by municipalities for children and youth experiencing mental distress (SUL §126a). Data is reported to FK Gateway (built Wed, Oct 29, 2025 22:39+0100+01:00)"},{"name":"ee.fhir.mpi","version":"1.5.0","fhirVersion":"5.0.0","canonical":"https://fhir.ee/mpi","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ee.fhir.mpi-1.5.0.tgz","date":"2025-10-31T18:09:48.000Z"},{"name":"ca.infoway.io.halo","version":"1.1.1-dft-preballot","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.infoway.io.halo","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.infoway.io.halo-1.1.1-dft-preballot.tgz","date":"2025-10-31T18:35:26.000Z","description":"HALO is a standardized technology framework that enables approved jurisdictional and vendor applications to seamlessly integrate into any authorized Point of Care system."},{"name":"ca.infoway.io.erec","version":"1.2.0-dft","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.infoway.io.erec","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.infoway.io.erec-1.2.0-dft.tgz","date":"2025-10-31T19:33:37.000Z","description":"The CA:eReC iGuide seeks to provide guidance around the messaging paradigm and other patterns related to sending and receiving eReferrals and eConsults."},{"name":"ihe.iti.balp","version":"1.1.4","fhirVersion":"4.0.1","canonical":"https://profiles.ihe.net/ITI/BALP","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.iti.balp-1.1.4.tgz","date":"2025-11-01T00:09:25.000Z","description":"The Basic Audit Log Patterns (BALP) Implementation Guide is a Content Profile that defines some basic and reusable AuditEvent patterns. This includes basic audit log profiles for FHIR RESTful operations to be used when there is not a more specific audit event defined. A focus is enabling Privacy centric AuditEvent logs that hold well formed indication of the Patient when they are the subject of the activity being recorded in the log. Where a more specific audit event can be defined it should be derived off of these basic patterns. (built Fri, Oct 31, 2025 12:53-0500-05:00)"},{"name":"cgm.iop.roche.com","version":"1.0.0","fhirVersion":"5.0.0","canonical":"http://simplifier.net/packages/cgm.iop.roche.com","kind":"fhir.ig","url":"https://packages2.fhir.org/web/cgm.iop.roche.com-1.0.0.tgz","date":"2025-11-02T16:20:27.000Z","description":"Simple project to test the Simplifier capabilities related to model CGM data in FHIR."},{"name":"ee.fhir.base","version":"2.0.0","fhirVersion":"5.0.0","canonical":"https://fhir.ee/base","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ee.fhir.base-2.0.0.tgz","date":"2025-11-05T18:10:19.000Z","description":"Eesti FHIR standardi baas juurutusjuhend (built Wed, Nov 5, 2025 12:10+0000+00:00)"},{"name":"medcom.fhir.dk.carecommunicationtestscripts","version":"5.0.0","fhirVersion":"4.0.1","canonical":"http://medcomfhir.dk/ig/carecommunicationtestscripts","kind":"fhir.ig","url":"https://packages2.fhir.org/web/medcom.fhir.dk.carecommunicationtestscripts-5.0.0.tgz","date":"2025-11-06T12:09:33.000Z","description":"Test scripts for CareCommunication v. 5.0 (built Thu, Nov 6, 2025 10:56+0000+00:00)"},{"name":"de.fhir.terminologie-basis","version":"1.0.0-alpha1","fhirVersion":"4.0.1","canonical":"http://fhir.de","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.fhir.terminologie-basis-1.0.0-alpha1.tgz","date":"2025-11-06T18:09:42.000Z"},{"name":"hl7.eu.fhir.xshare-yb","version":"0.2.0","fhirVersion":"4.0.1","canonical":"http://hl7.eu/fhir/ig/xshare-yb","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.eu.fhir.xshare-yb-0.2.0.tgz","date":"2025-11-06T18:10:27.000Z","description":"This guide documents the xShare Yellow BUtton for the xShare project. (built Wed, Nov 5, 2025 19:20+0100+01:00)"},{"name":"tw.gov.mohw.nhi.ci","version":"1.0.1","fhirVersion":"4.0.1","canonical":"https://nhicore.nhi.gov.tw/ci","kind":"fhir.ig","url":"https://packages2.fhir.org/web/tw.gov.mohw.nhi.ci-1.0.1.tgz","date":"2025-11-07T06:18:41.000Z","description":"臺灣重大傷病實作指引(Taiwan NHI Catastrophic Illness Implementation Guide，TWCI IG) (built Tue, Nov 4, 2025 22:05+0800+08:00)"},{"name":"rl.fhir.r4.draft","version":"0.1.4","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/rl.fhir.r4.draft","kind":"fhir.ig","url":"https://packages2.fhir.org/web/rl.fhir.r4.draft-0.1.4.tgz","date":"2025-11-07T08:35:48.000Z","description":"Progetto FHIR per Regione Lombardia"},{"name":"test.package.dependency.upgrade","version":"3.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/test.package.dependency.upgrade","kind":"fhir.ig","url":"https://packages2.fhir.org/web/test.package.dependency.upgrade-3.0.0.tgz","date":"2025-11-07T10:37:26.000Z","description":"playwright-test-project-quality-control"},{"name":"test.dependency.on.package","version":"2.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/test.dependency.on.package","kind":"fhir.ig","url":"https://packages2.fhir.org/web/test.dependency.on.package-2.0.1.tgz","date":"2025-11-07T10:39:57.000Z","description":"playwright-test-project-quality-control"},{"name":"lean.sa.fhir.core","version":"0.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/lean.sa.fhir.core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/lean.sa.fhir.core-0.0.1.tgz","date":"2025-11-10T16:06:38.000Z","description":"The generic FHIR profiles for Lean FHIR server."},{"name":"his.lw","version":"1.0.2","fhirVersion":"5.0.0","canonical":"http://simplifier.net/packages/his.lw","kind":"fhir.ig","url":"https://packages2.fhir.org/web/his.lw-1.0.2.tgz","date":"2025-11-11T09:27:55.000Z","description":"HIS"},{"name":"kbv.basis","version":"1.8.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/kbv.basis","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kbv.basis-1.8.0.tgz","date":"2025-11-12T10:40:38.000Z","description":"KBV-Basis-Profile V 1.8.0"},{"name":"kbv.basis.terminology","version":"1.8.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/kbv.basis.terminology","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kbv.basis.terminology-1.8.0.tgz","date":"2025-11-12T11:15:38.000Z","description":"KBV-Basis-Profile-Terminologie 1.8.0"},{"name":"uk.nhsdigital.bars.r4","version":"1.37.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/uk.nhsdigital.bars.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/uk.nhsdigital.bars.r4-1.37.0.tgz","date":"2025-11-12T12:10:30.000Z","description":"NHS Booking and Referrals"},{"name":"ca.ab.fhir.ab-eorder-lab","version":"1.0.3","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.ab.fhir.ab-eorder-lab","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.ab.fhir.ab-eorder-lab-1.0.3.tgz","date":"2025-11-13T17:37:01.000Z","description":"Alberta Laboratory eOrder Implementation Guide "},{"name":"fi.kela.kanta.pta.ajanvaraus.r4","version":"1.0.0-rc2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fi.kela.kanta.pta.ajanvaraus.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fi.kela.kanta.pta.ajanvaraus.r4-1.0.0-rc2.tgz","date":"2025-11-14T10:46:41.000Z","description":"Kanta Potilastietovarannon ajanvarauksen FHIR R4 määrittelyt (profiilit, laajennokset, ValueSet:it ja CodeSystem:it). Tämä versio sisältää uudet päivitetyt FHIR-artefaktit."},{"name":"hl7.fhir.us.medication-rems","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/medication-rems","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.medication-rems-2.0.0.tgz","date":"2025-11-18T00:01:14.000Z","description":"FHIR implementation options and guidance for medication REMS participants (built Mon, Nov 17, 2025 20:01+0000+00:00)"},{"name":"ans.fhir.fr.cds","version":"2.0.1","fhirVersion":"4.0.1","canonical":"https://interop.esante.gouv.fr/ig/fhir/cds","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ans.fhir.fr.cds-2.0.1.tgz","date":"2025-11-18T06:09:08.000Z"},{"name":"de.fhir.medication","version":"1.0.3","fhirVersion":"4.0.1","canonical":"http://ig.fhir.de/igs/medication","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.fhir.medication-1.0.3.tgz","date":"2025-11-19T18:10:56.000Z"},{"name":"lt.hl7.fhir.vitalsigns","version":"0.0.1","fhirVersion":"5.0.0","canonical":"https://hl7.lt/fhir/vitalsigns","kind":"fhir.ig","url":"https://packages2.fhir.org/web/lt.hl7.fhir.vitalsigns-0.0.1.tgz","date":"2025-11-19T18:18:39.000Z","description":"Lithuanian Vital Signs Implementation Guide (built Wed, Nov 19, 2025 15:54+0200+02:00)"},{"name":"fi.kela.kanta.gen.r4","version":"1.0.0-rc5","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fi.kela.kanta.gen.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fi.kela.kanta.gen.r4-1.0.0-rc5.tgz","date":"2025-11-20T12:21:33.000Z","description":"Tämä paketti sisältää eri Kanta-palveluissa käytettävät Kanta-yhteiset FHIR R4 artefaktit:\r\n- profiilit (StructereDefinitions)\r\n- laajennukset (StructureDefinitions)\r\n- koodistot (CodeSystem), jotka eivät sijaitse kansallisessa koodistopalvelusta\r\n- arvojoukot (ValueSystem)\r\n\r\n"},{"name":"ca.on.oh.setp.r4","version":"1.0.0-draft1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.oh.setp.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.oh.setp.r4-1.0.0-draft1.tgz","date":"2025-11-20T15:28:59.000Z","description":"Testing Release"},{"name":"fhir.r4.wales","version":"2.4.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.r4.wales","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.r4.wales-2.4.0.tgz","date":"2025-11-20T17:08:21.000Z","description":"NHS Wales Profiles and assets to enable the implementation of Diagnostics, Document Reference, Immunisations and Emergency Care Encounters. "},{"name":"dguv.basis","version":"1.4.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/dguv.basis","kind":"fhir.ig","url":"https://packages2.fhir.org/web/dguv.basis-1.4.0.tgz","date":"2025-11-21T12:02:27.000Z","description":"Die Basisprofile bilden die Grundlage zur Ablösung der bisherigen Formtexte für die Gesetzliche Unfallversicherung."},{"name":"fi.tietohiisi.fhir.testi.r4","version":"0.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fi.tietohiisi.fhir.testi.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fi.tietohiisi.fhir.testi.r4-0.0.1.tgz","date":"2025-11-22T20:22:38.000Z","description":"Testiprojekti testailuja varten"},{"name":"fi.kela.kanta.gen.r4.tahdonilmaisut","version":"1.0.0-rc1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fi.kela.kanta.gen.r4.tahdonilmaisut","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fi.kela.kanta.gen.r4.tahdonilmaisut-1.0.0-rc1.tgz","date":"2025-11-24T07:16:37.000Z","description":"Kanta FHIR tahdonilmaisut, rc1"},{"name":"de.medizininformatikinitiative.kerndatensatz.meta","version":"2026.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.medizininformatikinitiative.kerndatensatz.meta","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.medizininformatikinitiative.kerndatensatz.meta-2026.0.0.tgz","date":"2025-11-24T10:44:17.000Z","description":"Medizininformatik Initiative - Modul Meta"},{"name":"de.j-med.myjmed","version":"0.1.0","fhirVersion":"4.0.1","canonical":"https://fhir.j-med.de","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.j-med.myjmed-0.1.0.tgz","date":"2025-11-24T11:18:56.000Z","description":"FHIR-Profile für die MyJMed-App zur standardisierten Kommunikation zwischen Patient und Praxis "},{"name":"us.nlm.vsac","version":"0.24.0","fhirVersion":"4.0.1","canonical":"http://fhir.org/packages/us.nlm.vsac","kind":"fhir.ig","url":"https://packages2.fhir.org/web/us.nlm.vsac-0.24.0.tgz","date":"2025-11-25T01:16:09.000Z"},{"name":"ans.fhir.fr.sas","version":"1.2.0","fhirVersion":"4.0.1","canonical":"https://interop.esante.gouv.fr/ig/fhir/sas","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ans.fhir.fr.sas-1.2.0.tgz","date":"2025-11-25T06:11:14.000Z"},{"name":"koppeltaalv2.00","version":"0.15.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/koppeltaalv2.00","kind":"fhir.ig","url":"https://packages2.fhir.org/web/koppeltaalv2.00-0.15.0.tgz","date":"2025-11-25T09:13:36.000Z","description":"Draft of used FHIR resource profiles in Koppeltaal 2.0."},{"name":"br.go.ses.monitoramento-avaliacao","version":"1.0.0","fhirVersion":"4.0.1","canonical":"https://fhir.saude.go.gov.br/r4/monitoramento-avaliacao","kind":"fhir.ig","url":"https://packages2.fhir.org/web/br.go.ses.monitoramento-avaliacao-1.0.0.tgz","date":"2025-11-25T18:10:04.000Z","description":"Casos de uso relacionados a Monitoramento e avaliação. (built Tue, Nov 25, 2025 17:45+0000+00:00)"},{"name":"telus.dw.emr.extract","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/telus.dw.emr.extract","kind":"fhir.ig","url":"https://packages2.fhir.org/web/telus.dw.emr.extract-1.0.0.tgz","date":"2025-11-25T19:22:11.000Z","description":"TELUS FHIR4 specification push-only subscription to access EMR chart data"},{"name":"ihe.iti.pdqm","version":"3.2.0","fhirVersion":"4.0.1","canonical":"https://profiles.ihe.net/ITI/PDQm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.iti.pdqm-3.2.0.tgz","date":"2025-11-26T00:10:06.000Z","description":"The Patient Demographics Query for Mobile (PDQm) Profile defines a lightweight RESTful interface to a patient demographics supplier leveraging technologies readily available to mobile applications and lightweight browser based applications. (built Tue, Nov 4, 2025 12:07-0600-06:00)"},{"name":"ihe.iti.pmir","version":"1.6.0","fhirVersion":"4.0.1","canonical":"https://profiles.ihe.net/ITI/PMIR","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.iti.pmir-1.6.0.tgz","date":"2025-11-26T00:10:07.000Z","description":"The Patient Master Identity Registry (PMIR) Profile supports the creating, updating and deprecating of patient master identity information about a subject of care, as well as subscribing to changes to the patient master identity, using the HL7 FHIR standard resources and RESTful transactions. (built Tue, Nov 4, 2025 15:17-0600-06:00)"},{"name":"ihe.iti.pixm","version":"3.1.0","fhirVersion":"4.0.1","canonical":"https://profiles.ihe.net/ITI/PIXm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.iti.pixm-3.1.0.tgz","date":"2025-11-26T00:10:07.000Z","description":"ImplementationGuide for IHE IT Infrastructure Technical Framework Supplement Patient Identifier Cross-referencing for mobile (PIXm) (built Tue, Nov 4, 2025 14:14-0600-06:00)"},{"name":"dguv.enla","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/dguv.enla","kind":"fhir.ig","url":"https://packages2.fhir.org/web/dguv.enla-1.0.0.tgz","date":"2025-11-26T09:48:06.000Z","description":"Entlassungsbericht aus stationärer Behandlung (F 2102)\r\n\r\nDer Entlassungsbericht aus stationärer Behandlung der DGUV (F2102) ist ein spezifischer Bericht, der im Rahmen der stationären Behandlung infolge eines Arbeits- oder Wegeunfalls oder einer Berufskrankheit erstellt wird. Er enthält Informationen über Diagnosen, Behandlungen, Medikamente und Therapien, die während des Krankenhausaufenthaltes durchgeführt wurden, sowie Empfehlungen für die weitere Versorgung, z. B. zur Rehabilitation oder ambulanten Nachsorge.\r\nDarüber hinaus werden Angaben zur Art und Schwere des Unfalls oder der Erkrankung sowie zu potenziell arbeitsbedingten Einflussfaktoren gemacht.\r\nDer Bericht wird von der behandelnden Klinik an die zuständige Berufsgenossenschaft oder Unfallkasse sowie an die weiterbehandelnden Ärztinnen und Ärzte und die Patientinnen und Patienten übermittelt und bildet eine wichtige Grundlage für die weitere Versorgung und Rehabilitation.\r\n"},{"name":"flc.fhir.base","version":"0.2.4","fhirVersion":"4.0.1","canonical":"http://canonical.fhir.link/flc/base","kind":"fhir.ig","url":"https://packages2.fhir.org/web/flc.fhir.base-0.2.4.tgz","date":"2025-11-26T12:23:35.000Z","description":"Implementation Guide for FLC made by Service Well (built Wed, Nov 26, 2025 09:01+0000+00:00)"},{"name":"br.go.ses.core","version":"1.1.0","fhirVersion":"4.0.1","canonical":"https://fhir.saude.go.gov.br/r4/core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/br.go.ses.core-1.1.0.tgz","date":"2025-11-26T18:12:07.000Z","description":"Guia de Implementação da SES GO - CORE (built Wed, Nov 26, 2025 13:07+0000+00:00)"},{"name":"fi.tietohiisi.r4","version":"0.1.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fi.tietohiisi.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fi.tietohiisi.r4-0.1.0.tgz","date":"2025-11-27T20:52:47.000Z","description":"Test project for Tietohiisi 2025 profiling training"},{"name":"hl7.fhir.cr.terminology","version":"0.0.1-ballot","fhirVersion":"5.0.0","canonical":"https://hl7.or.cr/fhir/terminology","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.cr.terminology-0.0.1-ballot.tgz","date":"2025-11-29T14:19:09.000Z","description":"Esta guía de implementación define los recursos de terminología FHIR utilizados por la Iniciativa HL7 Costa Rica. (built Tue, Nov 25, 2025 20:19-0600-06:00)"},{"name":"fhir.halaxy","version":"0.1.1","fhirVersion":"4.0.1","canonical":"https://terminology.halaxy.com/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.halaxy-0.1.1.tgz","date":"2025-12-01T05:49:45.000Z","description":"Test Halaxy IG"},{"name":"kbv.ita.vos","version":"2.2.0-kommentierung2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/kbv.ita.vos","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kbv.ita.vos-2.2.0-kommentierung2.tgz","date":"2025-12-01T10:57:36.000Z","description":"Verordnungssoftware-Schnittstelle gemäß § 371 Absatz 1 SGB V"},{"name":"hl7.fhir.be.drp","version":"1.0.0","fhirVersion":"4.0.1","canonical":"https://www.ehealth.fgov.be/standards/fhir/drp","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.be.drp-1.0.0.tgz","date":"2025-12-01T12:10:36.000Z","description":"Digital Referral Prescription Implementation Guide (built Fri, Oct 10, 2025 14:07+0200+02:00)"},{"name":"hl7.fhir.be.medication","version":"1.1.0","fhirVersion":"4.0.1","canonical":"https://www.ehealth.fgov.be/standards/fhir/medication","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.be.medication-1.1.0.tgz","date":"2025-12-01T12:10:37.000Z","description":"FHIR Medication specifications (built Fri, Oct 10, 2025 13:23+0200+02:00)"},{"name":"hl7.fhir.be.patient-care","version":"1.1.0","fhirVersion":"4.0.1","canonical":"https://www.ehealth.fgov.be/standards/fhir/patient-care","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.be.patient-care-1.1.0.tgz","date":"2025-12-01T12:10:39.000Z","description":"Belgian Patient care profiles (built Fri, Oct 10, 2025 14:02+0200+02:00)"},{"name":"hl7.fhir.be.vaccination","version":"1.1.2","fhirVersion":"4.0.1","canonical":"https://www.ehealth.fgov.be/standards/fhir/vaccination","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.be.vaccination-1.1.2.tgz","date":"2025-12-01T12:10:42.000Z","description":"Belgian Patient profiles (built Thu, Nov 27, 2025 15:12+0100+01:00)"},{"name":"ltsi.fhir.oncofair","version":"0.1.0","fhirVersion":"5.0.0","canonical":"http://oncofair-ig.kereval.cloud","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ltsi.fhir.oncofair-0.1.0.tgz","date":"2025-12-01T12:19:46.000Z","description":"The OncoFAIR implementation guide reports on the implementation of prescribing and medication administration in oncology. (built Mon, Nov 17, 2025 13:40+0100+01:00)"},{"name":"de.gematik.isik-basismodul","version":"3.1.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gematik.isik-basismodul","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.isik-basismodul-3.1.1.tgz","date":"2025-12-01T13:50:23.000Z","description":"Technical Correction"},{"name":"de.gematik.isik-vitalparameter","version":"3.1.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gematik.isik-vitalparameter","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.isik-vitalparameter-3.1.1.tgz","date":"2025-12-01T15:05:07.000Z","description":"Technical Correction Package Release des ISiK Modul Vitalparameter"},{"name":"de.gematik.isik-medikation","version":"3.1.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gematik.isik-medikation","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.isik-medikation-3.1.1.tgz","date":"2025-12-01T15:17:43.000Z","description":"Medikations-Modul der Informationstechnischen Systeme im Krankenhaus Ausbaustufe 4"},{"name":"de.gematik.isik-dokumentenaustausch","version":"3.1.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gematik.isik-dokumentenaustausch","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.isik-dokumentenaustausch-3.1.1.tgz","date":"2025-12-01T15:40:23.000Z","description":"Technical Correction - Dokumentenaustausch-Modul der Informationstechnischen Systeme im Krankenhaus Ausbaustufe 3"},{"name":"de.gematik.isik-terminplanung","version":"3.1.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gematik.isik-terminplanung","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.isik-terminplanung-3.1.1.tgz","date":"2025-12-01T16:07:26.000Z","description":"Technical Correction - Package Release des ISiK Modul Terminplanung"},{"name":"navify.fhir.r5.rdc","version":"1.2.2","fhirVersion":"5.0.0","canonical":"http://simplifier.net/packages/navify.fhir.r5.rdc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/navify.fhir.r5.rdc-1.2.2.tgz","date":"2025-12-03T09:17:44.000Z","description":"RDC R5 Interoperability Guide"},{"name":"medcom.fhir.dk.terminology","version":"2.0.2","fhirVersion":"4.0.1","canonical":"http://medcomfhir.dk/ig/terminology","kind":"fhir.ig","url":"https://packages2.fhir.org/web/medcom.fhir.dk.terminology-2.0.2.tgz","date":"2025-12-03T12:12:26.000Z","description":"This IG includes CodeSystems, ValueSets and ConceptMaps defined by MedCom and used in MedCom's FHIR standards. (built Wed, Dec 3, 2025 07:54+0000+00:00)"},{"name":"br.go.ses.medicamentos","version":"1.1.0","fhirVersion":"4.0.1","canonical":"https://fhir.saude.go.gov.br/r4/medicamentos","kind":"fhir.ig","url":"https://packages2.fhir.org/web/br.go.ses.medicamentos-1.1.0.tgz","date":"2025-12-03T18:11:34.000Z","description":"Casos de uso relacionados a medicamentos. (built Wed, Dec 3, 2025 16:42+0000+00:00)"},{"name":"rapport.endoscopie.quebec","version":"0.9.0-beta9c","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/rapport.endoscopie.quebec","kind":"fhir.ig","url":"https://packages2.fhir.org/web/rapport.endoscopie.quebec-0.9.0-beta9c.tgz","date":"2025-12-04T14:34:36.000Z","description":"Envoi du rapport d’endoscopie au dépôt provincial"},{"name":"nictiz.fhir.nl.r4.immunization","version":"2.1.0-alpha.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/nictiz.fhir.nl.r4.immunization","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nictiz.fhir.nl.r4.immunization-2.1.0-alpha.1.tgz","date":"2025-12-05T11:27:16.000Z","description":"Nictiz NL package of FHIR R4 conformance resources for Immunization."},{"name":"hl7.fhir.cl.minsal.nid","version":"0.4.9","fhirVersion":"4.0.1","canonical":"https://interoperabilidad.minsal.cl/fhir/ig/nid","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.cl.minsal.nid-0.4.9.tgz","date":"2025-12-05T18:14:56.000Z","description":"Núcleo de Interoperabilidad de Datos del Ministerio de Salud de Chile (built Fri, Dec 5, 2025 14:30-0300-03:00)"},{"name":"hl7.fhir.us.davinci-vbpr","version":"1.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-vbpr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-vbpr-1.1.0.tgz","date":"2025-12-09T00:01:08.000Z","description":"The Da Vinci Fast Healthcare Interoperability Resource (FHIR) Value-Based Performance Reporting Implementation Guide (this IG) specifies standard representations of value-based performance reports that are exchanged payers and providers, which include performance metrics on financial, utilization, etc. and quality measures for varies types of value-based contracts. (built Mon, Dec 8, 2025 20:55+0000+00:00)"},{"name":"ca.infoway.io.ca-csd","version":"1.1.2-dft-preBallot","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.infoway.io.ca-csd","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.infoway.io.ca-csd-1.1.2-dft-preBallot.tgz","date":"2025-12-09T17:49:40.000Z","description":"This Pan-Canadian Healthcare Service Directory (CA-CSD) is based on IHE mCSD version 4.0.0. "},{"name":"hl7.fhir.us.udap-security","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/udap-security","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.udap-security-2.0.0.tgz","date":"2025-12-10T00:01:11.000Z","description":"This implementation guide describes how to extend OAuth 2.0 to support secure and scalable workflows for business-to-business (B2B) apps that implement the client credentials flow or authorization code flow. (built Tue, Dec 9, 2025 21:26+0000+00:00)"},{"name":"hl7.fhir.uv.aitransparency","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/aitransparency","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.aitransparency-1.0.0-ballot.tgz","date":"2025-12-10T00:01:12.000Z","description":"Provides guidance for representing the usage of AI in influencing FHIR resources. Starting with how to tag FHIR resources, and expanding into how to use Provenance, Device, and other data elements, this FHIR IG provides standards that enable downstream use cases to identify such resources. This allows the informed usage of AI-inferred health data. (built Tue, Dec 9, 2025 18:35+0000+00:00)"},{"name":"kbv.itv.evdga","version":"1.2.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/kbv.itv.evdga","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kbv.itv.evdga-1.2.2.tgz","date":"2025-12-10T14:50:43.000Z","description":"Der Gesetzgeber hat im Zuge des „Gesetzes für eine bessere Versorgung durch Digitalisierung und Innovation“ im Rahmen des § 33a SGB V festgelegt, dass Versicherte einen Leistungsanspruch auf Versorgung mit digitalen Gesundheitsanwendungen haben, welche Medizinprodukte niedriger Risikoklasse darstellen, deren Hauptfunktion wesentlich auf digitalen Technologien beruht und die dazu bestimmt sind, bei den Versicherten oder in der Versorgung durch Leistungserbringer die Erkennung, Überwachung, Behandlung oder Linderung von Krankheiten oder die Erkennung, Behandlung, Linderung oder Kompensierung von Verletzungen oder Behinderungen zu unterstützen. Damit wurde der Kreis der auch digital verordnungsfähigen Produkte und Leistungen gemäß § 86 SGB V Abs. 1 Satz 1 Nummer 2 auf digitale Gesundheitsanwendungen erweitert. \r\n\r\nWeitere technischen Vorgaben zur Verwendung der Profile finden sich unter https://update.kbv.de/ita-update/DigitaleMuster/eVDGA/ in dem Dokument [KBV_ITA_VGEX_Technische_Anlage_eVDGA]."},{"name":"de.medizininformatikinitiative.kerndatensatz.kardiologie","version":"2026.0.0-alpha.2","fhirVersion":"4.0.1","canonical":"https://www.medizininformatik-initiative.de/fhir/ext/modul-kardio/","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.medizininformatikinitiative.kerndatensatz.kardiologie-2026.0.0-alpha.2.tgz","date":"2025-12-10T14:51:36.000Z","description":"MII - Erweiterungsmodul Kardiologie 2026.0.0-alpha.2 - Umsetzungsphase 1"},{"name":"kbv.ita.eau","version":"1.2.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/kbv.ita.eau","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kbv.ita.eau-1.2.1.tgz","date":"2025-12-10T15:09:25.000Z","description":"Umsetzung der elektronischen Arbeitsunfähigkeit"},{"name":"hl7.fhir.us.identity-matching","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/identity-matching","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.identity-matching-2.0.0.tgz","date":"2025-12-10T18:01:03.000Z"},{"name":"br.go.ses.exame","version":"1.0.0","fhirVersion":"4.0.1","canonical":"https://fhir.saude.go.gov.br/r4/exame","kind":"fhir.ig","url":"https://packages2.fhir.org/web/br.go.ses.exame-1.0.0.tgz","date":"2025-12-11T00:11:31.000Z","description":"Detalhes de uso do FHIR para transferência de resultados de exames laboratoriais (built Wed, Dec 10, 2025 20:33+0000+00:00)"},{"name":"br.go.ses.saude-mulher","version":"1.0.0","fhirVersion":"4.0.1","canonical":"https://fhir.saude.go.gov.br/r4/saude-mulher","kind":"fhir.ig","url":"https://packages2.fhir.org/web/br.go.ses.saude-mulher-1.0.0.tgz","date":"2025-12-11T06:12:52.000Z","description":"Casos de uso relacionados a saúde da mulher. (built Thu, Dec 11, 2025 00:56+0000+00:00)"},{"name":"hl7.fhir.uv.bulkdata","version":"3.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/bulkdata","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.bulkdata-3.0.0.tgz","date":"2025-12-11T12:01:12.000Z","description":"FHIR based approach for exporting large data sets from a FHIR server to a client application (built Thu, Dec 11, 2025 13:43+0800+08:00)"},{"name":"hl7.fhir.uv.vulcan-schedule.r4","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/vulcan-schedule","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.vulcan-schedule.r4-1.0.0-ballot.tgz","date":"2025-12-11T12:01:21.000Z","description":"FHIR Implementation Guide representing a Clinical Study Schedule of Activites (built Sun, Dec 4, 2022 20:06+0000+00:00)"},{"name":"hl7.fhir.uv.vulcan-schedule.r4b","version":"1.0.0-ballot","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/vulcan-schedule","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.vulcan-schedule.r4b-1.0.0-ballot.tgz","date":"2025-12-11T12:01:21.000Z","description":"FHIR Implementation Guide representing a Clinical Study Schedule of Activites (built Sun, Dec 4, 2022 20:06+0000+00:00)"},{"name":"hl7.fhir.uv.xver-r2.r4.r4","version":"0.0.1-snapshot-2","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/1.0","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r2.r4.r4-0.0.1-snapshot-2.tgz","date":"2025-12-11T12:01:25.000Z","description":"The cross-version extensions available in FHIR R4 from FHIR R2 (built Sat, Sep 13, 2025 15:01-0400-04:00)"},{"name":"hl7.fhir.uv.xver-r2.r4.r4b","version":"0.0.1-snapshot-2","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/1.0","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r2.r4.r4b-0.0.1-snapshot-2.tgz","date":"2025-12-11T12:01:26.000Z","description":"The cross-version extensions available in FHIR R4 from FHIR R2 (built Sat, Sep 13, 2025 15:01-0400-04:00)"},{"name":"ch.fhir.ig.ch-ig","version":"1.2.3","fhirVersion":"4.0.1","canonical":"http://fhir.ch/ig/ch-ig","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ch.fhir.ig.ch-ig-1.2.3.tgz","date":"2025-12-11T12:02:56.000Z","description":"Template for HL7.ch FHIR Implementation Guides (built Thu, Dec 11, 2025 10:29+0000+00:00)"},{"name":"hl7.fhir.uv.xver-r2.r4b.r4","version":"0.0.1-snapshot-2","fhirVersion":"4.0.0","canonical":"http://hl7.org/fhir/1.0","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r2.r4b.r4-0.0.1-snapshot-2.tgz","date":"2025-12-11T18:01:17.000Z","description":"The cross-version extensions available in FHIR R4B from FHIR R2 (built Sat, Sep 13, 2025 15:10-0400-04:00)"},{"name":"hl7.fhir.uv.xver-r2.r4b.r4b","version":"0.0.1-snapshot-2","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/1.0","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r2.r4b.r4b-0.0.1-snapshot-2.tgz","date":"2025-12-11T18:01:18.000Z","description":"The cross-version extensions available in FHIR R4B from FHIR R2 (built Sat, Sep 13, 2025 15:10-0400-04:00)"},{"name":"hl7.fhir.uv.xver-r3.r4.r4","version":"0.0.1-snapshot-2","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/3.0","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r3.r4.r4-0.0.1-snapshot-2.tgz","date":"2025-12-11T18:01:20.000Z","description":"The cross-version extensions available in FHIR R4 from FHIR R3 (built Sat, Sep 13, 2025 15:32-0400-04:00)"},{"name":"hl7.fhir.uv.xver-r3.r4.r4b","version":"0.0.1-snapshot-2","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/3.0","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r3.r4.r4b-0.0.1-snapshot-2.tgz","date":"2025-12-11T18:01:20.000Z","description":"The cross-version extensions available in FHIR R4 from FHIR R3 (built Sat, Sep 13, 2025 15:32-0400-04:00)"},{"name":"hl7.fhir.uv.xver-r3.r4b.r4","version":"0.0.1-snapshot-2","fhirVersion":"4.0.0","canonical":"http://hl7.org/fhir/3.0","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r3.r4b.r4-0.0.1-snapshot-2.tgz","date":"2025-12-11T18:01:22.000Z","description":"The cross-version extensions available in FHIR R4B from FHIR R3 (built Sat, Sep 13, 2025 15:45-0400-04:00)"},{"name":"hl7.fhir.uv.xver-r3.r4b.r4b","version":"0.0.1-snapshot-2","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/3.0","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r3.r4b.r4b-0.0.1-snapshot-2.tgz","date":"2025-12-11T18:01:22.000Z","description":"The cross-version extensions available in FHIR R4B from FHIR R3 (built Sat, Sep 13, 2025 15:45-0400-04:00)"},{"name":"hl7.fhir.uv.xver-r4.r4b.r4","version":"0.0.1-snapshot-2","fhirVersion":"4.0.0","canonical":"http://hl7.org/fhir/4.0","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r4.r4b.r4-0.0.1-snapshot-2.tgz","date":"2025-12-11T18:01:28.000Z","description":"The cross-version extensions available in FHIR R4B from FHIR R4 (built Sat, Sep 13, 2025 16:11-0400-04:00)"},{"name":"ch.fhir.ig.ch-epl","version":"1.0.0","fhirVersion":"5.0.0","canonical":"http://fhir.ch/ig/ch-epl","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ch.fhir.ig.ch-epl-1.0.0.tgz","date":"2025-12-11T18:02:45.000Z","description":"Implementation Guide CH EPL (R5) (built Thu, Dec 11, 2025 12:29+0000+00:00)"},{"name":"hl7.fhir.uv.xver-r4b.r4.r4","version":"0.0.1-snapshot-2","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/4.3","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r4b.r4.r4-0.0.1-snapshot-2.tgz","date":"2025-12-12T00:01:19.000Z","description":"The cross-version extensions available in FHIR R4 from FHIR R4B (built Sat, Sep 13, 2025 16:38-0400-04:00)"},{"name":"hl7.fhir.uv.xver-r4b.r4.r4b","version":"0.0.1-snapshot-2","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/4.3","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r4b.r4.r4b-0.0.1-snapshot-2.tgz","date":"2025-12-12T00:01:19.000Z","description":"The cross-version extensions available in FHIR R4 from FHIR R4B (built Sat, Sep 13, 2025 16:38-0400-04:00)"},{"name":"hl7.fhir.uv.xver-r5.r4.r4","version":"0.0.1-snapshot-2","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/5.0","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r5.r4.r4-0.0.1-snapshot-2.tgz","date":"2025-12-12T00:01:24.000Z","description":"The cross-version extensions available in FHIR R4 from FHIR R5 (built Sat, Sep 13, 2025 16:55-0400-04:00)"},{"name":"hl7.fhir.uv.xver-r5.r4.r4b","version":"0.0.1-snapshot-2","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/5.0","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r5.r4.r4b-0.0.1-snapshot-2.tgz","date":"2025-12-12T00:01:26.000Z","description":"The cross-version extensions available in FHIR R4 from FHIR R5 (built Sat, Sep 13, 2025 16:55-0400-04:00)"},{"name":"hl7.fhir.us.core","version":"9.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.core-9.0.0-ballot.tgz","date":"2025-12-12T06:01:08.000Z","description":"The US Core Implementation Guide is based on FHIR Version R4 and defines the minimum conformance requirements for accessing patient data. The Argonaut pilot implementations, ONC 2015 Edition Common Clinical Data Set (CCDS), and ONC U.S. Core Data for Interoperability (USCDI) v1 provided the requirements for this guide. The prior Argonaut search and vocabulary requirements, based on FHIR DSTU2, are updated in this guide to support FHIR Version R4. This guide was used as the basis for further testing and guidance by the Argonaut Project Team to provide additional content and guidance specific to Data Query Access for purpose of ONC Certification testing. These profiles are the foundation for future US Realm FHIR implementation guides. In addition to Argonaut, they are used by DAF-Research, QI-Core, and CIMI. Under the guidance of HL7 and the HL7 US Realm Steering Committee, the content will expand in future versions to meet the needs specific to the US Realm.\nThese requirements were originally developed, balloted, and published in FHIR DSTU2 as part of the Office of the National Coordinator for Health Information Technology (ONC) sponsored Data Access Framework (DAF) project. For more information on how DAF became US Core see the US Core change notes. (built Thu, Dec 11, 2025 21:15+0000+00:00)"},{"name":"hl7.cda.uv.core","version":"2.0.2-sd","fhirVersion":"5.0.0","canonical":"http://hl7.org/cda/stds/core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.cda.uv.core-2.0.2-sd.tgz","date":"2025-12-12T06:01:27.000Z"},{"name":"fi.kela.kanta.kvp.r4","version":"1.0.0-rc3","fhirVersion":"4.0.1","canonical":"https://kvp.kanta.fi/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fi.kela.kanta.kvp.r4-1.0.0-rc3.tgz","date":"2025-12-12T12:48:48.000Z","description":"Kanta Kysely- ja välityspalvelun FHIR R4 määrittelyt (profiilit, laajennokset, ValueSet:it ja CodeSystem:it)"},{"name":"acme.tulipcare","version":"0.0.1-alpha","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/acme.tulipcare","kind":"fhir.ig","url":"https://packages2.fhir.org/web/acme.tulipcare-0.0.1-alpha.tgz","date":"2025-12-12T14:44:07.000Z","description":"A FSH-based Implementation Guide for handling valuable flowers"},{"name":"nictiz.fhir.nl.r4.zib2020","version":"0.12.0-labtrial.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/nictiz.fhir.nl.r4.zib2020","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nictiz.fhir.nl.r4.zib2020-0.12.0-labtrial.1.tgz","date":"2025-12-12T15:44:31.000Z","description":"NL package of FHIR R4 conformance resources for zib (Zorginformatiebouwstenen, Clinical Information Models) release 2020."},{"name":"nictiz.fhir.nl.r4.nl-core","version":"0.12.0-labtrial.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/nictiz.fhir.nl.r4.nl-core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nictiz.fhir.nl.r4.nl-core-0.12.0-labtrial.1.tgz","date":"2025-12-12T15:46:41.000Z","description":"NL package of FHIR R4 conformance resources for zib (Zorginformatiebouwstenen, Clinical Information Models) release 2020."},{"name":"hl7.fhir.us.ecr","version":"3.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/ecr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.ecr-3.0.0-ballot.tgz","date":"2025-12-12T18:01:04.000Z","description":"The Electronic Case Reporting (eCR) FHIR IG specifies a standard for the creation of an Electronic Initial Case Report (eICR), A Reportability Response (RR), and includes the electronic Reporting and Surveillance Distribution (eRSD). (built Fri, Dec 12, 2025 16:22+0000+00:00)"},{"name":"br.go.ses.imunizacao","version":"1.0.0","fhirVersion":"4.0.1","canonical":"https://fhir.saude.go.gov.br/r4/imunizacao","kind":"fhir.ig","url":"https://packages2.fhir.org/web/br.go.ses.imunizacao-1.0.0.tgz","date":"2025-12-12T18:03:06.000Z","description":"Casos de uso relacionados a imunização. (built Fri, Dec 12, 2025 17:17+0000+00:00)"},{"name":"hl7.fhir.us.sdoh-clinicalcare","version":"3.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/sdoh-clinicalcare","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.sdoh-clinicalcare-3.0.0-ballot.tgz","date":"2025-12-13T18:01:05.000Z","description":"This HL7 Implementation Guide (IG) defines how to exchange Social Determinants of Health (SDOH) content defined by the Gravity Project using the HL7 FHIR standard.. (built Sat, Dec 13, 2025 17:11+0000+00:00)"},{"name":"de.medizininformatikinitiative.kerndatensatz.base","version":"2026.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.medizininformatikinitiative.kerndatensatz.base","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.medizininformatikinitiative.kerndatensatz.base-2026.0.0.tgz","date":"2025-12-13T18:39:08.000Z","description":"Basismodule Person, Diagnose, Prozedur, Fall v2026+"},{"name":"hl7.cda.us.ccda","version":"5.0.0-ballot","fhirVersion":"5.0.0","canonical":"http://hl7.org/cda/us/ccda","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.cda.us.ccda-5.0.0-ballot.tgz","date":"2025-12-14T00:01:24.000Z"},{"name":"stb.combined","version":"1.68.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/stb.combined","kind":"fhir.ig","url":"https://packages2.fhir.org/web/stb.combined-1.68.0.tgz","date":"2025-12-15T07:05:56.000Z","description":"KBV Schluesseltabellen"},{"name":"ch.fhir.ig.ch-term","version":"3.3.0","fhirVersion":"4.0.1","canonical":"http://fhir.ch/ig/ch-term","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ch.fhir.ig.ch-term-3.3.0.tgz","date":"2025-12-15T12:02:34.000Z","description":"Implementation Guide for Swiss Terminology (built Mon, Dec 15, 2025 10:36+0000+00:00)"},{"name":"dk.ehmi.eds","version":"1.0.2","fhirVersion":"4.0.1","canonical":"http://medcomehmi.dk/ig/eds","kind":"fhir.ig","url":"https://packages2.fhir.org/web/dk.ehmi.eds-1.0.2.tgz","date":"2025-12-15T12:02:51.000Z","description":"The DK EHMI Delivery Status (EDS) (built Thu, Dec 11, 2025 14:37+0000+00:00)"},{"name":"hl7.fhir.us.central-cancer-registry-reporting","version":"2.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/central-cancer-registry-reporting","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.central-cancer-registry-reporting-2.0.0-ballot.tgz","date":"2025-12-15T18:01:06.000Z","description":"The Central Cancer Registry Reporting Content IG provides healthcare organizations the necessary data exchange mechanisms to report cancer data to public health agencies. (built Mon, Dec 15, 2025 16:01+0000+00:00)"},{"name":"hl7.fhir.uv.phenomics-exchange","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/phenomics-exchange","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.phenomics-exchange-1.0.0-ballot.tgz","date":"2025-12-15T18:01:19.000Z","description":"Phenomics Exchange for Research and Diagnostics (built Mon, Dec 15, 2025 17:09+0000+00:00)"},{"name":"hl7.fhir.uv.cds-hooks","version":"3.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://cds-hooks.hl7.org","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.cds-hooks-3.0.0-ballot.tgz","date":"2025-12-15T18:01:34.000Z","description":"CDS Hooks describes a \"hook\"-based pattern for invoking decision support from within a clinician's workflow. (built Mon, Dec 15, 2025 23:02+1100+11:00)"},{"name":"hl7.fhir.us.consent-management","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/consent-management","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.consent-management-1.0.0-ballot.tgz","date":"2025-12-16T00:01:02.000Z","description":"A FHIR IG that provides APIs for managing consent at scale across multiple consent management repositories. (built Mon, Dec 15, 2025 21:10+0000+00:00)"},{"name":"ans.fhir.fr.sdo","version":"4.0.6","fhirVersion":"4.0.1","canonical":"https://interop.esante.gouv.fr/ig/fhir/sdo","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ans.fhir.fr.sdo-4.0.6.tgz","date":"2025-12-16T06:02:44.000Z"},{"name":"de.gematik.terminology","version":"1.0.8","fhirVersion":"4.0.1","canonical":"https://gematik.de/fhir/terminology","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.terminology-1.0.8.tgz","date":"2025-12-16T08:57:06.000Z","description":"Terminologies for Telematics Infrastructure (TI)"},{"name":"de.gematik.ti","version":"1.2.0","fhirVersion":"4.0.1","canonical":"https://gematik.de/fhir/ti","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.ti-1.2.0.tgz","date":"2025-12-16T09:01:58.000Z","description":"Telematikinfrastruktur (TI) Common"},{"name":"de.gematik.epa","version":"1.3.0","fhirVersion":"4.0.1","canonical":"https://gematik.de/fhir/epa","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.epa-1.3.0.tgz","date":"2025-12-16T09:08:54.000Z","description":"ePA Basisfunktionalitäten"},{"name":"de.gematik.epa.medication","version":"1.3.0","fhirVersion":"4.0.1","canonical":"https://gematik.de/fhir/epa-medication","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.epa.medication-1.3.0.tgz","date":"2025-12-16T09:21:59.000Z","description":"ePA Medication"},{"name":"uk.nhsdigital.r4.test","version":"2.18.12-prerelease","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/uk.nhsdigital.r4.test","kind":"fhir.ig","url":"https://packages2.fhir.org/web/uk.nhsdigital.r4.test-2.18.12-prerelease.tgz","date":"2025-12-16T11:54:49.000Z","description":"NHS (England) National Services Implementation Guide"},{"name":"ch.fhir.ig.ch-core","version":"6.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.ch/ig/ch-core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ch.fhir.ig.ch-core-6.0.0.tgz","date":"2025-12-16T12:02:48.000Z","description":"FHIR implementation guide CH Core (built Tue, Dec 16, 2025 07:58+0000+00:00)"},{"name":"ch.fhir.ig.ch-lab-order","version":"3.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.ch/ig/ch-lab-order","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ch.fhir.ig.ch-lab-order-3.0.0.tgz","date":"2025-12-16T12:02:49.000Z","description":"Implementation guide CH CH LAB-Order (R4) (built Tue, Dec 16, 2025 11:34+0000+00:00)"},{"name":"ch.fhir.ig.ch-emed","version":"6.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.ch/ig/ch-emed","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ch.fhir.ig.ch-emed-6.0.0.tgz","date":"2025-12-16T12:02:49.000Z","description":"Implementation Guide for the eMedication in Switzerland. (built Tue, Dec 16, 2025 11:07+0000+00:00)"},{"name":"ch.fhir.ig.ch-lab-report","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.ch/ig/ch-lab-report","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ch.fhir.ig.ch-lab-report-2.0.0.tgz","date":"2025-12-16T12:02:50.000Z","description":"FHIR® Implementation Guide for Laboratory Reports in Switzerland (built Tue, Dec 16, 2025 10:27+0000+00:00)"},{"name":"ch.fhir.ig.ch-orf","version":"3.0.2","fhirVersion":"4.0.1","canonical":"http://fhir.ch/ig/ch-orf","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ch.fhir.ig.ch-orf-3.0.2.tgz","date":"2025-12-16T12:02:51.000Z","description":"Order & Referral by Form - Implementation Guide (CH ORF) (built Tue, Dec 16, 2025 09:33+0000+00:00)"},{"name":"ch.fhir.ig.ch-vacd","version":"6.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.ch/ig/ch-vacd","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ch.fhir.ig.ch-vacd-6.0.0.tgz","date":"2025-12-16T12:02:52.000Z"},{"name":"ch.fhir.ig.ch-allergyintolerance","version":"3.0.1","fhirVersion":"4.0.1","canonical":"http://fhir.ch/ig/ch-allergyintolerance","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ch.fhir.ig.ch-allergyintolerance-3.0.1.tgz","date":"2025-12-16T18:02:45.000Z","description":"Implementation guide CH AllergyIntolerance (R4) (built Tue, Dec 16, 2025 16:28+0000+00:00)"},{"name":"ch.fhir.ig.ch-etoc","version":"3.0.1","fhirVersion":"4.0.1","canonical":"http://fhir.ch/ig/ch-etoc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ch.fhir.ig.ch-etoc-3.0.1.tgz","date":"2025-12-16T18:02:46.000Z","description":"Implementation guide for eTOC based on CH ORF (built Tue, Dec 16, 2025 15:53+0000+00:00)"},{"name":"ch.fhir.ig.ch-epreg","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.ch/ig/ch-epreg","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ch.fhir.ig.ch-epreg-1.0.0.tgz","date":"2025-12-16T18:02:46.000Z","description":"FHIR implementation guide for the pregnancy passport in Switzerland. (built Tue, Dec 16, 2025 12:16+0000+00:00)"},{"name":"ch.fhir.ig.ch-ips","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.ch/ig/ch-ips","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ch.fhir.ig.ch-ips-2.0.0.tgz","date":"2025-12-16T18:02:47.000Z","description":"The FHIR implementation guide CH IPS is derived from the Swiss Core IG (CH Core) and ensures conformity with the International Patient Summary (IPS). (built Tue, Dec 16, 2025 11:58+0000+00:00)"},{"name":"openehr.base","version":"0.1.0-snapshot","fhirVersion":"5.0.0","canonical":"http://openehr.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/openehr.base-0.1.0-snapshot.tgz","date":"2025-12-17T00:01:33.000Z","description":"This IG defines the base openEHR Reference model in order to support validation and publication of openEHR archetypes in the FHIR framework (built Wed, Dec 17, 2025 07:04+1100+11:00)"},{"name":"tw.gov.mohw.twcore","version":"1.0.0","fhirVersion":"4.0.1","canonical":"https://twcore.mohw.gov.tw/ig/twcore","kind":"fhir.ig","url":"https://packages2.fhir.org/web/tw.gov.mohw.twcore-1.0.0.tgz","date":"2025-12-17T06:03:21.000Z","description":"臺灣核心實作指引(TW Core IG) (built Wed, Dec 10, 2025 08:57+0000+00:00)"},{"name":"fi.kela.kanta.gen.r4.toimintakyky","version":"1.0.0-rc4","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fi.kela.kanta.gen.r4.toimintakyky","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fi.kela.kanta.gen.r4.toimintakyky-1.0.0-rc4.tgz","date":"2025-12-17T06:44:39.000Z","description":"Kanta-palvelujen SOTE-yhteisen toimintakykytietojen määrittelyt. "},{"name":"de.gematik.isik","version":"5.1.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gematik.isik","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.isik-5.1.1.tgz","date":"2025-12-17T10:08:32.000Z","description":"Die Stufe 5 der Informationssysteme im Krankenhaus (ISiK) Festlegung"},{"name":"ch.fhir.ig.ch-rad-order","version":"2.0.1","fhirVersion":"4.0.1","canonical":"http://fhir.ch/ig/ch-rad-order","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ch.fhir.ig.ch-rad-order-2.0.1.tgz","date":"2025-12-17T12:02:35.000Z","description":"Implementation guide CH RAD-Order (R4) (built Wed, Dec 17, 2025 07:17+0000+00:00)"},{"name":"fume.outburn.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fume.outburn.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fume.outburn.r4-1.0.0.tgz","date":"2025-12-17T15:11:41.000Z","description":"FUME artifacts"},{"name":"hl7.fhir.r6.core","version":"6.0.0-ballot4","fhirVersion":"6.0.0-ballot4","canonical":"http://hl7.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.r6.core-6.0.0-ballot4.tgz","date":"2025-12-18T12:00:00.000Z","description":"FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (built Thu, Dec 18, 2025 07:07+1100+11:00)"},{"name":"hl7.fhir.r6.expansions","version":"6.0.0-ballot4","fhirVersion":"6.0.0-ballot4","canonical":"http://hl7.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.r6.expansions-6.0.0-ballot4.tgz","date":"2025-12-18T12:00:00.000Z","description":"Expansions for the 6.0.0-ballot4 version of the FHIR standard (built Thu, Dec 18, 2025 07:07+1100+11:00)"},{"name":"hl7.fhir.r6.examples","version":"6.0.0-ballot4","fhirVersion":"6.0.0-ballot4","canonical":"http://hl7.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.r6.examples-6.0.0-ballot4.tgz","date":"2025-12-18T12:00:00.000Z","description":"Examples for the 6.0.0-ballot4 version of the FHIR standard (built Thu, Dec 18, 2025 07:07+1100+11:00)"},{"name":"hl7.fhir.r6.search","version":"6.0.0-ballot4","fhirVersion":"6.0.0-ballot4","canonical":"http://hl7.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.r6.search-6.0.0-ballot4.tgz","date":"2025-12-18T12:00:00.000Z","description":"FHIR 6.0.0-ballot4 package : Search Parameters (break out combined parameters for server execution convenience) (built Thu, Dec 18, 2025 07:07+1100+11:00)"},{"name":"valid.test","version":"0.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/valid.test","kind":"fhir.ig","url":"https://packages2.fhir.org/web/valid.test-0.0.1.tgz","date":"2025-12-18T14:01:04.000Z","description":"valid.test"},{"name":"ch.fhir.ig.ch-epr-fhir","version":"5.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.ch/ig/ch-epr-fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ch.fhir.ig.ch-epr-fhir-5.0.0.tgz","date":"2025-12-18T18:02:32.000Z","description":"FHIR implementation guide to the Swiss EPR (Electronic Patient Record) (built Thu, Dec 18, 2025 15:42+0000+00:00)"},{"name":"ihe.iti.mhd","version":"5.0.0","fhirVersion":"5.0.0","canonical":"https://profiles.ihe.net/ITI/MHD","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.iti.mhd-5.0.0.tgz","date":"2025-12-18T18:02:39.000Z","description":"ImplementationGuide for IHE IT Infrastructure Technical Framework Supplement Mobile access to Health Documents (MHD) (built Thu, Dec 18, 2025 09:48-0600-06:00)"},{"name":"hl7.fhir.cl.clips","version":"0.5.0-ballot","fhirVersion":"4.0.1","canonical":"https://hl7chile.cl/fhir/ig/clips","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.cl.clips-0.5.0-ballot.tgz","date":"2025-12-18T18:03:05.000Z","description":"Guía IPS homologada para la realidad Chilena. (built Thu, Dec 18, 2025 09:54-0300-03:00)"},{"name":"ca.on.consent.r4","version":"0.10.26","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.consent.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.consent.r4-0.10.26.tgz","date":"2025-12-19T02:43:08.000Z","description":"Ontario Provincial Consent Implementation Guide"},{"name":"de.gematik.erezept-workflow.r4","version":"1.6.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gematik.erezept-workflow.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.erezept-workflow.r4-1.6.1.tgz","date":"2025-12-19T08:36:10.000Z","description":"Die E-Rezept-Spezifikation"},{"name":"de.gematik.erp.t-prescription","version":"1.1.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gematik.erp.t-prescription","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.erp.t-prescription-1.1.0.tgz","date":"2025-12-19T09:57:07.000Z","description":"Spezifikation Datenaustausch E-T-Rezept"},{"name":"rki.emiga.outbreak","version":"0.1.4","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/rki.emiga.outbreak","kind":"fhir.ig","url":"https://packages2.fhir.org/web/rki.emiga.outbreak-0.1.4.tgz","date":"2025-12-19T11:26:33.000Z","description":"Dieses Version ist noch nicht Produktiv"},{"name":"medcom.fhir.dk.homecareobservation","version":"1.2.1","fhirVersion":"4.0.1","canonical":"http://medcomfhir.dk/ig/homecareobservation","kind":"fhir.ig","url":"https://packages2.fhir.org/web/medcom.fhir.dk.homecareobservation-1.2.1.tgz","date":"2025-12-19T12:02:53.000Z","description":"Communication between general practitioners and municipal acute care team. (built Fri, Dec 19, 2025 07:50+0000+00:00)"},{"name":"de.medizininformatikinitiative.kerndatensatz.bildgebung","version":"2026.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.medizininformatikinitiative.kerndatensatz.bildgebung","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.medizininformatikinitiative.kerndatensatz.bildgebung-2026.0.0.tgz","date":"2025-12-19T14:13:31.000Z","description":"Medizininformatik Initiative - Modul Befunde bildgebender Verfahren"},{"name":"de.medizininformatikinitiative.kerndatensatz.molgen","version":"2026.0.4","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.medizininformatikinitiative.kerndatensatz.molgen","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.medizininformatikinitiative.kerndatensatz.molgen-2026.0.4.tgz","date":"2025-12-19T15:33:36.000Z","description":"Medizininformatik Initiative - Modul Molekulargenetischer Befundbericht. Version 2026.0.4: Package build fix and version consistency. Release Notes: https://simplifier.net/guide/MII-Modul-MolekulargenetischerBefundbericht-v2026-DE/MIIIGModulMolekulargenetischerBefundbericht/ReleaseNotes"},{"name":"swiss.mednet.fhir","version":"0.20.0","fhirVersion":"4.0.1","canonical":"https://mednet.swiss/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/swiss.mednet.fhir-0.20.0.tgz","date":"2025-12-19T18:02:56.000Z","description":"This Guide describes mednet interfaces (built Fri, Dec 19, 2025 18:18+0100+01:00)"},{"name":"hl7.fhir.eu.base","version":"2.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.eu/fhir/base","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.eu.base-2.0.0-ballot.tgz","date":"2025-12-22T12:02:52.000Z","description":"This guide collects base and core profiles to be used in the European context. It also includes common artifacts, such as the profiles describing the European Health Insurance Card. (built Fri, Dec 19, 2025 18:28+0100+01:00)"},{"name":"hl7.fhir.eu.base-r5","version":"2.0.0-ballot","fhirVersion":"5.0.0","canonical":"http://hl7.eu/fhir/base-r5","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.eu.base-r5-2.0.0-ballot.tgz","date":"2025-12-22T12:02:52.000Z","description":"This guide collects base and core profiles to be used in the European context. It also includes common artifacts, such as the profiles describing the European Health Insurance Card. (built Fri, Dec 19, 2025 19:52+0100+01:00)"},{"name":"rambam-fhir.health.gov.il","version":"0.3.2","fhirVersion":"4.0.1","canonical":"http://fhir.rmc.gov.il/ImplementationGuide/il.rmc.fhir.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/rambam-fhir.health.gov.il-0.3.2.tgz","date":"2025-12-23T08:00:41.000Z","description":"Rambam FHIR Project"},{"name":"de.basisprofil.r4","version":"1.6.0-ballot2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.basisprofil.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.basisprofil.r4-1.6.0-ballot2.tgz","date":"2025-12-23T22:27:07.000Z","description":"Projekt Basisprofilierung R4 (HL7 Deutschland e.V.)\r\n"},{"name":"fhir.bfarm.de","version":"3.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.bfarm.de","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.bfarm.de-3.0.1.tgz","date":"2025-12-27T16:12:12.000Z","description":"Bereitstellung der im DiGA- und DiPA-Verzeichnis veröffentlichten Daten durch das BfArM"},{"name":"noma.fhir.mpd","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/noma.fhir.mpd","kind":"fhir.ig","url":"https://packages2.fhir.org/web/noma.fhir.mpd-2.0.0.tgz","date":"2026-01-02T09:23:30.000Z","description":"Package for the 2.0.0. release of the NOMA (DMP) FHIR API for IDMP compatible medicinal product dictionary and enteral nutrition "},{"name":"de.medizininformatikinitiative.kerndatensatz.seltene","version":"2026.0.0","fhirVersion":"4.0.1","canonical":"https://www.medizininformatik-initiative.de/fhir/ext/modul-seltene","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.medizininformatikinitiative.kerndatensatz.seltene-2026.0.0.tgz","date":"2026-01-06T10:56:25.000Z","description":"Medizininformatik Initiative - Modul Seltene Erkrankungen. Version 2026.0.0: Finale Version nach Ballot-Abstimmung mit HPO-Phänotypisierung nach HL7 Phenomics IG, Therapieempfehlungen mit Therapietyp. Release Notes: https://simplifier.net/guide/mii-ig-seltene-erkrankungen-v2026-de/ReleaseNotes"},{"name":"de.medizininformatikinitiative.kerndatensatz.patho","version":"2026.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.medizininformatikinitiative.kerndatensatz.patho","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.medizininformatikinitiative.kerndatensatz.patho-2026.0.1.tgz","date":"2026-01-08T11:42:43.000Z","description":"Medizininformatik Initiative - Modul Pathologie Befund"},{"name":"ca.on.erec.r4","version":"0.12.5-2-TU","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.erec.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.erec.r4-0.12.5-2-TU.tgz","date":"2026-01-08T19:54:13.000Z","description":"IG updates with CI/CWM use case\r\n\r\n"},{"name":"digidot.ny","version":"0.2.6","fhirVersion":"4.0.1","canonical":"https://novari.no/fhir/digidot","kind":"fhir.ig","url":"https://packages2.fhir.org/web/digidot.ny-0.2.6.tgz","date":"2026-01-09T15:27:30.000Z","description":"Profiles for exchange of oral health information in the DigiDOT project."},{"name":"hl7.fhir.kr.core","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://www.hl7korea.or.kr/fhir/krcore","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.kr.core-2.0.0.tgz","date":"2026-01-12T07:04:05.000Z","description":"KR Core (built Fri, Aug 29, 2025 13:48+0900+09:00)"},{"name":"fhir.r4.spirecore","version":"0.1.0-alpha","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.r4.spirecore","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.r4.spirecore-0.1.0-alpha.tgz","date":"2026-01-12T10:43:43.000Z","description":"Spire Healthcare - SpireCore profiles based on UKCore (where possible) and custom extensions"},{"name":"rki.emiga.case","version":"0.3.0-alpha.5","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/rki.emiga.case","kind":"fhir.ig","url":"https://packages2.fhir.org/web/rki.emiga.case-0.3.0-alpha.5.tgz","date":"2026-01-12T13:53:22.000Z","description":"EMIGA Fall. Diese Version ist noch nicht produktiv"},{"name":"hl7.fhir.nl.zorgviewer","version":"1.22.0","fhirVersion":"3.0.2","canonical":"http://fhir.hl7.nl/zorgviewer","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.nl.zorgviewer-1.22.0.tgz","date":"2026-01-12T18:03:03.000Z","description":"De zorgviewer biedt zorgverleners een 360° beeld van de patiënt of cliënt. Opgebouwd uit alle beschikbare zorginformatie, waarvoor de patiënt of cliënt toestemming heeft gegeven. (built Mon, Jan 12, 2026 14:24+0000+00:00)"},{"name":"medcom.fhir.dk.core","version":"4.0.0","fhirVersion":"4.0.1","canonical":"http://medcomfhir.dk/ig/core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/medcom.fhir.dk.core-4.0.0.tgz","date":"2026-01-13T18:03:01.000Z","description":"This IG includes core profiles defined by MedCom. These profiles are used in MedCom's FHIR standards (built Tue, Jan 13, 2026 14:02+0000+00:00)"},{"name":"ans.fhir.fr.pdsm","version":"3.1.1","fhirVersion":"4.0.1","canonical":"https://interop.esante.gouv.fr/ig/fhir/pdsm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ans.fhir.fr.pdsm-3.1.1.tgz","date":"2026-01-15T18:02:46.000Z"},{"name":"hl7.fhir.au.base","version":"6.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org.au/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.au.base-6.0.0.tgz","date":"2026-01-16T06:02:40.000Z","description":"This implementation guide is provided to support the use of FHIR®© in an Australian context. (built Thu, Jan 15, 2026 22:19+0000+00:00)"},{"name":"de.gematik.schuleingangsuntersuchung","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gematik.schuleingangsuntersuchung","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.schuleingangsuntersuchung-1.0.0-ballot.tgz","date":"2026-01-16T12:41:00.000Z","description":"Spezifikation der Schuleingangsuntersuchung mit Fokus auf den Sorgeberechtigenfragebogen"},{"name":"kbv.itv.ks","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/kbv.itv.ks","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kbv.itv.ks-2.0.0.tgz","date":"2026-01-16T13:57:30.000Z","description":"Webservice Kollegensuche der KBV"},{"name":"br.go.ses.seguranca","version":"0.1.2","fhirVersion":"4.0.1","canonical":"https://fhir.saude.go.gov.br/r4/seguranca","kind":"fhir.ig","url":"https://packages2.fhir.org/web/br.go.ses.seguranca-0.1.2.tgz","date":"2026-01-20T00:02:55.000Z","description":"Segurança da Informação na SES-GO (built Mon, Jan 19, 2026 21:25+0000+00:00)"},{"name":"ch.fhir.ig.ch-elm","version":"1.13.1","fhirVersion":"4.0.1","canonical":"http://fhir.ch/ig/ch-elm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ch.fhir.ig.ch-elm-1.13.1.tgz","date":"2026-01-21T12:02:37.000Z","description":"FHIR® Implementation Guide for the Electronic Laboratory Report of the Swiss Federal Office of Public Health (built Wed, Jan 21, 2026 11:05+0000+00:00)"},{"name":"de.medizininformatikinitiative.kerndatensatz.mtb","version":"2026.0.0","fhirVersion":"4.0.1","canonical":"https://www.medizininformatik-initiative.de/fhir/ext/modul-mtb/ImplementationGuide/mii-ig-mtb-de","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.medizininformatikinitiative.kerndatensatz.mtb-2026.0.0.tgz","date":"2026-01-22T09:51:52.000Z","description":"Medizininformatik Initiative - Modul Molekulares Tumorboard. Version 2026.0.0: Erste stabile Version nach der Ballot-Phase. Release Notes: https://simplifier.net/guide/MII-IG-MTB-DE/MIIIGModulMolekularesTumorboard/ReleaseNotes"},{"name":"acme.base","version":"2.0.6","fhirVersion":"4.0.1","canonical":"https://fake-acme.org/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/acme.base-2.0.6.tgz","date":"2026-01-22T13:30:57.000Z","description":"🇧🇷 ACME Base Profiles that ACME projects and products can build upon."},{"name":"ca.on.phsd.r4-alpha","version":"1.1.0-draft","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.phsd.r4-alpha","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.phsd.r4-alpha-1.1.0-draft.tgz","date":"2026-01-22T21:51:49.000Z","description":"Internal preview of PHSD 1.1.0"},{"name":"de.uk-koeln.nngm.therapie","version":"0.1.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.uk-koeln.nngm.therapie","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.uk-koeln.nngm.therapie-0.1.0.tgz","date":"2026-01-23T13:27:00.000Z","description":"nNGM Therapie test"},{"name":"il.pcmdemo.fhir.r4","version":"0.1.10","fhirVersion":"4.0.1","canonical":"http://pcmdemo.health.org.il/ImplementationGuide/il.pcmdemo.fhir.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/il.pcmdemo.fhir.r4-0.1.10.tgz","date":"2026-01-25T13:55:51.000Z","description":"PCM Demo"},{"name":"pharmacyeclaim.trial","version":"1.0.0-trial-preview","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/pharmacyeclaim.trial","kind":"fhir.ig","url":"https://packages2.fhir.org/web/pharmacyeclaim.trial-1.0.0-trial-preview.tgz","date":"2026-01-25T21:16:30.000Z","description":"TRIAL USE - FHIR specification for electronic submission of Pharmacy Claims for adjudication in Canada. This FHIR standard is created by CPHA, CLHIA and various Canadian stakeholder groups including vendors, Pharmacy associations, Pharmacy Benefit Managers."},{"name":"iknl.fhir.nl.r4.ncr-ehr","version":"1.4.0","fhirVersion":"4.0.1","canonical":"http://fhir.iknl.nl/fhir/iknl-ncr-ehr-r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/iknl.fhir.nl.r4.ncr-ehr-1.4.0.tgz","date":"2026-01-27T18:03:01.000Z","description":"Deze implementatiegids beschrijft hoe ziekenhuizen, epd-leveranciers en andere partijen die bevoegd zijn om data uit elektronische patiëntendossiers (epd's) of andere relevante databronnen te halen, verbinding kunnen maken met de Nederlandse Kankerregistratie (NKR). (built Tue, Jan 27, 2026 13:59+0100+01:00)"},{"name":"il.fhir.r4.ashmc","version":"0.3.6","fhirVersion":"4.0.1","canonical":"http://fhir.ashmc.co.il/ImplementationGuide/il.fhir.r4.ashmc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/il.fhir.r4.ashmc-0.3.6.tgz","date":"2026-01-28T09:48:13.000Z","description":"Assuta Ashdod FHIR Projects"},{"name":"hl7.fhir.au.core","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org.au/fhir/core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.au.core-2.0.0.tgz","date":"2026-01-28T12:02:39.000Z","description":"This implementation guide is provided to support the use of FHIR®© in an Australian context, and defines the minimum set of constraints on the FHIR resources to create the AU Core profiles. This implementation guide forms the foundation to build future AU Realm FHIR implementation guides and its content will continue to grow to meet the needs of AU implementers. (built Wed, Jan 28, 2026 05:31+0000+00:00)"},{"name":"medcom.fhir.dk.ekg","version":"1.0.2","fhirVersion":"4.0.1","canonical":"http://medcomfhir.dk/ig/ekg","kind":"fhir.ig","url":"https://packages2.fhir.org/web/medcom.fhir.dk.ekg-1.0.2.tgz","date":"2026-01-28T12:02:59.000Z","description":"The DK MedCom IG for EKG (built Wed, Jan 28, 2026 10:06+0000+00:00)"},{"name":"hl7.fhir.pl.base.r5","version":"0.1.5","fhirVersion":"5.0.0","canonical":"http://hl7.org.pl/fhir/ig/pl-base","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.pl.base.r5-0.1.5.tgz","date":"2026-01-28T18:03:06.000Z","description":"Polska bazowa specyfikacja krajowa standardu HL7 FHIR (built Wed, Jan 28, 2026 12:35+0000+00:00)"},{"name":"kbv.all.st","version":"1.34.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/kbv.all.st","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kbv.all.st-1.34.0.tgz","date":"2026-01-29T00:20:20.000Z","description":"KBV Schluesseltabellen"},{"name":"de.gematik.fhir.directory","version":"1.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gematik.fhir.directory","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.fhir.directory-1.0.1.tgz","date":"2026-01-29T10:07:36.000Z","description":"\r\ngematik FHIR Directory: Verzeichnisdienst der Telematikinfrastruktur "},{"name":"hl7.fhir.uv.fhir-clinical-document","version":"1.0.1","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/fhir-clinical-document","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.fhir-clinical-document-1.0.1.tgz","date":"2026-01-29T18:01:17.000Z"},{"name":"maccabi.maccabident.medicationrequest.r4","version":"1.0.9","fhirVersion":"4.0.1","canonical":"http://fhir.maccabi-dent.com/ImplementationGuide/maccabi.maccabident.medicationrequest.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/maccabi.maccabident.medicationrequest.r4-1.0.9.tgz","date":"2026-02-02T20:37:01.000Z","description":"maccabi medication request for maccabi dent. Test by Itay Nachliel"},{"name":"uk.nhsengland.genomics.r4","version":"0.5.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/uk.nhsengland.genomics.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/uk.nhsengland.genomics.r4-0.5.2.tgz","date":"2026-02-03T16:30:10.000Z","description":"FHIR Genomics Implementation Guide FHIR Assets"},{"name":"uz.dhp.core","version":"0.4.0","fhirVersion":"5.0.0","canonical":"https://dhp.uz/fhir/core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/uz.dhp.core-0.4.0.tgz","date":"2026-02-03T18:03:18.000Z","description":"National implementation guide for Uzbekistan using FHIR R5. (built Tue, Feb 3, 2026 12:58+0100+01:00)"},{"name":"de.medizininformatikinitiative.kerndatensatz.pros","version":"2026.0.1","fhirVersion":"4.0.1","canonical":"https://www.medizininformatik-initiative.de/fhir/ext/modul-dok/ImplementationGuide/mii-ig-pro","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.medizininformatikinitiative.kerndatensatz.pros-2026.0.1.tgz","date":"2026-02-04T17:05:55.000Z","description":"MII PRO Module v2026.0.1 - Patch release. Fixes: Canonical URL standardization (http→https), PROMIS-29 German variant, validation fixes. Release Notes: https://simplifier.net/guide/mii-pro-v2026-de/MIIIGModulPRO/Release-Notes"},{"name":"de.gematik.sterbefall","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gematik.sterbefall","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.sterbefall-1.0.0.tgz","date":"2026-02-05T10:06:13.000Z","description":"Spezifikationen im Kontext von Sterbefällen"},{"name":"de.medizininformatikinitiative.kerndatensatz.studie","version":"2026.0.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.medizininformatikinitiative.kerndatensatz.studie","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.medizininformatikinitiative.kerndatensatz.studie-2026.0.2.tgz","date":"2026-02-05T11:16:49.000Z","description":"Medizininformatik Initiative - Modul Medizinisches Forschungsvorhaben"},{"name":"hl7.fhir.uv.extensions.r3","version":"5.1.0-snapshot1","fhirVersion":"3.0.2","canonical":"http://hl7.org/fhir/extensions","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.extensions.r3-5.1.0-snapshot1.tgz","date":"2026-02-05T12:01:17.000Z","description":"This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Tue, Mar 12, 2024 13:29+1100+11:00)"},{"name":"hl7.fhir.uv.extensions.r4","version":"5.1.0-snapshot1","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/extensions","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.extensions.r4-5.1.0-snapshot1.tgz","date":"2026-02-05T12:01:18.000Z","description":"This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Tue, Mar 12, 2024 13:29+1100+11:00)"},{"name":"hl7.fhir.uv.extensions.r5","version":"5.1.0-snapshot1","fhirVersion":"5.0.0","canonical":"http://hl7.org/fhir/extensions","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.extensions.r5-5.1.0-snapshot1.tgz","date":"2026-02-05T12:01:22.000Z","description":"This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Tue, Mar 12, 2024 13:29+1100+11:00)"},{"name":"de.medizininformatikinitiative.kerndatensatz.laborbefund","version":"2026.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.medizininformatikinitiative.kerndatensatz.laborbefund","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.medizininformatikinitiative.kerndatensatz.laborbefund-2026.0.1.tgz","date":"2026-02-05T13:21:47.000Z","description":"Medizininformatik Initiative - Modul Labor"},{"name":"de.medizininformatikinitiative.kerndatensatz.consent","version":"2026.0.1-rc-1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.medizininformatikinitiative.kerndatensatz.consent","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.medizininformatikinitiative.kerndatensatz.consent-2026.0.1-rc-1.tgz","date":"2026-02-05T13:47:35.000Z","description":"KDS Modul Consent Release 2026.0.1-rc-1\r\n- bake-Pipeline Test"},{"name":"de.medizininformatikinitiative.kerndatensatz.icu","version":"2026.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.medizininformatikinitiative.kerndatensatz.icu","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.medizininformatikinitiative.kerndatensatz.icu-2026.0.1.tgz","date":"2026-02-05T15:57:53.000Z","description":"Medizininformatik Initiative - Modul Intensivmedizin PDMS-Daten und hochauflösende Biosignaldaten"},{"name":"medcom.fhir.dk.acknowledgement","version":"2.0.3","fhirVersion":"4.0.1","canonical":"http://medcomfhir.dk/ig/acknowledgement","kind":"fhir.ig","url":"https://packages2.fhir.org/web/medcom.fhir.dk.acknowledgement-2.0.3.tgz","date":"2026-02-05T18:02:45.000Z","description":"The DK MedCom acknowledgement IG (built Thu, Feb 5, 2026 13:47+0000+00:00)"},{"name":"rki.demis.igs","version":"5.0.0","fhirVersion":"4.0.1","canonical":"https://demis.rki.de/fhir/igs","kind":"fhir.ig","url":"https://packages2.fhir.org/web/rki.demis.igs-5.0.0.tgz","date":"2026-02-06T15:40:38.000Z","description":"DEMIS-Integrierte Genomische Surveillance (IGS)"},{"name":"fhir.r4.nhsengland.pathology","version":"0.1.3-alpha","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.r4.nhsengland.pathology","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.r4.nhsengland.pathology-0.1.3-alpha.tgz","date":"2026-02-09T12:48:33.000Z","description":"A project for NHS England FHIR R4 Pathology alpha phase"},{"name":"de.medizininformatikinitiative.use-case.omi","version":"0.3.25","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.medizininformatikinitiative.use-case.omi","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.medizininformatikinitiative.use-case.omi-0.3.25.tgz","date":"2026-02-09T13:26:49.000Z","description":"This FHIR-IG contains all profiles necessary to characterize AI-Services and their artefacts needed. This project is work in progress and will change over time."},{"name":"de.gematik.erezept.eu","version":"1.1.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gematik.erezept.eu","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.erezept.eu-1.1.2.tgz","date":"2026-02-09T13:28:25.000Z","description":"E-Rezept Spezifikation für den EU Austausch"},{"name":"ans.fhir.fr.tde","version":"2.0.0-ballot","fhirVersion":"4.0.1","canonical":"https://interop.esante.gouv.fr/ig/fhir/tde","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ans.fhir.fr.tde-2.0.0-ballot.tgz","date":"2026-02-09T18:02:29.000Z"},{"name":"ca.on.mi.r4","version":"1.0.0-snapshot6","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.mi.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.mi.r4-1.0.0-snapshot6.tgz","date":"2026-02-09T21:04:22.000Z","description":"The purpose of the Medical Imaging (MI) project is to consolidate medical imaging documents and imag"},{"name":"ans.fhir.fr.nde","version":"3.0.0-ballot","fhirVersion":"4.0.1","canonical":"https://interop.esante.gouv.fr/ig/fhir/nde","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ans.fhir.fr.nde-3.0.0-ballot.tgz","date":"2026-02-10T00:02:39.000Z"},{"name":"ca.ab.fhir.psab","version":"1.2.0-pre2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.ab.fhir.psab","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.ab.fhir.psab-1.2.0-pre2.tgz","date":"2026-02-10T18:57:22.000Z","description":"FHIR artifacts for Alberta Patient Summary (PS-AB)"},{"name":"hl7.fhir.us.health-care-surveys-reporting","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/health-care-surveys-reporting","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.health-care-surveys-reporting-2.0.0.tgz","date":"2026-02-11T06:01:08.000Z","description":"This implementation guide (IG) provides Health Level Seven (HL7 FHIR) resources to define standards. This guide contains a library of FHIR profiles and is compliant with FHIR Release 4. (built Wed, Feb 11, 2026 01:46+0000+00:00)"},{"name":"hl7.fhir.au.ereq","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org.au/fhir/ereq","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.au.ereq-1.0.0.tgz","date":"2026-02-11T12:02:34.000Z","description":"This implementation guide is provided to support the use of FHIR®© for clinical requesting and ordering in an Australian context. , and defines the minimum set of constraints on the FHIR resources to create the AU eRequesting profiles. (built Wed, Feb 11, 2026 06:09+0000+00:00)"},{"name":"ch.fhir.ig.ch-emed-epr","version":"3.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.ch/ig/ch-emed-epr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ch.fhir.ig.ch-emed-epr-3.0.0.tgz","date":"2026-02-11T12:02:35.000Z","description":"FHIR Implementation Guide which defines the documents for the exchange of medication information in the context of the Swiss eMedication service (built Wed, Feb 11, 2026 07:01+0000+00:00)"},{"name":"ch.fhir.ig.ch-emed-epr.r4","version":"3.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.ch/ig/ch-emed-epr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ch.fhir.ig.ch-emed-epr.r4-3.0.0.tgz","date":"2026-02-11T12:02:35.000Z","description":"FHIR Implementation Guide which defines the documents for the exchange of medication information in the context of the Swiss eMedication service (built Wed, Feb 11, 2026 07:01+0000+00:00)"},{"name":"medcom.fhir.dk.hospitalnotification","version":"3.0.2","fhirVersion":"4.0.1","canonical":"http://medcomfhir.dk/ig/hospitalnotification","kind":"fhir.ig","url":"https://packages2.fhir.org/web/medcom.fhir.dk.hospitalnotification-3.0.2.tgz","date":"2026-02-11T12:02:55.000Z","description":"The DK MedCom HospitalNotification IG (built Tue, Feb 10, 2026 12:53+0000+00:00)"},{"name":"de.medizininformatikinitiative.kerndatensatz.biobank","version":"2026.0.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.medizininformatikinitiative.kerndatensatz.biobank","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.medizininformatikinitiative.kerndatensatz.biobank-2026.0.1.tgz","date":"2026-02-11T15:47:07.000Z","description":"Medizininformatik Initiative - Kerndatensatz Erweiterungsmodul Biobank / Bioprobendaten"},{"name":"br.go.ses.reds-go","version":"1.0.3","fhirVersion":"4.0.1","canonical":"http://www.saude.gov.br/fhir/r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/br.go.ses.reds-go-1.0.3.tgz","date":"2026-02-12T06:03:00.000Z","description":"NPM Package contendo artefatos de conformidade FHIR da Rede Nacional de Dados em Saúde (RNDS) do Brasil, ajustados para compatibilidade técnica com FHIR R4 sem alteração semântica. (built Thu, Feb 12, 2026 03:00+0000+00:00)"},{"name":"smart.who.int.trust","version":"1.4.0","fhirVersion":"4.0.1","canonical":"http://smart.who.int/trust","kind":"fhir.ig","url":"https://packages2.fhir.org/web/smart.who.int.trust-1.4.0.tgz","date":"2026-02-12T12:02:54.000Z","description":"SMART Trust Implementation Guide (built Wed, Feb 11, 2026 14:11+0000+00:00)"},{"name":"kbv.mio.laborbefund","version":"1.0.0-kommentierung.2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/kbv.mio.laborbefund","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kbv.mio.laborbefund-1.0.0-kommentierung.2.tgz","date":"2026-02-12T12:51:23.000Z","description":"Medizinische Informationsobjekte (MIO) Laborbefund V1.0.0"},{"name":"medcom.fhir.dk.messaging","version":"4.0.2","fhirVersion":"4.0.1","canonical":"http://medcomfhir.dk/ig/messaging","kind":"fhir.ig","url":"https://packages2.fhir.org/web/medcom.fhir.dk.messaging-4.0.2.tgz","date":"2026-02-13T12:02:45.000Z","description":"This IG includes messaging profiles defined by MedCom. These profiles are used in messagebased communication. (built Fri, Feb 13, 2026 09:21+0000+00:00)"},{"name":"de.medizininformatikinitiative.kerndatensatz.medikation","version":"2026.0.1","fhirVersion":"4.0.1","canonical":"https://www.medizininformatik-initiative.de/fhir/core/modul-medikation","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.medizininformatikinitiative.kerndatensatz.medikation-2026.0.1.tgz","date":"2026-02-13T14:16:35.000Z","description":"Medizininformatik Initiative - Modul Medikation"},{"name":"se.electronichealth.fhir.nll.r4","version":"1.1.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/se.electronichealth.fhir.nll.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/se.electronichealth.fhir.nll.r4-1.1.1.tgz","date":"2026-02-13T14:57:45.000Z","description":"The Swedish National Medication List is a nationwide information source that provides caregivers, pharmacies, and patients access to the same information about a patient's prescribed medications. This makes the patient more involved in their care, while prescribers get a better tool for following up the medication treatment. See https://www.ehalsomyndigheten.se/yrkesverksam/nationella-lakemedelslistan/ for more information about the national medication list."},{"name":"kbv.ita.for","version":"1.3.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/kbv.ita.for","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kbv.ita.for-1.3.1.tgz","date":"2026-02-13T15:56:34.000Z","description":"Umsetzung der formularübergreifende Vorgaben für Digitale Muster der KBV"},{"name":"kbv.ita.erp","version":"1.4.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/kbv.ita.erp","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kbv.ita.erp-1.4.1.tgz","date":"2026-02-13T17:04:02.000Z","description":"Umsetzung der elektronischen Arzneimittelverordnung"},{"name":"hl7.fhir.uv.tx-ecosystem","version":"1.9.0","fhirVersion":"5.0.0","canonical":"http://hl7.org/fhir/uv/tx-ecosystem","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.tx-ecosystem-1.9.0.tgz","date":"2026-02-16T12:01:14.000Z","description":"This IG defines the extensions that the tools use internally. Some of these extensions are content that are being evaluated for elevation into the main spec, and others are tooling concerns (built Mon, Feb 16, 2026 20:53+1100+11:00)"},{"name":"medcom.fhir.dk.carecommunication","version":"5.0.2","fhirVersion":"4.0.1","canonical":"http://medcomfhir.dk/ig/carecommunication","kind":"fhir.ig","url":"https://packages2.fhir.org/web/medcom.fhir.dk.carecommunication-5.0.2.tgz","date":"2026-02-16T12:02:42.000Z","description":"The DK MedCom Carecommunication IG (built Fri, Feb 13, 2026 11:52+0000+00:00)"},{"name":"hl7.at.fhir.elga.aps.r4","version":"1.0.0","fhirVersion":"4.0.1","canonical":"https://fhir.hl7.at/elga/aps/r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.at.fhir.elga.aps.r4-1.0.0.tgz","date":"2026-02-16T12:02:46.000Z","description":"The FHIR® implementation guide Austrian Patient Summary is derived from the HL7® Austria FHIR® Core implementation guide and ensures conformity with the International Patient Summary (IPS). (built Mon, Feb 16, 2026 11:31+0000+00:00)"},{"name":"test.colo.qc","version":"0.0.14","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/test.colo.qc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/test.colo.qc-0.0.14.tgz","date":"2026-02-16T13:44:37.000Z","description":"Test projet for validation purposes"},{"name":"hl7.fhir.au.ps","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org.au/fhir/ps","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.au.ps-1.0.0-ballot.tgz","date":"2026-02-16T18:02:25.000Z","description":"AU Patient Summary (AU PS) is provided to support the use of patient summaries in HL7® FHIR®© in an Australian context. It complies with the requirements defined in IPS and AU Core, and sets the minimum expectations on FHIR resources to support conformance and implementation in systems. (built Mon, Feb 16, 2026 11:51+0000+00:00)"},{"name":"hl7.fhir.us.ph-library","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/ph-library","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.ph-library-2.0.0.tgz","date":"2026-02-17T18:01:09.000Z","description":"The US Public Health Profiles Library (USPHPL) is a collection of reusable architecture and content profiles representing common public health concepts and patterns. (built Tue, Feb 17, 2026 13:41+0000+00:00)"},{"name":"portuguese.core.guide","version":"2.0.0","fhirVersion":"4.3.0","canonical":"http://simplifier.net/packages/portuguese.core.guide","kind":"fhir.ig","url":"https://packages2.fhir.org/web/portuguese.core.guide-2.0.0.tgz","date":"2026-02-18T11:39:57.000Z","description":"Publicação do Guia de Implementação para os Profiles Core, versão 2.0.0."},{"name":"ca.on.dhdr.r4","version":"4.0.3-snapshot13","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.dhdr.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.dhdr.r4-4.0.3-snapshot13.tgz","date":"2026-02-18T19:45:09.000Z","description":"Implementation Guide for the Ontario DHDR Version 4 \r\n\r\nClick: https://simplifier.net/guide/ca-on-dhdr-fhir-provider-iguide/TableofContent?version=4.0.2 to access the most recently published IG\r\n\r\nClick: https://simplifier.net/guide/ca-on-dhdr-fhir-provider-iguide/TableofContent?version=4.0.1 to access v 4.0.1\r\n"},{"name":"il.mac.fhir.terminology.r4","version":"0.2.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/il.mac.fhir.terminology.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/il.mac.fhir.terminology.r4-0.2.1.tgz","date":"2026-02-20T08:35:24.000Z","description":"Maccabi HealthCare (Israel) Local Terminology\r\n"},{"name":"hl7.fhir.fi.smart","version":"2.0.0","fhirVersion":"4.0.1","canonical":"https://hl7.fi/fhir/finnish-smart","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.fi.smart-2.0.0.tgz","date":"2026-02-20T12:02:49.000Z","description":"Guidelines for using the SMART App Launch mechanism in Finland. (built Sun, Oct 26, 2025 13:22+0200+02:00)"},{"name":"hl7.fhir.fi.base","version":"2.0.0","fhirVersion":"4.0.1","canonical":"https://hl7.fi/fhir/finnish-base-profiles","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.fi.base-2.0.0.tgz","date":"2026-02-20T12:02:49.000Z","description":"A core set of FHIR resources profiled for use in Finland, published and maintained by HL7 Finland (built Sun, Oct 5, 2025 18:38+0300+03:00)"},{"name":"hl7.fhir.fi.scheduling","version":"2.0.0-rc3","fhirVersion":"4.0.1","canonical":"https://hl7.fi/fhir/finnish-scheduling","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.fi.scheduling-2.0.0-rc3.tgz","date":"2026-02-20T12:02:49.000Z","description":"Finnish HL7 FHIR implementation guide for scheduling, published and maintained by HL7 Finland (built Wed, Aug 27, 2025 16:14+0300+03:00)"},{"name":"ca.on.accdr","version":"1.1.0-snapshot1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.accdr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.accdr-1.1.0-snapshot1.tgz","date":"2026-02-20T20:07:06.000Z","description":"eHealth Ontario "},{"name":"kbv.all.st-rc","version":"1.15.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/kbv.all.st-rc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kbv.all.st-rc-1.15.0.tgz","date":"2026-02-21T00:20:15.000Z","description":"KBV Schluesseltabellen"},{"name":"kbv.all.st-combined","version":"1.30.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/kbv.all.st-combined","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kbv.all.st-combined-1.30.0.tgz","date":"2026-02-21T00:20:20.000Z","description":"KBV Schluesseltabellen"},{"name":"accdr.fhir.ig.pkg","version":"0.9.30","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/accdr.fhir.ig.pkg","kind":"fhir.ig","url":"https://packages2.fhir.org/web/accdr.fhir.ig.pkg-0.9.30.tgz","date":"2026-02-21T01:05:42.000Z","description":"Ontario Health"},{"name":"il.fhir.r4.dgmc","version":"0.8.0","fhirVersion":"4.0.1","canonical":"http://fhir.dgmc.health.gov.il/ImplementationGuide/il.fhir.r4.dgmc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/il.fhir.r4.dgmc-0.8.0.tgz","date":"2026-02-22T09:05:14.000Z","description":"FHIR package for DGMC (Division of Governmental Hospitals Israel)\r\n"},{"name":"ans.fhir.fr.mesures","version":"3.2.0","fhirVersion":"4.0.1","canonical":"https://interop.esante.gouv.fr/ig/fhir/mesures","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ans.fhir.fr.mesures-3.2.0.tgz","date":"2026-02-23T12:02:32.000Z"},{"name":"healthhub.fhir","version":"0.0.11","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/healthhub.fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/healthhub.fhir-0.0.11.tgz","date":"2026-02-24T09:30:18.000Z","description":"Health Hub"},{"name":"fhir.nhs.uk.stu3.assets","version":"1.0.0","fhirVersion":"3.0.1","canonical":"http://simplifier.net/packages/fhir.nhs.uk.stu3.assets","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.nhs.uk.stu3.assets-1.0.0.tgz","date":"2026-02-25T08:51:12.000Z","description":"Assets formerly on the fhir server https://fhir.nhs.uk"},{"name":"nictiz.fhir.nl.r4.medicationprocess9","version":"2.0.0-rc.7","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/nictiz.fhir.nl.r4.medicationprocess9","kind":"fhir.ig","url":"https://packages2.fhir.org/web/nictiz.fhir.nl.r4.medicationprocess9-2.0.0-rc.7.tgz","date":"2026-02-26T10:19:12.000Z","description":"Version 2.0.0-rc.7 release of FHIR R4 conformance resources for Medication Process 9 (MP9) version 3.0.0-rc.2. \r\nPlease consult the implementation guide for more information: \r\nLandingspagina Medicatieproces - informatiestandaarden . "},{"name":"medmij.fhir.nl.stu3.core","version":"1.1.0","fhirVersion":"3.0.1","canonical":"http://simplifier.net/packages/medmij.fhir.nl.stu3.core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/medmij.fhir.nl.stu3.core-1.1.0.tgz","date":"2026-02-26T14:42:33.000Z","description":"MedMij STU3 Core 1.1.0"},{"name":"medmij.fhir.nl.stu3.longtermhealthcare","version":"1.0.0-beta.2","fhirVersion":"3.0.1","canonical":"http://simplifier.net/packages/medmij.fhir.nl.stu3.longtermhealthcare","kind":"fhir.ig","url":"https://packages2.fhir.org/web/medmij.fhir.nl.stu3.longtermhealthcare-1.0.0-beta.2.tgz","date":"2026-02-26T15:03:17.000Z","description":"MedMij Long-term Healthcare 1.0.0-beta.2"},{"name":"medmij.fhir.nl.r4.pathology","version":"1.0.0-alpha.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/medmij.fhir.nl.r4.pathology","kind":"fhir.ig","url":"https://packages2.fhir.org/web/medmij.fhir.nl.r4.pathology-1.0.0-alpha.1.tgz","date":"2026-02-26T19:43:05.000Z","description":"MedMij Pathology 1.0.0-alpha.1"},{"name":"kvdigital.terminsynchronisation-tvs","version":"1.7.1-Expansions","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/kvdigital.terminsynchronisation-tvs","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kvdigital.terminsynchronisation-tvs-1.7.1-Expansions.tgz","date":"2026-02-27T16:13:50.000Z","description":"Terminsynchronisation - TVS"},{"name":"de.einwilligungsmanagement","version":"2.0.3","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.einwilligungsmanagement","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.einwilligungsmanagement-2.0.3.tgz","date":"2026-03-02T14:09:59.000Z","description":"Einwilligungsmanagement Release 2.0.3\r\n\r\nTechnical Correction, Details siehe Changelog im IG\r\n"},{"name":"ca.ab.fhir.aberec1","version":"1.1.0-pre6","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.ab.fhir.aberec1","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.ab.fhir.aberec1-1.1.0-pre6.tgz","date":"2026-03-02T15:28:46.000Z","description":"This version is pre-release for Phase 2c of Alberta eReferral-eConsult project"},{"name":"ans.fhir.fr.tddui","version":"2.3.0-ballot","fhirVersion":"4.0.1","canonical":"https://interop.esante.gouv.fr/ig/fhir/tddui","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ans.fhir.fr.tddui-2.3.0-ballot.tgz","date":"2026-03-03T12:02:21.000Z"},{"name":"dk.ehealth.sundhed.fhir.ig.core","version":"8.0.1","fhirVersion":"4.0.1","canonical":"http://ehealth.sundhed.dk/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/dk.ehealth.sundhed.fhir.ig.core-8.0.1.tgz","date":"2026-03-03T12:02:23.000Z","description":"The Danish eHealth Infrastructure Implementation Guide defines a set of FHIR profiles with extensions and bindings needed to create interoperable, quality-focused applications. (built Tue, Mar 3, 2026 10:24+0000+00:00)"},{"name":"hl7.fhir.be.pss","version":"1.1.0","fhirVersion":"4.0.1","canonical":"https://www.ehealth.fgov.be/standards/fhir/pss","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.be.pss-1.1.0.tgz","date":"2026-03-03T12:02:26.000Z","description":"Example IG exercises many of the fields in a SUSHI configuration. (built Fri, Feb 27, 2026 16:08+0100+01:00)"},{"name":"hl7.fhir.be.core-clinical","version":"1.1.0","fhirVersion":"4.0.1","canonical":"https://www.ehealth.fgov.be/standards/fhir/core-clinical","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.be.core-clinical-1.1.0.tgz","date":"2026-03-03T12:02:26.000Z","description":"HL7 Belgium - Transversal Clinical Core (built Fri, Feb 27, 2026 16:19+0100+01:00)"},{"name":"rki.demis.common","version":"3.0.0-rc.6","fhirVersion":"4.0.1","canonical":"https://demis.rki.de/fhir/common","kind":"fhir.ig","url":"https://packages2.fhir.org/web/rki.demis.common-3.0.0-rc.6.tgz","date":"2026-03-03T12:47:35.000Z","description":"Das DEMIS Common Package definiert das Datenmodell der Basismeldeinhalte."},{"name":"rki.demis.disease","version":"2.2.3","fhirVersion":"4.0.1","canonical":"https://demis.rki.de/fhir/demis","kind":"fhir.ig","url":"https://packages2.fhir.org/web/rki.demis.disease-2.2.3.tgz","date":"2026-03-03T12:51:43.000Z","description":"Beinhaltet die in DEMIS zur Umsetzung der Erkrankungsmeldung definierten Informationsmodellartefakte."},{"name":"rki.demis.laboratory","version":"5.0.1-alpha.6","fhirVersion":"4.0.1","canonical":"https://demis.rki.de/fhir/demis","kind":"fhir.ig","url":"https://packages2.fhir.org/web/rki.demis.laboratory-5.0.1-alpha.6.tgz","date":"2026-03-03T13:02:41.000Z","description":"Beinhaltet die in DEMIS zur Umsetzung der Erregernachweismeldungen definierten Informationsmodellartefakte."},{"name":"kvdigital.vermittlungscode-abrufen-pvs","version":"1.9.0-Expansions","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/kvdigital.vermittlungscode-abrufen-pvs","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kvdigital.vermittlungscode-abrufen-pvs-1.9.0-Expansions.tgz","date":"2026-03-03T16:15:24.000Z","description":"Abrufen eines Vermittlungscodes über ein Praxisverwaltungssystem (PVS)"},{"name":"alticelabs.fhir.smartal.glintt","version":"0.1.0-beta","fhirVersion":"4.0.1","canonical":"http://alticelabs.com/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/alticelabs.fhir.smartal.glintt-0.1.0-beta.tgz","date":"2026-03-03T16:44:46.000Z","description":"FHIR R4 Implementation Guide for the SmartAL to Glintt integration."},{"name":"iknl.fhir.r4.pzp","version":"1.0.0-rc2","fhirVersion":"4.0.1","canonical":"https://api.iknl.nl/docs/pzp/r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/iknl.fhir.r4.pzp-1.0.0-rc2.tgz","date":"2026-03-03T18:02:44.000Z","description":"Advance Care Planning (PZP) IG for FHIR R4 based on zib release 2020 (built Tue, Mar 3, 2026 12:29+0100+01:00)"},{"name":"iknl.fhir.stu3.pzp","version":"1.0.0-rc2","fhirVersion":"3.0.2","canonical":"https://api.iknl.nl/docs/pzp/stu3","kind":"fhir.ig","url":"https://packages2.fhir.org/web/iknl.fhir.stu3.pzp-1.0.0-rc2.tgz","date":"2026-03-03T18:02:44.000Z","description":"Advance Care Planning (PZP) IG for FHIR STU3 based on zib release 2017 (built Tue, Mar 3, 2026 13:12+0100+01:00)"},{"name":"ans.fr.terminologies","version":"1.7.0","fhirVersion":"4.0.1","canonical":"https://interop.esante.gouv.fr/terminologies","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ans.fr.terminologies-1.7.0.tgz","date":"2026-03-04T12:02:33.000Z","description":"Les nomenclatures des objets de Santé sont mises à disposition du secteur santé-social par l’agence du numérique en santé (built Tue, Feb 24, 2026 10:58+0000+00:00)"},{"name":"ca.on.pubsub.r4","version":"1.0.0-BallotedDraft","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.pubsub.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.pubsub.r4-1.0.0-BallotedDraft.tgz","date":"2026-03-04T15:06:55.000Z","description":"This Implementation Guide (IG) will provide comprehensive guidance on leveraging the advanced Subscription Solution."},{"name":"fhir.r4.ukcore.stu3.currentbuild","version":"0.28.0-pre-release","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.r4.ukcore.stu3.currentbuild","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.r4.ukcore.stu3.currentbuild-0.28.0-pre-release.tgz","date":"2026-03-04T15:34:41.000Z","description":"UK Core FHIR profiles and assets"},{"name":"ihe.pcc.fiio","version":"1.0.0-comment","fhirVersion":"4.0.1","canonical":"https://profiles.ihe.net/PCC/FIIO","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.pcc.fiio-1.0.0-comment.tgz","date":"2026-03-05T00:02:35.000Z","description":"Additional options for implementing the HL7 International Patient Summary FHIR document and associated testing requirements. (built Tue, Mar 3, 2026 19:01-0600-06:00)"},{"name":"fhir.base.template.a","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://fhir.org/templates/fhir.base.template","kind":"fhir.template","url":"https://packages2.fhir.org/web/fhir.base.template.a-1.0.0.tgz","date":"2026-03-05T06:02:23.000Z","description":"FHIR IG Base Template - foundational for use by anyone"},{"name":"de.gematik.hddt","version":"1.0.0-rc2","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gematik.hddt","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.hddt-1.0.0-rc2.tgz","date":"2026-03-05T09:29:01.000Z","description":"Specification of health data transfer from devices to DiGA (§374a SGB V)"},{"name":"basisprofil.tiplu.de.r4","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/basisprofil.tiplu.de.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/basisprofil.tiplu.de.r4-2.0.0.tgz","date":"2026-03-05T11:34:09.000Z","description":"Projekt Basisprofilierung (DE) (R4) (Tiplu GmbH)"},{"name":"fhir.r4.nhsengland.programme","version":"0.24.0-pre-release","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/fhir.r4.nhsengland.programme","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.r4.nhsengland.programme-0.24.0-pre-release.tgz","date":"2026-03-05T17:03:08.000Z","description":"NHS England Programme FHIR Implementation Guide for development and testing purposes of specific programmes only"},{"name":"ans.fr.documentation","version":"0.1.10","fhirVersion":"4.0.1","canonical":"https://interop.esante.gouv.fr/ig/documentation","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ans.fr.documentation-0.1.10.tgz","date":"2026-03-05T18:02:24.000Z"},{"name":"ans.fhir.fr.tdmi","version":"3.0.0-ballot","fhirVersion":"4.0.1","canonical":"https://interop.esante.gouv.fr/ig/fhir/tdmi","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ans.fhir.fr.tdmi-3.0.0-ballot.tgz","date":"2026-03-05T18:02:25.000Z"},{"name":"ca.on.oh.setp.iar.dev","version":"1.0.0-ballot1-dev","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.oh.setp.iar.dev","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.oh.setp.iar.dev-1.0.0-ballot1-dev.tgz","date":"2026-03-06T19:41:38.000Z","description":"Release for development testing only"},{"name":"de.gematik.dipag","version":"1.0.4","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gematik.dipag","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.dipag-1.0.4.tgz","date":"2026-03-07T11:43:43.000Z","description":"Der 'Digitale Patientenrechnung'-Fachdienst ermöglicht es Versicherten (allgemein Rechnungsempfängern) Rechnungen von Leistungserbringern zu erhalten und bei Kostenträgern einzureichen."},{"name":"hl7.terminology.r3","version":"7.1.0","fhirVersion":"3.0.2","canonical":"http://terminology.hl7.org","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.terminology.r3-7.1.0.tgz","date":"2026-03-08T12:17:17.000Z","description":"Defines and exposes all HL7 terminologies managed through the unified terminology governance process (built Sun, Mar 8, 2026 18:17-0600-06:00)"},{"name":"hl7.terminology.r4","version":"7.1.0","fhirVersion":"4.0.1","canonical":"http://terminology.hl7.org","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.terminology.r4-7.1.0.tgz","date":"2026-03-08T12:17:17.000Z","description":"Defines and exposes all HL7 terminologies managed through the unified terminology governance process (built Sun, Mar 8, 2026 18:17-0600-06:00)"},{"name":"hl7.terminology.r5","version":"7.1.0","fhirVersion":"5.0.0","canonical":"http://terminology.hl7.org","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.terminology.r5-7.1.0.tgz","date":"2026-03-08T12:17:17.000Z","description":"Defines and exposes all HL7 terminologies managed through the unified terminology governance process (built Sun, Mar 8, 2026 18:17-0600-06:00)"},{"name":"hl7.terminology","version":"7.1.0","fhirVersion":"5.0.0","canonical":"http://terminology.hl7.org","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.terminology-7.1.0.tgz","date":"2026-03-08T12:17:17.000Z","description":"Defines and exposes all HL7 terminologies managed through the unified terminology governance process (built Sun, Mar 8, 2026 18:17-0600-06:00)"},{"name":"rki.emiga.vzd","version":"2.0.0-alpha.21","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/rki.emiga.vzd","kind":"fhir.ig","url":"https://packages2.fhir.org/web/rki.emiga.vzd-2.0.0-alpha.21.tgz","date":"2026-03-09T14:48:33.000Z","description":"EMIGA Verzeichnisdienstinhalte. Dieses Version ist noch nicht produktiv"},{"name":"ca.on.oh-seris","version":"0.11.0-alpha1.0.5","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.oh-seris","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.oh-seris-0.11.0-alpha1.0.5.tgz","date":"2026-03-09T16:35:10.000Z","description":"Updated VS to remove references of Netherlands SNOMED codes"},{"name":"synapxe.sgcdi","version":"1.1.3","fhirVersion":"5.0.0","canonical":"http://simplifier.net/packages/synapxe.sgcdi","kind":"fhir.ig","url":"https://packages2.fhir.org/web/synapxe.sgcdi-1.1.3.tgz","date":"2026-03-10T01:52:22.000Z","description":"Synapxe SGCDI Project"},{"name":"medcom.fhir.dk.notes","version":"1.0.0-trial-use","fhirVersion":"4.0.1","canonical":"http://medcomfhir.dk/ig/notes","kind":"fhir.ig","url":"https://packages2.fhir.org/web/medcom.fhir.dk.notes-1.0.0-trial-use.tgz","date":"2026-03-10T01:52:56.000Z","description":"The DK MedCom Notes IG (built Tue, Mar 10, 2026 13:52+0000+00:00)"},{"name":"medcom.fhir.dk.document","version":"2.0.1","fhirVersion":"4.0.1","canonical":"http://medcomfhir.dk/ig/document","kind":"fhir.ig","url":"https://packages2.fhir.org/web/medcom.fhir.dk.document-2.0.1.tgz","date":"2026-03-10T10:51:18.000Z","description":"The DK MedCom Document IG (built Tue, Mar 10, 2026 10:51+0000+00:00)"},{"name":"rl.fhir.r4","version":"0.0.18","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/rl.fhir.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/rl.fhir.r4-0.0.18.tgz","date":"2026-03-10T14:47:36.000Z","description":"Progetto FHIR per Regione Lombardia"},{"name":"ca.on.mha.pds","version":"2.0.0-snapshot10","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.mha.pds","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.mha.pds-2.0.0-snapshot10.tgz","date":"2026-03-10T17:40:14.000Z","description":"Ontario Mental Health and Addictions Provincial Data Set"},{"name":"hl7.fhir.dk.core","version":"3.6.0","fhirVersion":"4.0.1","canonical":"http://hl7.dk/fhir/core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.dk.core-3.6.0.tgz","date":"2026-03-11T10:10:00.000Z","description":"A FHIR Implementation Guide for the Danish common needs across healthcare sectors (built Wed, Mar 11, 2026 23:10+0100+01:00)"},{"name":"se.electronichealth.fhir.nppr.r5","version":"0.1.0-alpha","fhirVersion":"5.0.0","canonical":"http://simplifier.net/packages/se.electronichealth.fhir.nppr.r5","kind":"fhir.ig","url":"https://packages2.fhir.org/web/se.electronichealth.fhir.nppr.r5-0.1.0-alpha.tgz","date":"2026-03-11T11:27:44.000Z","description":"This project contains core profiles for the basic data (grunddata) domains person and person roles (patient, personnel, related person). The profiles are created and maintained by the Swedish e-Health Agency."},{"name":"rki.emiga.common","version":"1.2.0-alpha.21","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/rki.emiga.common","kind":"fhir.ig","url":"https://packages2.fhir.org/web/rki.emiga.common-1.2.0-alpha.21.tgz","date":"2026-03-11T11:35:39.000Z","description":"Diese Version ist noch nicht produktiv. "},{"name":"de.medizininformatikinitiative.kerndatensatz.dokument","version":"2026.0.1","fhirVersion":"4.0.1","canonical":"https://www.medizininformatik-initiative.de/fhir/ext/modul-dokument/ImplementationGuide/mii-ig-dokument","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.medizininformatikinitiative.kerndatensatz.dokument-2026.0.1.tgz","date":"2026-03-11T16:37:48.000Z","description":"Medizininformatik Initiative - Modul Dokument"},{"name":"r50.test1234","version":"0.0.1","fhirVersion":"5.0.0","canonical":"http://simplifier.net/packages/r50.test1234","kind":"fhir.ig","url":"https://packages2.fhir.org/web/r50.test1234-0.0.1.tgz","date":"2026-03-12T10:13:42.000Z","description":"test"},{"name":"mes.fhir.fr.mesure","version":"2.1.0","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/mes.fhir.fr.mesure","kind":"fhir.ig","url":"https://packages2.fhir.org/web/mes.fhir.fr.mesure-2.1.0.tgz","date":"2026-03-12T10:49:28.000Z","description":"Ce projet regroupe l'ensemble des ressources FHIR utilisées par l'API Mesures de Mon espace santé."},{"name":"de.gematik.vsdm2","version":"1.0.0-rc7","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.gematik.vsdm2","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.vsdm2-1.0.0-rc7.tgz","date":"2026-03-13T12:41:47.000Z"},{"name":"de.medizininformatikinitiative.kerndatensatz.onkologie","version":"2026.0.3-rc.1","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/de.medizininformatikinitiative.kerndatensatz.onkologie","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.medizininformatikinitiative.kerndatensatz.onkologie-2026.0.3-rc.1.tgz","date":"2026-03-13T14:45:18.000Z","description":"MII Kerndatensatz Modul Onkologie v2026.0.2 - ATC-DE 2026 Update mit 23 neuen Codes, Display-Name-Korrekturen (WIdO-validiert), neue Substanzklasse L01EP (c-MET-Inhibitoren). Release Notes: https://simplifier.net/guide/mii-ig-modul-onkologie-v2026-de/MIIIGModulOnkologie/Release-Notes"},{"name":"helsenorge.profiler","version":"2.0.3","fhirVersion":"4.0.1","canonical":"http://helsenorge.no/fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/helsenorge.profiler-2.0.3.tgz","date":"2026-03-13T15:18:33.000Z","description":"For test - not for production: Beskrivelser av FHIR-profiler på HelseNorge. Siden er under oppbygging og profiler hentes/legges inn fortløpende. Det er en del opprydding som gjenstår etter import fra github"},{"name":"hl7.fhir.eu.health-data-api","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.eu/fhir/health-data-api","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.eu.health-data-api-1.0.0-ballot.tgz","date":"2026-03-13T20:24:29.000Z","description":"This Implementation Guide defines FHIR-based APIs for accessing and exchanging health data in the European Health Data Space (EHDS). It composes existing IHE and HL7 specifications — MHD for document exchange, SMART Backend Services for authorization, PDQm for patient matching, and IPA for resource access — into a unified conformance target for EHR systems across Europe. (built Fri, Mar 13, 2026 21:22+0100+01:00)"},{"name":"ca.on.oh-eforms","version":"1.0.0-ballot5","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.oh-eforms","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.oh-eforms-1.0.0-ballot5.tgz","date":"2026-03-14T00:56:15.000Z","description":"Post Open Review Updates"},{"name":"ihe.formatcode.fhir","version":"1.5.0","fhirVersion":"4.0.1","canonical":"https://profiles.ihe.net/fhir/ihe.formatcode.fhir","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ihe.formatcode.fhir-1.5.0.tgz","date":"2026-03-14T14:01:07.000Z","description":"Implementation Guide for IHE defined FormatCode vocabulary. (built Sat, Mar 14, 2026 21:01-0500-05:00)"},{"name":"lt.hl7.fhir.base","version":"0.3.0","fhirVersion":"5.0.0","canonical":"https://hl7.lt/fhir/base","kind":"fhir.ig","url":"https://packages2.fhir.org/web/lt.hl7.fhir.base-0.3.0.tgz","date":"2026-03-15T04:57:53.000Z","description":"Lithuanian Base Implementation Guide (built Sun, Mar 15, 2026 18:57+0200+02:00)"},{"name":"lt.hl7.fhir.eu","version":"0.0.2","fhirVersion":"5.0.0","canonical":"https://hl7.lt/fhir/eu","kind":"fhir.ig","url":"https://packages2.fhir.org/web/lt.hl7.fhir.eu-0.0.2.tgz","date":"2026-03-15T07:19:00.000Z","description":"The copy of the Laboratory Report and Imaging Report Implementation Guide, to enable them for development of the Lithuanian Implementation Guides. The content is based on the HL7 Europe IGs. This IG should be removed after publication of the official IG-s. (built Sun, Mar 15, 2026 21:19+0200+02:00)"},{"name":"hl7.fhir.eu.imaging","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.eu/fhir/imaging","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.eu.imaging-1.0.0-ballot.tgz","date":"2026-03-16T13:37:33.000Z","description":"This guide describes how a Imaging Report can be represented in the European REALM using FHIR R4. (built Mon, Mar 16, 2026 14:15+0100+01:00)"},{"name":"kvdigital.terminschnittstelle-fuer-kven","version":"2.1.0-Expansions","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/kvdigital.terminschnittstelle-fuer-kven","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kvdigital.terminschnittstelle-fuer-kven-2.1.0-Expansions.tgz","date":"2026-03-16T18:13:38.000Z","description":"Vermittlung von Terminen durch Kassenärztliche Vereinigungen (KVen)"},{"name":"ca.on.ehr.r4","version":"1.0.0-snapshot21","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/ca.on.ehr.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/ca.on.ehr.r4-1.0.0-snapshot21.tgz","date":"2026-03-16T19:56:41.000Z","description":"Trial for use release"},{"name":"kvdigital.terminschnittstelle-fuer-dritte","version":"2.4.2-Expansions","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/kvdigital.terminschnittstelle-fuer-dritte","kind":"fhir.ig","url":"https://packages2.fhir.org/web/kvdigital.terminschnittstelle-fuer-dritte-2.4.2-Expansions.tgz","date":"2026-03-17T15:55:56.000Z","description":"Vermittlung von Terminen durch Dritte gemäß § 370a Absatz 2 SGB V"},{"name":"no.nhn.fhir.helsenorge.profiles","version":"2.0.1-beta","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/no.nhn.fhir.helsenorge.profiles","kind":"fhir.ig","url":"https://packages2.fhir.org/web/no.nhn.fhir.helsenorge.profiles-2.0.1-beta.tgz","date":"2026-03-17T16:42:54.000Z","description":"Beskrivelser av FHIR-profiler på HelseNorge. Siden er under oppbygging og profiler hentes/legges inn fortløpende. Det er en del opprydding som gjenstår etter import fra github"},{"name":"fhir.cdc.opioid-cds-r4","version":"2022.1.0","fhirVersion":"4.0.1","canonical":"http://fhir.org/guides/cdc/opioid-cds","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.cdc.opioid-cds-r4-2022.1.0.tgz","date":"2026-03-17T17:10:11.000Z","description":"2022 CDC Clinical Practice Guideline for Prescribing Opioids Implementation Guide (built Wed, Mar 18, 2026 16:10+1100+11:00)"},{"name":"il.core.fhir.r4","version":"0.20.3","fhirVersion":"4.0.1","canonical":"http://simplifier.net/packages/il.core.fhir.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/il.core.fhir.r4-0.20.3.tgz","date":"2026-03-18T12:03:02.000Z","description":"IL core project version 0.20.3"},{"name":"il.hdp.fhir.r4","version":"0.4.2","fhirVersion":"4.0.1","canonical":"http://hdp.fhir.health.gov.il/ImplementationGuide/il.hdp.fhir.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/il.hdp.fhir.r4-0.4.2.tgz","date":"2026-03-18T12:15:04.000Z","description":"Implementation Guide for the Israeli Health Data Portability law - 0.4.2\r\n"},{"name":"il.szmc.fhir.r4","version":"0.3.6","fhirVersion":"4.0.1","canonical":"http://fhir.szmc.org.il/ImplementationGuide/il.szmc.fhir.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/il.szmc.fhir.r4-0.3.6.tgz","date":"2026-03-18T12:22:48.000Z","description":"FHIR Package for Shaare Zedek Medical Center, Jerusalem, Israel"},{"name":"il.tasmc.fhir.r4","version":"0.7.1","fhirVersion":"4.0.1","canonical":"http://fhir.tasmc.org.il/ImplementationGuide/il.tasmc.fhir.r4","kind":"fhir.ig","url":"https://packages2.fhir.org/web/il.tasmc.fhir.r4-0.7.1.tgz","date":"2026-03-18T12:25:21.000Z","description":"Tel Aviv Sourasky Medical Center"},{"name":"il.laniado.fhir.r4","version":"0.2.10","fhirVersion":"4.0.1","canonical":"http://fhir.laniado.org.il/ImplementationGuide/LaniadoHospital","kind":"fhir.ig","url":"https://packages2.fhir.org/web/il.laniado.fhir.r4-0.2.10.tgz","date":"2026-03-18T12:30:16.000Z","description":"Laniado Hospital Project"},{"name":"leumit.fhir.r4","version":"0.6.7","fhirVersion":"4.0.1","canonical":"http://fhir.leumit.co.il/ImplementationGuide/il.fhir.r4.leumit-hdp","kind":"fhir.ig","url":"https://packages2.fhir.org/web/leumit.fhir.r4-0.6.7.tgz","date":"2026-03-18T12:35:47.000Z","description":"leumit FHIR entities"},{"name":"hl7.fhir.us.davinci-pct","version":"2.0.1","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-pct","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-pct-2.0.1.tgz","date":"2026-03-20T00:38:03.000Z","description":"To support the request for cost information for specific items and services from the payer and return them in near real-time to allow effective decision making by the patient in consultation with the 'ordering' provider. (built Fri, Mar 20, 2026 11:38+1100+11:00)"},{"name":"hl7.fhir.eu.imaging-r5","version":"1.0.0-ballot","fhirVersion":"5.0.0","canonical":"http://hl7.eu/fhir/imaging-r5","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.eu.imaging-r5-1.0.0-ballot.tgz","date":"2026-03-20T12:26:32.000Z","description":"This guide describes how a Imaging Report can be represented in the European REALM using FHIR R5. (built Fri, Mar 20, 2026 12:59+0100+01:00)"},{"name":"hl7.fhir.uv.xver-r2.r4","version":"0.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/xver","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r2.r4-0.1.0.tgz","date":"2026-03-21T06:58:45.000Z","description":"Extensions for Using Data Elements from FHIR DSTU2 in FHIR R4 (built Fri, Mar 20, 2026 10:54+1100+11:00)"},{"name":"hl7.fhir.uv.xver-r2.r4b","version":"0.1.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/xver","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r2.r4b-0.1.0.tgz","date":"2026-03-21T06:58:45.000Z","description":"Extensions for Using Data Elements from FHIR DSTU2 in FHIR R4B (built Fri, Mar 20, 2026 11:13+1100+11:00)"},{"name":"hl7.fhir.uv.xver-r2.r5","version":"0.1.0","fhirVersion":"5.0.0","canonical":"http://hl7.org/fhir/uv/xver","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r2.r5-0.1.0.tgz","date":"2026-03-21T06:58:45.000Z","description":"Cross Version Extensions to use FHIR DSTU2 in FHIR R5 (built Fri, Mar 20, 2026 11:35+1100+11:00)"},{"name":"hl7.fhir.uv.xver-r3.r4","version":"0.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/xver","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r3.r4-0.1.0.tgz","date":"2026-03-21T06:58:45.000Z","description":"Extensions for Using Data Elements from FHIR STU3 in FHIR R4 (built Fri, Mar 20, 2026 11:58+1100+11:00)"},{"name":"hl7.fhir.uv.xver-r3.r4b","version":"0.1.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/xver","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r3.r4b-0.1.0.tgz","date":"2026-03-21T06:58:45.000Z","description":"Extensions for Using Data Elements from FHIR STU3 in FHIR R4B (built Fri, Mar 20, 2026 12:09+1100+11:00)"},{"name":"hl7.fhir.uv.xver-r3.r5","version":"0.1.0","fhirVersion":"5.0.0","canonical":"http://hl7.org/fhir/uv/xver","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r3.r5-0.1.0.tgz","date":"2026-03-21T06:58:45.000Z","description":"Cross Version Extensions to use FHIR STU3 in FHIR R5 (built Fri, Mar 20, 2026 12:39+1100+11:00)"},{"name":"hl7.fhir.uv.xver-r4.r4b","version":"0.1.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/xver","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r4.r4b-0.1.0.tgz","date":"2026-03-21T06:58:45.000Z","description":"Extensions for Using Data Elements from FHIR R4 in FHIR R4B (built Fri, Mar 20, 2026 13:27+1100+11:00)"},{"name":"hl7.fhir.uv.xver-r4.r5","version":"0.1.0","fhirVersion":"5.0.0","canonical":"http://hl7.org/fhir/uv/xver","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r4.r5-0.1.0.tgz","date":"2026-03-21T06:58:45.000Z","description":"Cross Version Extensions to use FHIR R4 in FHIR R5 (built Fri, Mar 20, 2026 13:38+1100+11:00)"},{"name":"hl7.fhir.uv.xver-r4b.r4","version":"0.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/xver","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r4b.r4-0.1.0.tgz","date":"2026-03-21T06:58:45.000Z","description":"Extensions for Using Data Elements from FHIR R4B in FHIR R4 (built Fri, Mar 20, 2026 14:30+1100+11:00)"},{"name":"hl7.fhir.uv.xver-r4b.r5","version":"0.1.0","fhirVersion":"5.0.0","canonical":"http://hl7.org/fhir/uv/xver","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r4b.r5-0.1.0.tgz","date":"2026-03-21T06:58:45.000Z","description":"Cross Version Extensions to use FHIR R4B in FHIR R5 (built Fri, Mar 20, 2026 14:38+1100+11:00)"},{"name":"hl7.fhir.uv.xver-r5.r4","version":"0.1.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/xver","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r5.r4-0.1.0.tgz","date":"2026-03-21T06:58:45.000Z","description":"Extensions for Using Data Elements from FHIR R5 in FHIR R4 (built Fri, Mar 20, 2026 15:40+1100+11:00)"},{"name":"hl7.fhir.uv.xver-r5.r4b","version":"0.1.0","fhirVersion":"4.3.0","canonical":"http://hl7.org/fhir/uv/xver","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r5.r4b-0.1.0.tgz","date":"2026-03-21T06:58:45.000Z","description":"Extensions for Using Data Elements from FHIR R5 in FHIR R4B (built Fri, Mar 20, 2026 16:18+1100+11:00)"},{"name":"hl7.fhir.uv.xver-r4.r3","version":"0.1.0","fhirVersion":"3.0.2","canonical":"http://hl7.org/fhir/uv/xver","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r4.r3-0.1.0.tgz","date":"2026-03-21T06:58:45.000Z","description":"Extensions for Using Data Elements from FHIR R4 in FHIR STU3 (built Fri, Mar 20, 2026 13:05+1100+11:00)"},{"name":"hl7.fhir.uv.xver-r4b.r3","version":"0.1.0","fhirVersion":"3.0.2","canonical":"http://hl7.org/fhir/uv/xver","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r4b.r3-0.1.0.tgz","date":"2026-03-21T06:58:45.000Z","description":"Extensions for Using Data Elements from FHIR R4B in FHIR STU3 (built Fri, Mar 20, 2026 13:55+1100+11:00)"},{"name":"hl7.fhir.uv.xver-r5.r3","version":"0.1.0","fhirVersion":"3.0.2","canonical":"http://hl7.org/fhir/uv/xver","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.xver-r5.r3-0.1.0.tgz","date":"2026-03-21T06:58:45.000Z","description":"Extensions for Using Data Elements from FHIR R5 in FHIR STU3 (built Fri, Mar 20, 2026 14:49+1100+11:00)"},{"name":"smart.who.int.dak-srv","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://smart.who.int/dak-srv","kind":"fhir.ig","url":"https://packages2.fhir.org/web/smart.who.int.dak-srv-1.0.0.tgz","date":"2026-03-23T12:42:48.000Z","description":"Surveillance Digital Adaptation Kit (DAK) Implementation Guide for publishing SMART DAK content for infectious disease surveillance (built Mon, Mar 23, 2026 12:42+0000+00:00)"},{"name":"hl7.fhir.uv.sdc","version":"4.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/sdc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.sdc-4.0.0.tgz","date":"2026-03-23T17:16:08.000Z","description":"The SDC specification provides an infrastructure to standardize the capture and expanded use of patient-level data collected within an EHR. (built Tue, Mar 24, 2026 16:16+1100+11:00)"},{"name":"hl7.fhir.us.davinci-hrex","version":"1.2.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-hrex","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-hrex-1.2.0.tgz","date":"2026-03-23T18:12:23.000Z","description":"The Da Vinci Payer Health Record exchange (HRex) Framework/library specifies the FHIR elements used in multiple Da Vinci implementation guides. This includes FHIR profiles, functions, operations, and constraints on other specifications such as CDS-Hooks and other aspects of Da Vinci Use Cases that are common across more than a single use case.\\n\\nDa Vinci HRex Implementation Guide (IG) will make use of US Core profiles that are based on the FHIR R4 specification wherever practical. The HRex IG will use the HL7 FHIR Release 4/US Core STU3 specification as its base but will provide additional guidance and documentation to support implementations that follow the HL7 FHIR STU3/US Core STU2 and HL7 FHIR DSTU2/Argonaut specifications.\\n\\nThe HRex profiles documented in this IG will be used to exchange data between providers systems (e.g. EHRs) and other providers, payers, and third-party applications where appropriate. In addition, exchanges from payer systems to providers, other payers, and third-party applications are supported by the HRex profiles and operations.\\n\\nHRex may define new extensions, profiles, value sets, constraints/extension to other specification (e.g. specific CDS-Hooks) that are specific Da Vinci requirements. Where appropriate these Da Vinci specific artifacts will be promoted for incorporation into the future versions of existing standards (e.g. R4 US Core profiles) and deprecated in this guide on publication in the updated standard. (built Tue, Mar 24, 2026 17:12+1100+11:00)"},{"name":"hl7.fhir.uv.tools.r3","version":"1.1.2","fhirVersion":"3.0.2","canonical":"http://hl7.org/fhir/tools","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.tools.r3-1.1.2.tgz","date":"2026-03-24T00:13:30.000Z","description":"This IG defines the extensions that the tools use internally. Some of these extensions are content that are being evaluated for elevation into the main spec, and others are tooling concerns (built Tue, Mar 24, 2026 11:13+1100+11:00)"},{"name":"hl7.fhir.uv.tools.r4","version":"1.1.2","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/tools","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.tools.r4-1.1.2.tgz","date":"2026-03-24T00:13:30.000Z","description":"This IG defines the extensions that the tools use internally. Some of these extensions are content that are being evaluated for elevation into the main spec, and others are tooling concerns (built Tue, Mar 24, 2026 11:13+1100+11:00)"},{"name":"hl7.fhir.uv.tools.r5","version":"1.1.2","fhirVersion":"5.0.0","canonical":"http://hl7.org/fhir/tools","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.tools.r5-1.1.2.tgz","date":"2026-03-24T00:13:30.000Z","description":"This IG defines the extensions that the tools use internally. Some of these extensions are content that are being evaluated for elevation into the main spec, and others are tooling concerns (built Tue, Mar 24, 2026 11:13+1100+11:00)"},{"name":"hl7.fhir.uv.tools","version":"1.1.2","fhirVersion":"5.0.0","canonical":"http://hl7.org/fhir/tools","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.tools-1.1.2.tgz","date":"2026-03-24T00:13:30.000Z","description":"This IG defines the extensions that the tools use internally. Some of these extensions are content that are being evaluated for elevation into the main spec, and others are tooling concerns (built Tue, Mar 24, 2026 11:13+1100+11:00)"},{"name":"hl7.fhir.fr.core","version":"2.2.0","fhirVersion":"4.0.1","canonical":"https://hl7.fr/ig/fhir/core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.fr.core-2.2.0.tgz","date":"2026-03-25T05:02:37.000Z","description":"Guide d'implémentation FR Core définissant la structuration générique de FHIR en France. Socle de référence à utiliser systématiquement dans tout projet FHIR français. (built Wed, Mar 25, 2026 18:02+0100+01:00)"},{"name":"hl7.fhir.be.patient-dossier","version":"1.0.0","fhirVersion":"4.0.1","canonical":"https://www.ehealth.fgov.be/standards/fhir/patient-dossier","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.be.patient-dossier-1.0.0.tgz","date":"2026-03-26T03:53:30.000Z","description":"HL7 Belgium FHIR Implementation Guide: Patient Dossier (built Thu, Mar 26, 2026 16:53+0100+01:00)"},{"name":"hl7.fhir.us.davinci-pas","version":"2.2.1","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-pas","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-pas-2.2.1.tgz","date":"2026-03-26T14:58:48.000Z","description":"Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Fri, Mar 27, 2026 13:58+1100+11:00)"},{"name":"hl7.fhir.us.davinci-dtr","version":"2.2.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-dtr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-dtr-2.2.0.tgz","date":"2026-03-26T17:04:08.000Z","description":"The Documentation Templates and Rules (DTR) Implementation Guide (IG) specifies how payer rules can be executed in a provider context to ensure that documentation requirements are met. The IG is a companion to the Coverage Requirements Discovery (CRD) IG, which uses CDS Hooks to query payers to determine if there are documentation requirements for a proposed medication, procedure or other service. (built Fri, Mar 27, 2026 16:04+1100+11:00)"},{"name":"hl7.fhir.us.carin-bb","version":"2.2.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/carin-bb","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.carin-bb-2.2.0.tgz","date":"2026-03-26T19:06:11.000Z","description":"CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) (built Fri, Mar 27, 2026 18:06+1100+11:00)"},{"name":"tw.gov.mohw.nhi.pas","version":"1.2.1","fhirVersion":"4.0.1","canonical":"https://nhicore.nhi.gov.tw/pas","kind":"fhir.ig","url":"https://packages2.fhir.org/web/tw.gov.mohw.nhi.pas-1.2.1.tgz","date":"2026-03-26T20:48:34.000Z","description":"臺灣健保事前審查實作指引(Taiwan NHI Prior Authorization Support Implementation Guide，TWPAS IG) (built Fri, Mar 27, 2026 16:48+0800+08:00)"},{"name":"hl7.fhir.us.davinci-crd","version":"2.2.1","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/davinci-crd","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.davinci-crd-2.2.1.tgz","date":"2026-03-27T00:32:28.000Z","description":"Guidelines for conveying coverage requirements to clinicians when planning treatment (built Fri, Mar 27, 2026 11:32+1100+11:00)"},{"name":"hl7.fhir.pubpack","version":"0.2.5","fhirVersion":"4.0.1","canonical":"http://fhir.org/packages/hl7.fhir.pubpack","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.pubpack-0.2.5.tgz","date":"2026-03-27T15:39:06.000Z"},{"name":"fhir.tx.support.r4","version":"0.36.0","fhirVersion":"4.0.1","canonical":"http://fhir.org/terminology-support","kind":"fhir.ig","url":"https://packages2.fhir.org/web/fhir.tx.support.r4-0.36.0.tgz","date":"2026-03-27T15:39:07.000Z","description":"Various supporting code systems for tx.fhir.org (R4)"},{"name":"hl7.fhir.eu.extensions","version":"1.3.0","fhirVersion":"5.0.0","canonical":"http://hl7.eu/fhir/extensions","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.eu.extensions-1.3.0.tgz","date":"2026-03-27T18:49:59.000Z","description":"This guide lists the extensions specified for the European REALM. (built Fri, Mar 27, 2026 19:47+0100+01:00)"},{"name":"hl7.fhir.eu.extensions.r5","version":"1.3.0","fhirVersion":"5.0.0","canonical":"http://hl7.eu/fhir/extensions","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.eu.extensions.r5-1.3.0.tgz","date":"2026-03-27T18:49:59.000Z","description":"This guide lists the extensions specified for the European REALM. (built Fri, Mar 27, 2026 19:47+0100+01:00)"},{"name":"hl7.fhir.eu.extensions.r4","version":"1.3.0","fhirVersion":"4.0.1","canonical":"http://hl7.eu/fhir/extensions","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.eu.extensions.r4-1.3.0.tgz","date":"2026-03-27T18:49:59.000Z","description":"This guide lists the extensions specified for the European REALM. (built Fri, Mar 27, 2026 19:47+0100+01:00)"},{"name":"hl7.fhir.us.ph-bulk-data","version":"2.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/ph-bulk-data","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.ph-bulk-data-2.0.0-ballot.tgz","date":"2026-03-30T20:09:53.000Z","description":"White paper describing the application of FHIR bulk data to public health use cases (built Tue, Mar 31, 2026 07:09+1100+11:00)"},{"name":"hl7.fhir.us.pcs","version":"1.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/pcs","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.pcs-1.0.0-ballot.tgz","date":"2026-03-30T21:58:54.000Z"},{"name":"hl7.fhir.uv.phd","version":"2.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/phd","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.phd-2.0.0.tgz","date":"2026-03-31T14:09:40.000Z"},{"name":"hl7.fhir.us.safr","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/safr","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.safr-1.0.0.tgz","date":"2026-03-31T15:56:48.000Z","description":"US Situational Awareness Framework for Reporting (US SAFR) (built Wed, Apr 1, 2026 02:56+1100+11:00)"},{"name":"csiro.stars","version":"0.6.0","fhirVersion":"5.0.0","canonical":"https://starsapi.csiro.au/fhir-ig/stars","kind":"fhir.ig","url":"https://packages2.fhir.org/web/csiro.stars-0.6.0.tgz","date":"2026-03-31T20:55:44.000Z","description":"STARS implementation guide (built Wed, Apr 1, 2026 19:55+1100+11:00)"},{"name":"de.gematik.epa.mhd","version":"1.1.2","fhirVersion":"4.0.1","canonical":"https://gematik.de/fhir/epa-mhd","kind":"fhir.ig","url":"https://packages2.fhir.org/web/de.gematik.epa.mhd-1.1.2.tgz","date":"2026-04-01T12:13:55.000Z"},{"name":"hl7.fhir.uv.symptoms","version":"1.0.0","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/uv/symptoms","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.uv.symptoms-1.0.0.tgz","date":"2026-04-01T17:00:21.000Z","description":"A guide that details how to capture and exchange Symptoms data in FHIR (built Thu, Apr 2, 2026 04:00+1100+11:00)"},{"name":"servicewell.fhir.wof-connect","version":"0.1.3","fhirVersion":"4.0.1","canonical":"http://canonical.fhir.link/servicewell/wof-connect","kind":"fhir.ig","url":"https://packages2.fhir.org/web/servicewell.fhir.wof-connect-0.1.3.tgz","date":"2026-04-02T09:20:58.000Z","description":"Service Wells guide for connecting your system to Service Well Portal, delivering smart ways for dental care scheduling. (built Thu, Apr 2, 2026 09:20+0000+00:00)"},{"name":"servicewell.fhir.frenda-wof-connect-flc","version":"0.1.1","fhirVersion":"4.0.1","canonical":"https://canonical.fhir.link/servicewell/frenda-wof-connect-flc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/servicewell.fhir.frenda-wof-connect-flc-0.1.1.tgz","date":"2026-04-02T12:45:00.000Z","description":"Service Well’s FHIR Liquid Conversion (FLC) implementation for Frenda to WOF Connect, enabling template-driven transformation of Frenda data into standards-compliant FHIR (built Thu, Apr 2, 2026 12:45+0000+00:00)"},{"name":"hl7.fhir.us.cql","version":"2.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/cql","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.cql-2.0.0-ballot.tgz","date":"2026-04-03T01:32:37.000Z","description":"This implementation guide contains architectural guidance and re-usable libraries that facilitate the use of Clinical Quality Language (CQL) with FHIR in the US Realm, with an initial use case of Prior Authorization Support Questionnaires as described in the DaVinci Documentation Templates and Rules (DTR) implementation guide. Much of the guidance and content presented here is built on work done in the quality measurement domain, including patterns established by measure developers as part of testing and developing quality measures for use with FHIR. These patterns have been generalized to support US Core as well as harmonized to be usable across use cases. (built Fri, Apr 3, 2026 00:32+1100+11:00)"},{"name":"io.health-samurai.mdm.r5","version":"0.2602.2","fhirVersion":"5.0.0","canonical":"http://health-samurai.io/fhir/mdm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/io.health-samurai.mdm.r5-0.2602.2.tgz","date":"2026-04-03T09:53:54.000Z","description":"Health Samurai MDM (Master Data Management) resources"},{"name":"io.health-samurai.core.r4b","version":"0.2602.2","fhirVersion":"4.3.0","canonical":"http://health-samurai.io/fhir/core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/io.health-samurai.core.r4b-0.2602.2.tgz","date":"2026-04-03T09:53:54.000Z","description":"Health Samurai Aidbox infrastructure resources"},{"name":"io.health-samurai.sdc.r5","version":"0.2602.2","fhirVersion":"5.0.0","canonical":"http://health-samurai.io/fhir/sdc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/io.health-samurai.sdc.r5-0.2602.2.tgz","date":"2026-04-03T09:53:54.000Z","description":"Health Samurai SDC (Structured Data Capture) resources"},{"name":"io.health-samurai.mdm.r4","version":"0.2602.2","fhirVersion":"4.0.1","canonical":"http://health-samurai.io/fhir/mdm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/io.health-samurai.mdm.r4-0.2602.2.tgz","date":"2026-04-03T09:53:54.000Z","description":"Health Samurai MDM (Master Data Management) resources"},{"name":"io.health-samurai.sdc.r4b","version":"0.2602.2","fhirVersion":"4.3.0","canonical":"http://health-samurai.io/fhir/sdc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/io.health-samurai.sdc.r4b-0.2602.2.tgz","date":"2026-04-03T09:53:54.000Z","description":"Health Samurai SDC (Structured Data Capture) resources"},{"name":"io.health-samurai.core.r5","version":"0.2602.2","fhirVersion":"5.0.0","canonical":"http://health-samurai.io/fhir/core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/io.health-samurai.core.r5-0.2602.2.tgz","date":"2026-04-03T09:53:54.000Z","description":"Health Samurai Aidbox infrastructure resources"},{"name":"io.health-samurai.sdc.r3","version":"0.2602.2","fhirVersion":"3.0.2","canonical":"http://health-samurai.io/fhir/sdc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/io.health-samurai.sdc.r3-0.2602.2.tgz","date":"2026-04-03T09:53:54.000Z","description":"Health Samurai SDC (Structured Data Capture) resources"},{"name":"io.health-samurai.sdc.r4","version":"0.2602.2","fhirVersion":"4.0.1","canonical":"http://health-samurai.io/fhir/sdc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/io.health-samurai.sdc.r4-0.2602.2.tgz","date":"2026-04-03T09:53:54.000Z","description":"Health Samurai SDC (Structured Data Capture) resources"},{"name":"io.health-samurai.core.r3","version":"0.2602.2","fhirVersion":"3.0.2","canonical":"http://health-samurai.io/fhir/core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/io.health-samurai.core.r3-0.2602.2.tgz","date":"2026-04-03T09:53:54.000Z","description":"Health Samurai Aidbox infrastructure resources"},{"name":"io.health-samurai.mdm.r3","version":"0.2602.2","fhirVersion":"3.0.2","canonical":"http://health-samurai.io/fhir/mdm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/io.health-samurai.mdm.r3-0.2602.2.tgz","date":"2026-04-03T09:53:54.000Z","description":"Health Samurai MDM (Master Data Management) resources"},{"name":"io.health-samurai.core.r4","version":"0.2602.2","fhirVersion":"4.0.1","canonical":"http://health-samurai.io/fhir/core","kind":"fhir.ig","url":"https://packages2.fhir.org/web/io.health-samurai.core.r4-0.2602.2.tgz","date":"2026-04-03T09:53:54.000Z","description":"Health Samurai Aidbox infrastructure resources"},{"name":"io.health-samurai.mdm.r4b","version":"0.2602.2","fhirVersion":"4.3.0","canonical":"http://health-samurai.io/fhir/mdm","kind":"fhir.ig","url":"https://packages2.fhir.org/web/io.health-samurai.mdm.r4b-0.2602.2.tgz","date":"2026-04-03T09:53:54.000Z","description":"Health Samurai MDM (Master Data Management) resources"},{"name":"hl7.fhir.us.qicore","version":"7.0.2","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/qicore","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.qicore-7.0.2.tgz","date":"2026-04-03T19:52:31.000Z","description":"The QICore Implementation Guide defines a set of FHIR profiles with extensions and bindings needed to create interoperable, quality-focused applications. The profiles in this implementation guide derive from and extend the [US Core](http://hl7.org/fhir/us/core) profiles to provide a common foundation for building, sharing, and evaluating knowledge artifacts across quality improvement efforts in the US Realm. (built Sat, Apr 4, 2026 06:52+1100+11:00)"},{"name":"hl7.fhir.us.carin-rtpbc","version":"2.0.0-ballot","fhirVersion":"4.0.1","canonical":"http://hl7.org/fhir/us/carin-rtpbc","kind":"fhir.ig","url":"https://packages2.fhir.org/web/hl7.fhir.us.carin-rtpbc-2.0.0-ballot.tgz","date":"2026-04-03T20:49:51.000Z","description":"FHIR Implementation Guide for Consumer Real-Time Pharmacy Benefit Check (built Sat, Apr 4, 2026 07:49+1100+11:00)"}]