HL7, Inc FHIR Packages New Packages published by HL7, Inc> http://hl7.org/fhir/package-feed.xml HL7, Inc FHIR Publication tooling Mon, 16 Feb 2026 08:53:45 +1100 Mon, 16 Feb 2026 08:53:45 +1100 en 600 hl7.fhir.uv.tx-ecosystem#1.9.0 Major update - big overhaul to tests for FHIRsmith development http://hl7.org/fhir/uv/tx-ecosystem/1.9.0/package.tgz http://hl7.org/fhir/uv/tx-ecosystem/1.9.0/package.tgz HL7, Inc 5.0.0 IG Mon, 16 Feb 2026 08:53:45 +1100 Publication run at 16/02/2026 by grahamegrieve using Version 2.0.27-SNAPSHOT (Git# 3172ab963c43). Built 2025-11-18T16:05:57.128+11:00 (90 days old) source id Unknown (todo) hl7.fhir.us.health-care-surveys-reporting#2.0.0 STU 2 for National Health Care Surveys, alignment with US Core 6.1.0 / USCDI V3.1 data elements http://hl7.org/fhir/us/health-care-surveys-reporting/STU2/package.tgz http://hl7.org/fhir/us/health-care-surveys-reporting/STU2/package.tgz HL7, Inc 4.0.1 IG Wed, 11 Feb 2026 01:46:23 +0000 Publication run at 11/02/2026 by EC2AMAZ-2MR79IJ using Version 2.1.0 (Git# c044f39673af). Built 2026-02-03T21:34:10.972Z (7 days old) source id Unknown (todo) hl7.fhir.uv.tools.r3#1.0.0 Added term-params-in-artifacts parameter, Added R6 inter-version Requirements parameters,Added requirements-category-vs, add strict-identifiers and toggle-changes parameters http://hl7.org/fhir/tools/1.0.0/hl7.fhir.uv.tools.r3.tgz http://hl7.org/fhir/tools/1.0.0/hl7.fhir.uv.tools.r3.tgz HL7, Inc 3.0.2 IG Wed, 04 Feb 2026 08:29:03 +1100 Publication run at 04/02/2026 by grahamegrieve using Version 2.0.30 (Git# 04ebe87f19c1). Built 2026-01-20T18:29:40.591Z (14 days old) source id Unknown (todo) hl7.fhir.uv.tools.r4#1.0.0 Added term-params-in-artifacts parameter, Added R6 inter-version Requirements parameters,Added requirements-category-vs, add strict-identifiers and toggle-changes parameters http://hl7.org/fhir/tools/1.0.0/hl7.fhir.uv.tools.r4.tgz http://hl7.org/fhir/tools/1.0.0/hl7.fhir.uv.tools.r4.tgz HL7, Inc 4.0.1 IG Wed, 04 Feb 2026 08:29:03 +1100 Publication run at 04/02/2026 by grahamegrieve using Version 2.0.30 (Git# 04ebe87f19c1). Built 2026-01-20T18:29:40.591Z (14 days old) source id Unknown (todo) hl7.fhir.uv.tools.r5#1.0.0 Added term-params-in-artifacts parameter, Added R6 inter-version Requirements parameters,Added requirements-category-vs, add strict-identifiers and toggle-changes parameters http://hl7.org/fhir/tools/1.0.0/hl7.fhir.uv.tools.r5.tgz http://hl7.org/fhir/tools/1.0.0/hl7.fhir.uv.tools.r5.tgz HL7, Inc 5.0.0 IG Wed, 04 Feb 2026 08:29:03 +1100 Publication run at 04/02/2026 by grahamegrieve using Version 2.0.30 (Git# 04ebe87f19c1). Built 2026-01-20T18:29:40.591Z (14 days old) source id Unknown (todo) hl7.fhir.uv.tools#1.0.0 Added term-params-in-artifacts parameter, Added R6 inter-version Requirements parameters,Added requirements-category-vs, add strict-identifiers and toggle-changes parameters http://hl7.org/fhir/tools/1.0.0/package.tgz http://hl7.org/fhir/tools/1.0.0/package.tgz HL7, Inc 5.0.0 IG Wed, 04 Feb 2026 08:29:03 +1100 Publication run at 04/02/2026 by grahamegrieve using Version 2.0.30 (Git# 04ebe87f19c1). Built 2026-01-20T18:29:40.591Z (14 days old) source id Unknown (todo) hl7.fhir.uv.fhir-clinical-document#1.0.1 Technical correction release for FHIR Clinical Documents STU 1. For a detailed list of the changes for this version, see the Change Log: http://hl7.org/fhir/uv/fhir-clinical-document/STU1.0.1/change-log.html http://hl7.org/fhir/uv/fhir-clinical-document/STU1.0.1/package.tgz http://hl7.org/fhir/uv/fhir-clinical-document/STU1.0.1/package.tgz HL7, Inc 4.0.1 IG Fri, 30 Jan 2026 02:13:33 +1100 Publication run at 30/01/2026 by grahamegrieve using Version 2.0.29 (Git# 826a7eb003d6). Built 2025-12-17T01:19:30.102Z (43 days old) source id Unknown (todo) hl7.fhir.uv.symptoms#1.0.0-ballot A guide that details how to capture and exchange Symptoms data in FHIR. http://hl7.org/fhir/uv/symptoms/2026Jan/package.tgz http://hl7.org/fhir/uv/symptoms/2026Jan/package.tgz HL7, Inc 4.0.1 IG Thu, 18 Dec 2025 10:05:34 +0000 Publication run at 18/12/2025 by EC2AMAZ-2MR79IJ using Version 2.0.29 (Git# 826a7eb003d6). Built 2025-12-17T01:19:30.102Z (44 hours old) source id Unknown (todo) hl7.fhir.r6.core#6.0.0-ballot4 FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (built Tue, Apr 1, 2025 12:16+1100+11:00) http://hl7.org/fhir/6.0.0-ballot4/hl7.fhir.r6.core.tgz http://hl7.org/fhir/6.0.0-ballot4/hl7.fhir.r6.core.tgz HL7, Inc 6.0.0-ballot4 fhir.core Thu, 18 Dec 2025 12:00:00 +1100 GMT hl7.fhir.r6.expansions#6.0.0-ballot4 Expansions for the 6.0.0-ballot4 version of the FHIR standard (built Tue, Apr 1, 2025 12:16+1100+11:00) http://hl7.org/fhir/6.0.0-ballot4/hl7.fhir.r6.expansions.tgz http://hl7.org/fhir/6.0.0-ballot4/hl7.fhir.r6.expansions.tgz HL7, Inc 6.0.0-ballot4 fhir.core Thu, 18 Dec 2025 12:00:00 +1100 GMT hl7.fhir.r6.examples#6.0.0-ballot4 Examples for the 6.0.0-ballot4 version of the FHIR standard (built Tue, Apr 1, 2025 12:16+1100+11:00) http://hl7.org/fhir/6.0.0-ballot4/hl7.fhir.r6.examples.tgz http://hl7.org/fhir/6.0.0-ballot4/hl7.fhir.r6.examples.tgz HL7, Inc 6.0.0-ballot4 fhir.core Thu, 18 Dec 2025 12:00:00 +1100 GMT hl7.fhir.r6.search#6.0.0-ballot4 FHIR 6.0.0-ballot4 package : Search Parameters (break out combined parameters for server execution convenience) (built Tue, Apr 1, 2025 12:16+1100+11:00) http://hl7.org/fhir/6.0.0-ballot4/hl7.fhir.r6.search.tgz http://hl7.org/fhir/6.0.0-ballot4/hl7.fhir.r6.search.tgz HL7, Inc 6.0.0-ballot4 fhir.core Thu, 18 Dec 2025 12:00:00 +1100 GMT hl7.fhir.uv.tools.r3#0.9.0 Support for Additional Resources, and various documentation improvements http://hl7.org/fhir/tools/0.9.0/hl7.fhir.uv.tools.r3.tgz http://hl7.org/fhir/tools/0.9.0/hl7.fhir.uv.tools.r3.tgz HL7, Inc 3.0.2 IG Tue, 16 Dec 2025 11:18:40 +1100 Publication run at 16/12/2025 by grahamegrieve using Version 2.0.28 (Git# 6c0c59a855ec). Built 2025-12-08T04:22:21.813Z (8 days old) source id Unknown (todo) hl7.fhir.uv.tools.r4#0.9.0 Support for Additional Resources, and various documentation improvements http://hl7.org/fhir/tools/0.9.0/hl7.fhir.uv.tools.r4.tgz http://hl7.org/fhir/tools/0.9.0/hl7.fhir.uv.tools.r4.tgz HL7, Inc 4.0.1 IG Tue, 16 Dec 2025 11:18:40 +1100 Publication run at 16/12/2025 by grahamegrieve using Version 2.0.28 (Git# 6c0c59a855ec). Built 2025-12-08T04:22:21.813Z (8 days old) source id Unknown (todo) hl7.fhir.uv.tools.r5#0.9.0 Support for Additional Resources, and various documentation improvements http://hl7.org/fhir/tools/0.9.0/hl7.fhir.uv.tools.r5.tgz http://hl7.org/fhir/tools/0.9.0/hl7.fhir.uv.tools.r5.tgz HL7, Inc 5.0.0 IG Tue, 16 Dec 2025 11:18:40 +1100 Publication run at 16/12/2025 by grahamegrieve using Version 2.0.28 (Git# 6c0c59a855ec). Built 2025-12-08T04:22:21.813Z (8 days old) source id Unknown (todo) hl7.fhir.uv.tools#0.9.0 Support for Additional Resources, and various documentation improvements http://hl7.org/fhir/tools/0.9.0/package.tgz http://hl7.org/fhir/tools/0.9.0/package.tgz HL7, Inc 5.0.0 IG Tue, 16 Dec 2025 11:18:40 +1100 Publication run at 16/12/2025 by grahamegrieve using Version 2.0.28 (Git# 6c0c59a855ec). Built 2025-12-08T04:22:21.813Z (8 days old) source id Unknown (todo) hl7.fhir.us.consent-management#1.0.0-ballot A FHIR IG that provides APIs for managing consent at scale across multiple consent management repositories. http://hl7.org/fhir/us/consent-management/2026Jan/package.tgz http://hl7.org/fhir/us/consent-management/2026Jan/package.tgz HL7, Inc 4.0.1 IG Mon, 15 Dec 2025 09:10:40 +0000 Publication run at 15/12/2025 by EC2AMAZ-2MR79IJ using Version 2.0.28 (Git# 6c0c59a855ec). Built 2025-12-08T04:22:21.813Z (7 days old) source id Unknown (todo) hl7.fhir.uv.phenomics-exchange#1.0.0-ballot This publication is for Comment Ballot http://hl7.org/fhir/uv/phenomics-exchange/2026Jan/package.tgz http://hl7.org/fhir/uv/phenomics-exchange/2026Jan/package.tgz HL7, Inc 4.0.1 IG Mon, 15 Dec 2025 05:09:58 +0000 Publication run at 15/12/2025 by EC2AMAZ-2MR79IJ using Version 2.0.28 (Git# 6c0c59a855ec). Built 2025-12-08T04:22:21.813Z (7 days old) source id Unknown (todo) hl7.fhir.us.central-cancer-registry-reporting#2.0.0-ballot This is the STU 2 - Ballot version of the Central Cancer Registry Reporting FHIR IG. http://hl7.org/fhir/us/central-cancer-registry-reporting/2026Jan/package.tgz http://hl7.org/fhir/us/central-cancer-registry-reporting/2026Jan/package.tgz HL7, Inc 4.0.1 IG Mon, 15 Dec 2025 04:01:21 +0000 Publication run at 15/12/2025 by EC2AMAZ-2MR79IJ using Version 2.0.28 (Git# 6c0c59a855ec). Built 2025-12-08T04:22:21.813Z (7 days old) source id Unknown (todo) hl7.fhir.us.sdoh-clinicalcare#3.0.0-ballot STU 3 ballot http://hl7.org/fhir/us/sdoh-clinicalcare/2026Jan/package.tgz http://hl7.org/fhir/us/sdoh-clinicalcare/2026Jan/package.tgz HL7, Inc 4.0.1 IG Sat, 13 Dec 2025 05:11:59 +0000 Publication run at 13/12/2025 by EC2AMAZ-2MR79IJ using Version 2.0.28 (Git# 6c0c59a855ec). Built 2025-12-08T04:22:21.813Z (5 days old) source id Unknown (todo) hl7.fhir.us.ecr#3.0.0-ballot Ballot http://hl7.org/fhir/us/ecr/2026Jan/package.tgz http://hl7.org/fhir/us/ecr/2026Jan/package.tgz HL7, Inc 4.0.1 IG Fri, 12 Dec 2025 04:22:55 +0000 Publication run at 12/12/2025 by EC2AMAZ-2MR79IJ using Version 2.0.28 (Git# 6c0c59a855ec). Built 2025-12-08T04:22:21.813Z (4 days old) source id Unknown (todo) hl7.fhir.us.core#9.0.0-ballot The January 2026 Ballot Version adds United States Core Data for Interoperability (USCDI) V6 updates that the Assistant Secretary for Technology Policy (ASTP) published in July 2025. It also addresses over 50 trackers submitted by implementers since the publication of US Core ver 8.0.0. For a detailed list of the changes for this version, see the Change Notes at http://hl7.org/fhir/us/core/2026Jan/changes.html. http://hl7.org/fhir/us/core/2026Jan/package.tgz http://hl7.org/fhir/us/core/2026Jan/package.tgz HL7, Inc 4.0.1 IG Thu, 11 Dec 2025 09:15:30 +0000 Publication run at 11/12/2025 by EC2AMAZ-2MR79IJ using Version 2.0.28 (Git# 6c0c59a855ec). Built 2025-12-08T04:22:21.813Z (3 days old) source id Unknown (todo) hl7.fhir.uv.bulkdata#3.0.0 STU 3 Publication http://hl7.org/fhir/uv/bulkdata/STU3/package.tgz http://hl7.org/fhir/uv/bulkdata/STU3/package.tgz HL7, Inc 4.0.1 IG Thu, 11 Dec 2025 01:43:06 +0800 Publication run at 11/12/2025 by grahamegrieve using Version 2.0.27-SNAPSHOT (Git# 3172ab963c43). Built 2025-11-18T16:05:57.128+11:00 (23 days old) source id Unknown (todo) hl7.fhir.us.identity-matching#2.0.0 HL7 FHIR Implementation Guide for Interoperable Digital Identity and Patient Matching http://hl7.org/fhir/us/identity-matching/STU2/package.tgz http://hl7.org/fhir/us/identity-matching/STU2/package.tgz HL7, Inc 4.0.1 IG Wed, 10 Dec 2025 04:42:49 +0000 Publication run at 10/12/2025 by EC2AMAZ-2MR79IJ using Version 2.0.28 (Git# 6c0c59a855ec). Built 2025-12-08T04:22:21.813Z (60 hours old) source id Unknown (todo) hl7.fhir.us.core#8.0.1 The changes in this technical correction to US Core have been reviewed and commented upon by the public through the HL7 errata process. The HL7 International Cross-Group Projects work group members have agreed to and voted on the resolution of the community comments. For a detailed list of the changes for this version, see the Change Notes: http://hl7.org/fhir/us/core/STU8/changes.html. http://hl7.org/fhir/us/core/STU8.0.1/package.tgz http://hl7.org/fhir/us/core/STU8.0.1/package.tgz HL7, Inc 4.0.1 IG Wed, 10 Dec 2025 03:47:16 +0500 Publication run at 10/12/2025 by grahamegrieve using Version 2.0.28 (Git# 6c0c59a855ec). Built 2025-12-08T04:22:21.813Z (42 hours old) source id Unknown (todo) hl7.fhir.us.udap-security#2.0.0 UDAP Security IG STU2 http://hl7.org/fhir/us/udap-security/STU2/package.tgz http://hl7.org/fhir/us/udap-security/STU2/package.tgz HL7, Inc 4.0.1 IG Tue, 09 Dec 2025 09:26:54 +0000 Publication run at 09/12/2025 by EC2AMAZ-2MR79IJ using Version 2.0.28 (Git# 6c0c59a855ec). Built 2025-12-08T04:22:21.813Z (41 hours old) source id Unknown (todo) hl7.fhir.uv.aitransparency#1.0.0-ballot This publication is for STU1 Ballot http://hl7.org/fhir/uv/aitransparency/2026Jan/package.tgz http://hl7.org/fhir/uv/aitransparency/2026Jan/package.tgz HL7, Inc 4.0.1 IG Tue, 09 Dec 2025 06:35:29 +0000 Publication run at 09/12/2025 by EC2AMAZ-2MR79IJ using Version 2.0.28 (Git# 6c0c59a855ec). Built 2025-12-08T04:22:21.813Z (38 hours old) source id Unknown (todo) hl7.fhir.us.davinci-vbpr#1.1.0 STU 1.1.0 Release http://hl7.org/fhir/us/davinci-vbpr/STU1.1.0/package.tgz http://hl7.org/fhir/us/davinci-vbpr/STU1.1.0/package.tgz HL7, Inc 4.0.1 IG Mon, 08 Dec 2025 08:55:52 +0000 Publication run at 08/12/2025 by EC2AMAZ-2MR79IJ using Version 2.0.28 (Git# 6c0c59a855ec). Built 2025-12-08T04:22:21.813Z (16 hours old) source id Unknown (todo) hl7.fhir.us.ph-library#2.0.0-snapshot Pre-publication snapshot of STU 2 for Public Health Library, align with USCDI+ Public Health Case Reporting Use Case data elements and update to US Core 6.1.0 http://hl7.org/fhir/us/ph-library/2.0.0-snapshot/package.tgz http://hl7.org/fhir/us/ph-library/2.0.0-snapshot/package.tgz HL7, Inc 4.0.1 IG Mon, 01 Dec 2025 09:57:14 +0300 Publication run at 01/12/2025 by grahamegrieve using Version 2.0.27 (Git# 07050daf807f). Built 2025-11-28T20:03:59.255Z (58 hours old) source id Unknown (todo) hl7.fhir.us.medication-rems#2.0.0 This is the STU2 version of the US Medication REMS FHIR IG. It is sponsored by the HL7 Pharmacy Work Group http://hl7.org/fhir/us/medication-rems/STU2/package.tgz http://hl7.org/fhir/us/medication-rems/STU2/package.tgz HL7, Inc 4.0.1 IG Mon, 17 Nov 2025 08:01:33 +0000 Publication run at 17/11/2025 by EC2AMAZ-2MR79IJ using Version 2.0.26 (Git# 0a43ac207d1f). Built 2025-11-06T09:21:35.314Z (11 days old) source id Unknown (todo) hl7.fhir.us.cql#1.0.0 This 1.0.0 edition is the initial publication of the Common CQL Artifacts for FHIR (US-Based) implementation guide, providing shareable libraries of CQL logic for use with FHIR systems support US Core version 7, 6.1.0, and 3.1.1. http://hl7.org/fhir/us/cql/Informative1/package.tgz http://hl7.org/fhir/us/cql/Informative1/package.tgz HL7, Inc 4.0.1 IG Wed, 22 Oct 2025 08:38:00 +0000 Publication run at 22/10/2025 by EC2AMAZ-2MR79IJ using Version 2.0.22 (Git# 6bbdf7dc5537). Built 2025-10-22T10:27:38.176Z (10 hours old) source id Unknown (todo) hl7.fhir.us.davinci-pct#2.0.0 Da Vinci Patient Cost Transparency Implementation Guide Edition 2, 2.0.0 - US Realm STU http://hl7.org/fhir/us/davinci-pct/STU2/package.tgz http://hl7.org/fhir/us/davinci-pct/STU2/package.tgz HL7, Inc 4.0.1 IG Wed, 08 Oct 2025 08:08:46 +0000 Publication run at 08/10/2025 by EC2AMAZ-2MR79IJ using Version 2.0.19 (Git# e7076c8963f4). Built 2025-10-03T18:07:42.122Z (5 days old) source id Unknown (todo) hl7.fhir.uv.v2mappings#1.0.0 This release is the STU 1 publication of this implementation guide. http://hl7.org/fhir/uv/v2mappings/STU1/package.tgz http://hl7.org/fhir/uv/v2mappings/STU1/package.tgz HL7, Inc 4.0.1 IG Tue, 07 Oct 2025 07:28:41 +0000 Publication run at 07/10/2025 by EC2AMAZ-2MR79IJ using Version 2.0.19 (Git# e7076c8963f4). Built 2025-10-03T18:07:42.122Z (4 days old) source id Unknown (todo) hl7.fhir.uv.ips#2.0.0 This publication is a 2.0.0 STU release, which incorporates implementation feedback, terminology updates, new Alerts and Patient Story sections, converting the IG source to FSH, plus multiple additional updates and publication cleanup. http://hl7.org/fhir/uv/ips/STU2/package.tgz http://hl7.org/fhir/uv/ips/STU2/package.tgz HL7, Inc 4.0.1 IG Fri, 03 Oct 2025 03:47:44 +0000 Publication run at 03/10/2025 by EC2AMAZ-2MR79IJ using Version 2.0.18 (Git# 073deb2e0664). Built 2025-10-01T03:24:07.806Z (60 hours old) source id Unknown (todo) hl7.fhir.us.cancer-reporting#2.0.0 STU 2 Release (v2.0.0) http://hl7.org/fhir/us/cancer-reporting/STU2/package.tgz http://hl7.org/fhir/us/cancer-reporting/STU2/package.tgz HL7, Inc 4.0.1 IG Fri, 03 Oct 2025 02:09:01 +0000 Publication run at 03/10/2025 by EC2AMAZ-2MR79IJ using Version 2.0.18 (Git# 073deb2e0664). Built 2025-10-01T03:24:07.806Z (58 hours old) source id Unknown (todo) hl7.fhir.uv.tx-ecosystem#1.8.0 Rolling Update - see test history http://hl7.org/fhir/uv/tx-ecosystem/1.8.0/package.tgz http://hl7.org/fhir/uv/tx-ecosystem/1.8.0/package.tgz HL7, Inc 5.0.0 IG Mon, 08 Sep 2025 02:10:00 +1000 Publication run at 29/09/2025 by grahamegrieve using Version (unknown) (Git# null). Built null (?vu-duration?) source id Unknown (todo) hl7.fhir.uv.cgm#1.0.0 This is the first version of the Continuous Glucose Monitoring Implementation Guide. http://hl7.org/fhir/uv/cgm/STU1/package.tgz http://hl7.org/fhir/uv/cgm/STU1/package.tgz HL7, Inc 4.0.1 IG Wed, 24 Sep 2025 07:31:12 +0000 Publication run at 24/09/2025 by EC2AMAZ-2MR79IJ using Version 2.0.17 (Git# 98facbadd305). Built 2025-09-09T06:53:45.198Z (15 days old) source id Unknown (todo) hl7.fhir.uv.xver-r2.r4#0.0.1-snapshot-2 Release 1.0.0 0.0.1-snapshot-2 http://hl7.org/fhir/uv/xver-r2.r4/0.0.1-snapshot-2/package.tgz http://hl7.org/fhir/uv/xver-r2.r4/0.0.1-snapshot-2/package.tgz HL7, Inc 4.0.1 IG Thu, 11 Sep 2025 06:58:45 +0000 Published Manually hl7.fhir.uv.xver-r2.r4b#0.0.1-snapshot-2 Release 1.0.0 0.0.1-snapshot-2 http://hl7.org/fhir/uv/xver-r2.r4b/0.0.1-snapshot-2/package.tgz http://hl7.org/fhir/uv/xver-r2.r4b/0.0.1-snapshot-2/package.tgz HL7, Inc 4.0.1 IG Thu, 11 Sep 2025 06:58:45 +0000 Published Manually hl7.fhir.uv.xver-r2.r5#0.0.1-snapshot-2 Release 1.0.0 0.0.1-snapshot-2 http://hl7.org/fhir/uv/xver-r2.r5/0.0.1-snapshot-2/package.tgz http://hl7.org/fhir/uv/xver-r2.r5/0.0.1-snapshot-2/package.tgz HL7, Inc 4.0.1 IG Thu, 11 Sep 2025 06:58:45 +0000 Published Manually hl7.fhir.uv.xver-r3.r4#0.0.1-snapshot-2 Release 1.0.0 0.0.1-snapshot-2 http://hl7.org/fhir/uv/xver-r3.r4/0.0.1-snapshot-2/package.tgz http://hl7.org/fhir/uv/xver-r3.r4/0.0.1-snapshot-2/package.tgz HL7, Inc 4.0.1 IG Thu, 11 Sep 2025 06:58:45 +0000 Published Manually hl7.fhir.uv.xver-r3.r4b#0.0.1-snapshot-2 Release 1.0.0 0.0.1-snapshot-2 http://hl7.org/fhir/uv/xver-r3.r4b/0.0.1-snapshot-2/package.tgz http://hl7.org/fhir/uv/xver-r3.r4b/0.0.1-snapshot-2/package.tgz HL7, Inc 4.0.1 IG Thu, 11 Sep 2025 06:58:45 +0000 Published Manually hl7.fhir.uv.xver-r3.r5#0.0.1-snapshot-2 Release 1.0.0 0.0.1-snapshot-2 http://hl7.org/fhir/uv/xver-r3.r5/0.0.1-snapshot-2/package.tgz http://hl7.org/fhir/uv/xver-r3.r5/0.0.1-snapshot-2/package.tgz HL7, Inc 4.0.1 IG Thu, 11 Sep 2025 06:58:45 +0000 Published Manually hl7.fhir.uv.xver-r4.r4b#0.0.1-snapshot-2 Release 1.0.0 0.0.1-snapshot-2 http://hl7.org/fhir/uv/xver-r4.r4b/0.0.1-snapshot-2/package.tgz http://hl7.org/fhir/uv/xver-r4.r4b/0.0.1-snapshot-2/package.tgz HL7, Inc 4.0.1 IG Thu, 11 Sep 2025 06:58:45 +0000 Published Manually hl7.fhir.uv.xver-r4.r5#0.0.1-snapshot-2 Release 1.0.0 0.0.1-snapshot-2 http://hl7.org/fhir/uv/xver-r4.r5/0.0.1-snapshot-2/package.tgz http://hl7.org/fhir/uv/xver-r4.r5/0.0.1-snapshot-2/package.tgz HL7, Inc 4.0.1 IG Thu, 11 Sep 2025 06:58:45 +0000 Published Manually hl7.fhir.uv.xver-r4b.r4#0.0.1-snapshot-2 Release 1.0.0 0.0.1-snapshot-2 http://hl7.org/fhir/uv/xver-r4b.r4/0.0.1-snapshot-2/package.tgz http://hl7.org/fhir/uv/xver-r4b.r4/0.0.1-snapshot-2/package.tgz HL7, Inc 4.0.1 IG Thu, 11 Sep 2025 06:58:45 +0000 Published Manually hl7.fhir.uv.xver-r4b.r5#0.0.1-snapshot-2 Release 1.0.0 0.0.1-snapshot-2 http://hl7.org/fhir/uv/xver-r4b.r5/0.0.1-snapshot-2/package.tgz http://hl7.org/fhir/uv/xver-r4b.r5/0.0.1-snapshot-2/package.tgz HL7, Inc 4.0.1 IG Thu, 11 Sep 2025 06:58:45 +0000 Published Manually hl7.fhir.uv.xver-r5.r4#0.0.1-snapshot-2 Release 1.0.0 0.0.1-snapshot-2 http://hl7.org/fhir/uv/xver-r5.r4/0.0.1-snapshot-2/package.tgz http://hl7.org/fhir/uv/xver-r5.r4/0.0.1-snapshot-2/package.tgz HL7, Inc 4.0.1 IG Thu, 11 Sep 2025 06:58:45 +0000 Published Manually hl7.fhir.uv.xver-r5.r4b#0.0.1-snapshot-2 Release 1.0.0 0.0.1-snapshot-2 http://hl7.org/fhir/uv/xver-r5.r4b/0.0.1-snapshot-2/package.tgz http://hl7.org/fhir/uv/xver-r5.r4b/0.0.1-snapshot-2/package.tgz HL7, Inc 4.0.1 IG Thu, 11 Sep 2025 06:58:45 +0000 Published Manually hl7.fhir.uv.cqm#1.0.0 Release 1.0.0 STU 1 http://hl7.org/fhir/uv/cqm/STU1/package.tgz http://hl7.org/fhir/uv/cqm/STU1/package.tgz HL7, Inc 4.0.1 IG Thu, 11 Sep 2025 06:58:45 +0000 Publication run at 11/09/2025 by EC2AMAZ-2MR79IJ using Version 2.0.17 (Git# 98facbadd305). Built 2025-09-09T06:53:45.198Z (60 hours old) source id Unknown (todo) hl7.fhir.uv.tx-ecosystem#1.8.0 Rolling Update - see test history http://hl7.org/fhir/uv/tx-ecosystem/1.8.0/package.tgz http://hl7.org/fhir/uv/tx-ecosystem/1.8.0/package.tgz HL7, Inc 5.0.0 IG Mon, 08 Sep 2025 02:10:00 +1000 Publication run at 08/09/2025 by grahamegrieve using Version 2.0.16 (Git# b88a2ed37ef7). Built 2025-08-27T17:19:52.105Z (11 days old) source id Unknown (todo) hl7.fhir.uv.rtls#1.0.0-ballot2 STU 1.0 second ballot http://hl7.org/fhir/uv/rtls/2025Sep/package.tgz http://hl7.org/fhir/uv/rtls/2025Sep/package.tgz HL7, Inc 4.0.1 IG Thu, 07 Aug 2025 05:38:48 +0000 Publication run at 07/08/2025 by EC2AMAZ-2MR79IJ using Version 2.0.13 (Git# bdf473444570). Built 2025-08-07T03:35:38.89Z (14 hours old) source id Unknown (todo) hl7.fhir.us.davinci-crd#2.2.0-ballot STU 2.2.0 Ballot Release http://hl7.org/fhir/us/davinci-crd/2025Sep/package.tgz http://hl7.org/fhir/us/davinci-crd/2025Sep/package.tgz HL7, Inc 4.0.1 IG Wed, 06 Aug 2025 05:27:13 +0000 Publication run at 06/08/2025 by EC2AMAZ-2MR79IJ using Version 2.0.12 (Git# 1e7f5af908a3). Built 2025-07-27T20:11:20.240Z (9 days old) source id Unknown (todo) hl7.fhir.uv.phd#2.0.0-ballot2 STU 2 - 2nd ballot. This version is based on IEEE 11073-10206 - ACOM with Bluetooth GHS support. http://hl7.org/fhir/uv/phd/2025Sep/package.tgz http://hl7.org/fhir/uv/phd/2025Sep/package.tgz HL7, Inc 4.0.1 IG Wed, 06 Aug 2025 02:14:22 +0000 Publication run at 06/08/2025 by EC2AMAZ-2MR79IJ using Version 2.0.12 (Git# 1e7f5af908a3). Built 2025-07-27T20:11:20.240Z (9 days old) source id Unknown (todo) hl7.fhir.uv.tools.r3#0.8.0 More refinements to the CDS Hooks definitions http://hl7.org/fhir/tools/0.8.0/hl7.fhir.uv.tools.r3.tgz http://hl7.org/fhir/tools/0.8.0/hl7.fhir.uv.tools.r3.tgz HL7, Inc 3.0.2 IG Tue, 05 Aug 2025 08:09:06 +1000 Publication run at 05/08/2025 by grahamegrieve using Version 2.0.12 (Git# 1e7f5af908a3). Built 2025-07-27T20:11:20.240Z (8 days old) source id Unknown (todo) hl7.fhir.uv.tools.r4#0.8.0 More refinements to the CDS Hooks definitions http://hl7.org/fhir/tools/0.8.0/hl7.fhir.uv.tools.r4.tgz http://hl7.org/fhir/tools/0.8.0/hl7.fhir.uv.tools.r4.tgz HL7, Inc 4.0.1 IG Tue, 05 Aug 2025 08:09:06 +1000 Publication run at 05/08/2025 by grahamegrieve using Version 2.0.12 (Git# 1e7f5af908a3). Built 2025-07-27T20:11:20.240Z (8 days old) source id Unknown (todo) hl7.fhir.uv.tools.r5#0.8.0 More refinements to the CDS Hooks definitions http://hl7.org/fhir/tools/0.8.0/hl7.fhir.uv.tools.r5.tgz http://hl7.org/fhir/tools/0.8.0/hl7.fhir.uv.tools.r5.tgz HL7, Inc 5.0.0 IG Tue, 05 Aug 2025 08:09:06 +1000 Publication run at 05/08/2025 by grahamegrieve using Version 2.0.12 (Git# 1e7f5af908a3). Built 2025-07-27T20:11:20.240Z (8 days old) source id Unknown (todo) hl7.fhir.uv.tools#0.8.0 More refinements to the CDS Hooks definitions http://hl7.org/fhir/tools/0.8.0/package.tgz http://hl7.org/fhir/tools/0.8.0/package.tgz HL7, Inc 5.0.0 IG Tue, 05 Aug 2025 08:09:06 +1000 Publication run at 05/08/2025 by grahamegrieve using Version 2.0.12 (Git# 1e7f5af908a3). Built 2025-07-27T20:11:20.240Z (8 days old) source id Unknown (todo) hl7.fhir.us.pacio-adi#2.0.0-ballot STU2 Ballot http://hl7.org/fhir/us/pacio-adi/2025Sep/package.tgz http://hl7.org/fhir/us/pacio-adi/2025Sep/package.tgz HL7, Inc 4.0.1 IG Mon, 04 Aug 2025 09:33:15 +0000 Publication run at 04/08/2025 by EC2AMAZ-2MR79IJ using Version 2.0.12 (Git# 1e7f5af908a3). Built 2025-07-27T20:11:20.240Z (8 days old) source id Unknown (todo) hl7.fhir.uv.bulkdata#3.0.0-ballot STU 3 with optional new functionality and additional guidance. Since all of the new capabilities are optional for servers to support and for clients to use, valid Bulk Export STU 2 servers are also valid STU 3 servers and clients that work with STU 2 servers will also work with STU 3 servers. Additional features defined in STU 3 includes include the ability to organize output resources in export files by a focal resource such as Patient instead of by resource type, the ability to return of partial export manifests during an export and after it is complete, an `_until` kickoff parameter, a capability statement extension for servers to indicate supported _typeFilter search parameters, and a Group profile and extension to support the creation of characteristic based cohorts using coarse-grained filters. Clarifications to the `_typeFilter` parameter cover search expression support, boolean logic, and interactions with other filters. Additional guidance covers the use of capability urls and content encoding when providing and retrieving bulk files, and the use of FHIR Groups with Bulk Export. http://hl7.org/fhir/uv/bulkdata/2025Sep/package.tgz http://hl7.org/fhir/uv/bulkdata/2025Sep/package.tgz HL7, Inc 4.0.1 IG Mon, 04 Aug 2025 08:07:54 +0000 Publication run at 04/08/2025 by EC2AMAZ-2MR79IJ using Version 2.0.12 (Git# 1e7f5af908a3). Built 2025-07-27T20:11:20.240Z (7 days old) source id Unknown (todo) hl7.fhir.us.davinci-dtr#2.2.0-ballot STU 2.2.0 Ballot Release http://hl7.org/fhir/us/davinci-dtr/2025Sep/package.tgz http://hl7.org/fhir/us/davinci-dtr/2025Sep/package.tgz HL7, Inc 4.0.1 IG Mon, 04 Aug 2025 03:40:14 +0000 Publication run at 04/08/2025 by EC2AMAZ-2MR79IJ using Version 2.0.12 (Git# 1e7f5af908a3). Built 2025-07-27T20:11:20.240Z (7 days old) source id Unknown (todo) hl7.fhir.us.resp-net#2.0.0-ballot This is the STU 2 - Ballot version of the RESP-NET FHIR IG. http://hl7.org/fhir/us/resp-net/2025Sep/package.tgz http://hl7.org/fhir/us/resp-net/2025Sep/package.tgz HL7, Inc 4.0.1 IG Mon, 04 Aug 2025 01:36:52 +0000 Publication run at 04/08/2025 by EC2AMAZ-2MR79IJ using Version 2.0.12 (Git# 1e7f5af908a3). Built 2025-07-27T20:11:20.240Z (7 days old) source id Unknown (todo) hl7.fhir.uv.extensions.r3#5.3.0-ballot-tc1 Ballot for release 5.3, with an actual technical correction for broken r4 package generation http://hl7.org/fhir/extensions/5.3.0-ballot-tc1/hl7.fhir.uv.extensions.r3.tgz http://hl7.org/fhir/extensions/5.3.0-ballot-tc1/hl7.fhir.uv.extensions.r3.tgz HL7, Inc 3.0.2 IG Sun, 03 Aug 2025 06:28:00 +1000 Publication run at 03/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (45 hours old) source id Unknown (todo) hl7.fhir.uv.extensions.r4#5.3.0-ballot-tc1 Ballot for release 5.3, with an actual technical correction for broken r4 package generation http://hl7.org/fhir/extensions/5.3.0-ballot-tc1/hl7.fhir.uv.extensions.r4.tgz http://hl7.org/fhir/extensions/5.3.0-ballot-tc1/hl7.fhir.uv.extensions.r4.tgz HL7, Inc 4.0.1 IG Sun, 03 Aug 2025 06:28:00 +1000 Publication run at 03/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (45 hours old) source id Unknown (todo) hl7.fhir.uv.extensions.r5#5.3.0-ballot-tc1 Ballot for release 5.3, with an actual technical correction for broken r4 package generation http://hl7.org/fhir/extensions/5.3.0-ballot-tc1/hl7.fhir.uv.extensions.r5.tgz http://hl7.org/fhir/extensions/5.3.0-ballot-tc1/hl7.fhir.uv.extensions.r5.tgz HL7, Inc 5.0.0 IG Sun, 03 Aug 2025 06:28:00 +1000 Publication run at 03/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (45 hours old) source id Unknown (todo) hl7.fhir.uv.extensions#5.3.0-ballot-tc1 Ballot for release 5.3, with an actual technical correction for broken r4 package generation http://hl7.org/fhir/extensions/5.3.0-ballot-tc1/package.tgz http://hl7.org/fhir/extensions/5.3.0-ballot-tc1/package.tgz HL7, Inc 5.0.0 IG Sun, 03 Aug 2025 06:28:00 +1000 Publication run at 03/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (45 hours old) source id Unknown (todo) hl7.fhir.uv.extensions.r3#5.3.0-ballot-tc Ballot for release 5.3, with a technical correction for broken r4 package generation http://hl7.org/fhir/extensions/5.3.0-ballot-tc/hl7.fhir.uv.extensions.r3.tgz http://hl7.org/fhir/extensions/5.3.0-ballot-tc/hl7.fhir.uv.extensions.r3.tgz HL7, Inc 3.0.2 IG Sat, 02 Aug 2025 09:12:59 +1000 Publication run at 02/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (35 hours old) source id Unknown (todo) hl7.fhir.us.cdc-opioid-cpg#1.0.0-ballot Release 1.0.0-ballot STU 1 Ballot http://hl7.org/fhir/us/cdc-opioid-cpg/2025Sep/package.tgz http://hl7.org/fhir/us/cdc-opioid-cpg/2025Sep/package.tgz HL7, Inc 4.0.1 IG Fri, 01 Aug 2025 08:38:22 +0000 Publication run at 01/08/2025 by EC2AMAZ-2MR79IJ using Version 2.0.12 (Git# 1e7f5af908a3). Built 2025-07-27T20:11:20.240Z (5 days old) source id Unknown (todo) hl7.fhir.uv.crmi#2.0.0-ballot STU 2 - Ballot (v2.0.0-ballot) http://hl7.org/fhir/uv/crmi/2025Sep/package.tgz http://hl7.org/fhir/uv/crmi/2025Sep/package.tgz HL7, Inc 4.0.1 IG Fri, 01 Aug 2025 06:39:13 +0000 Publication run at 01/08/2025 by EC2AMAZ-2MR79IJ using Version 2.0.12 (Git# 1e7f5af908a3). Built 2025-07-27T20:11:20.240Z (4 days old) source id Unknown (todo) hl7.fhir.us.qicore#8.0.0-ballot STU 8 - Ballot (v8.0.0-ballot) http://hl7.org/fhir/us/qicore/2025Sep/package.tgz http://hl7.org/fhir/us/qicore/2025Sep/package.tgz HL7, Inc 4.0.1 IG Fri, 01 Aug 2025 03:30:37 +0000 Publication run at 01/08/2025 by EC2AMAZ-2MR79IJ using Version 2.0.12 (Git# 1e7f5af908a3). Built 2025-07-27T20:11:20.240Z (4 days old) source id Unknown (todo) hl7.fhir.uv.pharmaceutical-research-protocol#1.0.0-ballot Initial release http://hl7.org/fhir/uv/pharmaceutical-research-protocol/2025Sep/package.tgz http://hl7.org/fhir/uv/pharmaceutical-research-protocol/2025Sep/package.tgz HL7, Inc 6.0.0 IG Fri, 01 Aug 2025 12:18:30 +0000 Publication run at 01/08/2025 by EC2AMAZ-2MR79IJ using Version 2.0.12 (Git# 1e7f5af908a3). Built 2025-07-27T20:11:20.240Z (4 days old) source id Unknown (todo) hl7.fhir.uv.extensions.r3#5.3.0-ballot Ballot for release 5.3 http://hl7.org/fhir/extensions/5.3.0-ballot/hl7.fhir.uv.extensions.r3.tgz http://hl7.org/fhir/extensions/5.3.0-ballot/hl7.fhir.uv.extensions.r3.tgz HL7, Inc 3.0.2 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions.r4#5.3.0-ballot Ballot for release 5.3 http://hl7.org/fhir/extensions/5.3.0-ballot/hl7.fhir.uv.extensions.r4.tgz http://hl7.org/fhir/extensions/5.3.0-ballot/hl7.fhir.uv.extensions.r4.tgz HL7, Inc 4.0.1 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions.r5#5.3.0-ballot Ballot for release 5.3 http://hl7.org/fhir/extensions/5.3.0-ballot/hl7.fhir.uv.extensions.r5.tgz http://hl7.org/fhir/extensions/5.3.0-ballot/hl7.fhir.uv.extensions.r5.tgz HL7, Inc 5.0.0 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions#5.3.0-ballot Ballot for release 5.3 http://hl7.org/fhir/extensions/5.3.0-ballot/package.tgz http://hl7.org/fhir/extensions/5.3.0-ballot/package.tgz HL7, Inc 5.0.0 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.us.health-care-surveys-reporting#2.0.0-ballot STU 2 for National Health Care Surveys, alignment with US Core 6.1.0 / USCDI V3.0 data elements http://hl7.org/fhir/us/health-care-surveys-reporting/2025Sep/package.tgz http://hl7.org/fhir/us/health-care-surveys-reporting/2025Sep/package.tgz HL7, Inc 4.0.1 IG Thu, 31 Jul 2025 11:11:09 +0000 Publication run at 31/07/2025 by EC2AMAZ-2MR79IJ using Version 2.0.12 (Git# 1e7f5af908a3). Built 2025-07-27T20:11:20.240Z (4 days old) source id Unknown (todo) hl7.fhir.us.medication-rems#2.0.0-ballot This is the STU2 version of the US Medication REMS FHIR IG. It is sponsored by the HL7 Pharmacy Work Group http://hl7.org/fhir/us/medication-rems/2025Sep/package.tgz http://hl7.org/fhir/us/medication-rems/2025Sep/package.tgz HL7, Inc 4.0.1 IG Thu, 31 Jul 2025 05:49:58 +0000 Publication run at 31/07/2025 by EC2AMAZ-2MR79IJ using Version 2.0.12 (Git# 1e7f5af908a3). Built 2025-07-27T20:11:20.240Z (3 days old) source id Unknown (todo) hl7.fhir.uv.cardx-cied#1.0.0-ballot STU 1 for CardX - Cardiac Implantable Electronic Devices, includes managing patient connectivity use case http://hl7.org/fhir/uv/cardx-cied/2025Sep/package.tgz http://hl7.org/fhir/uv/cardx-cied/2025Sep/package.tgz HL7, Inc 5.0.0 IG Thu, 31 Jul 2025 02:23:21 +0000 Publication run at 31/07/2025 by EC2AMAZ-2MR79IJ using Version 2.0.12 (Git# 1e7f5af908a3). Built 2025-07-27T20:11:20.240Z (3 days old) source id Unknown (todo) hl7.fhir.us.ph-library#2.0.0-ballot STU 2 for Public Health Library, align with USCDI+ Public Health Case Reporting Use Case data elements and update to US Core 6.1.0 http://hl7.org/fhir/us/ph-library/2025Sep/package.tgz http://hl7.org/fhir/us/ph-library/2025Sep/package.tgz HL7, Inc 4.0.1 IG Wed, 30 Jul 2025 02:31:09 +0000 Publication run at 30/07/2025 by EC2AMAZ-2MR79IJ using Version 2.0.12 (Git# 1e7f5af908a3). Built 2025-07-27T20:11:20.240Z (66 hours old) source id Unknown (todo) hl7.fhir.us.davinci-pas#2.2.0-ballot This is the first ballot of STU2.2. http://hl7.org/fhir/us/davinci-pas/2025Sep/package.tgz http://hl7.org/fhir/us/davinci-pas/2025Sep/package.tgz HL7, Inc 4.0.1 IG Wed, 30 Jul 2025 12:50:50 +0000 Publication run at 30/07/2025 by EC2AMAZ-2MR79IJ using Version 2.0.12 (Git# 1e7f5af908a3). Built 2025-07-27T20:11:20.240Z (52 hours old) source id Unknown (todo) hl7.fhir.uv.omop#1.0.0-ballot This is the first ballot of the informative release of FHIR OMOP. http://hl7.org/fhir/uv/omop/2025Sep/package.tgz http://hl7.org/fhir/uv/omop/2025Sep/package.tgz HL7, Inc 5.0.0 IG Tue, 29 Jul 2025 09:03:04 +0000 Publication run at 29/07/2025 by EC2AMAZ-2MR79IJ using Version 2.0.12 (Git# 1e7f5af908a3). Built 2025-07-27T20:11:20.240Z (48 hours old) source id Unknown (todo) hl7.fhir.uv.tools.r3#0.7.1 Regenerate IG to include elements missing in R3 and R4 snapshots for CDSHooks content http://hl7.org/fhir/tools/0.7.1/hl7.fhir.uv.tools.r3.tgz http://hl7.org/fhir/tools/0.7.1/hl7.fhir.uv.tools.r3.tgz HL7, Inc 3.0.2 IG Sat, 26 Jul 2025 06:59:02 +1000 Publication run at 26/07/2025 by grahamegrieve using Version 2.0.9-SNAPSHOT (Git# 9eef4da0df2c). Built 2025-07-21T15:16:25.723+10:00 (4 days old) source id Unknown (todo) hl7.fhir.uv.tools.r4#0.7.1 Regenerate IG to include elements missing in R3 and R4 snapshots for CDSHooks content http://hl7.org/fhir/tools/0.7.1/hl7.fhir.uv.tools.r4.tgz http://hl7.org/fhir/tools/0.7.1/hl7.fhir.uv.tools.r4.tgz HL7, Inc 4.0.1 IG Sat, 26 Jul 2025 06:59:02 +1000 Publication run at 26/07/2025 by grahamegrieve using Version 2.0.9-SNAPSHOT (Git# 9eef4da0df2c). Built 2025-07-21T15:16:25.723+10:00 (4 days old) source id Unknown (todo) hl7.fhir.uv.tools.r5#0.7.1 Regenerate IG to include elements missing in R3 and R4 snapshots for CDSHooks content http://hl7.org/fhir/tools/0.7.1/hl7.fhir.uv.tools.r5.tgz http://hl7.org/fhir/tools/0.7.1/hl7.fhir.uv.tools.r5.tgz HL7, Inc 5.0.0 IG Sat, 26 Jul 2025 06:59:02 +1000 Publication run at 26/07/2025 by grahamegrieve using Version 2.0.9-SNAPSHOT (Git# 9eef4da0df2c). Built 2025-07-21T15:16:25.723+10:00 (4 days old) source id Unknown (todo) hl7.fhir.uv.tools#0.7.1 Regenerate IG to include elements missing in R3 and R4 snapshots for CDSHooks content http://hl7.org/fhir/tools/0.7.1/package.tgz http://hl7.org/fhir/tools/0.7.1/package.tgz HL7, Inc 5.0.0 IG Sat, 26 Jul 2025 06:59:02 +1000 Publication run at 26/07/2025 by grahamegrieve using Version 2.0.9-SNAPSHOT (Git# 9eef4da0df2c). Built 2025-07-21T15:16:25.723+10:00 (4 days old) source id Unknown (todo) hl7.fhir.us.pacio-pfe#2.0.0 Personal Functioning and Engagement STU2 http://hl7.org/fhir/us/pacio-pfe/STU2/package.tgz http://hl7.org/fhir/us/pacio-pfe/STU2/package.tgz HL7, Inc 4.0.1 IG Wed, 23 Jul 2025 05:08:40 +0000 Publication run at 23/07/2025 by EC2AMAZ-2MR79IJ using Version 2.0.11 (Git# 321ce468cbb9). Built 2025-07-23T06:49:49.649Z (10 hours old) source id Unknown (todo) hl7.fhir.uv.smart-health-cards-and-links#1.0.0 This is the STU1 version of the SMART Health Cards and Links FHIR IG. It is sponsored by the HL7 FHIR Infrastructure Work Group http://hl7.org/fhir/uv/smart-health-cards-and-links/STU1/package.tgz http://hl7.org/fhir/uv/smart-health-cards-and-links/STU1/package.tgz HL7, Inc 4.0.1 IG Tue, 22 Jul 2025 01:19:59 +0000 Publication run at 22/07/2025 by EC2AMAZ-2MR79IJ using Version 2.0.10 (Git# 62d9b80e6b4e). Built 2025-07-21T13:43:01.341Z (23 hours old) source id Unknown (todo) hl7.fhir.uv.tools.r3#0.7.0 Fix missing context on extension http://hl7.org/fhir/tools/StructureDefinition/snapshot-source, and add missed extension type-profile-style http://hl7.org/fhir/tools/0.7.0/hl7.fhir.uv.tools.r3.tgz http://hl7.org/fhir/tools/0.7.0/hl7.fhir.uv.tools.r3.tgz HL7, Inc 3.0.2 IG Mon, 21 Jul 2025 06:48:45 +1000 Publication run at 21/07/2025 by grahamegrieve using Version 2.0.9-SNAPSHOT (Git# 9eef4da0df2c). Built 2025-07-21T15:16:25.723+10:00 (3 hours old) source id Unknown (todo) hl7.fhir.uv.tools.r4#0.7.0 Fix missing context on extension http://hl7.org/fhir/tools/StructureDefinition/snapshot-source, and add missed extension type-profile-style http://hl7.org/fhir/tools/0.7.0/hl7.fhir.uv.tools.r4.tgz http://hl7.org/fhir/tools/0.7.0/hl7.fhir.uv.tools.r4.tgz HL7, Inc 4.0.1 IG Mon, 21 Jul 2025 06:48:45 +1000 Publication run at 21/07/2025 by grahamegrieve using Version 2.0.9-SNAPSHOT (Git# 9eef4da0df2c). Built 2025-07-21T15:16:25.723+10:00 (3 hours old) source id Unknown (todo) hl7.fhir.uv.tools.r5#0.7.0 Fix missing context on extension http://hl7.org/fhir/tools/StructureDefinition/snapshot-source, and add missed extension type-profile-style http://hl7.org/fhir/tools/0.7.0/hl7.fhir.uv.tools.r5.tgz http://hl7.org/fhir/tools/0.7.0/hl7.fhir.uv.tools.r5.tgz HL7, Inc 5.0.0 IG Mon, 21 Jul 2025 06:48:45 +1000 Publication run at 21/07/2025 by grahamegrieve using Version 2.0.9-SNAPSHOT (Git# 9eef4da0df2c). Built 2025-07-21T15:16:25.723+10:00 (3 hours old) source id Unknown (todo) hl7.fhir.uv.tools#0.7.0 Fix missing context on extension http://hl7.org/fhir/tools/StructureDefinition/snapshot-source, and add missed extension type-profile-style http://hl7.org/fhir/tools/0.7.0/package.tgz http://hl7.org/fhir/tools/0.7.0/package.tgz HL7, Inc 5.0.0 IG Mon, 21 Jul 2025 06:48:45 +1000 Publication run at 21/07/2025 by grahamegrieve using Version 2.0.9-SNAPSHOT (Git# 9eef4da0df2c). Built 2025-07-21T15:16:25.723+10:00 (3 hours old) source id Unknown (todo) hl7.fhir.uv.tools#0.6.0 UML Diagrams, More IG parameters, Revise CDS-Hooks definitions, TestPlan changes, Add snapshot extensions, Deprecate resources moved to the Extensions Pack, and General QA http://hl7.org/fhir/tools/0.6.0/package.tgz http://hl7.org/fhir/tools/0.6.0/package.tgz HL7, Inc 5.0.0 IG Sun, 20 Jul 2025 09:15:46 +1000 Publication run at 20/07/2025 by grahamegrieve using Version 2.0.9-SNAPSHOT (Git# 075070d4d163). Built 2025-07-09T19:09:48.444+10:00 (11 days old) source id Unknown (todo) hl7.fhir.uv.tools.r3#0.6.0 UML Diagrams, More IG parameters, Revise CDS-Hooks definitions, TestPlan changes, Add snapshot extensions, Deprecate resources moved to the Extensions Pack, and General QA http://hl7.org/fhir/tools/0.6.0/hl7.fhir.uv.tools.r3.tgz http://hl7.org/fhir/tools/0.6.0/hl7.fhir.uv.tools.r3.tgz HL7, Inc 3.0.2 IG Sun, 20 Jul 2025 09:15:46 +1000 Publication run at 20/07/2025 by grahamegrieve using Version 2.0.9-SNAPSHOT (Git# 075070d4d163). Built 2025-07-09T19:09:48.444+10:00 (11 days old) source id Unknown (todo) hl7.fhir.uv.tools.r4#0.6.0 UML Diagrams, More IG parameters, Revise CDS-Hooks definitions, TestPlan changes, Add snapshot extensions, Deprecate resources moved to the Extensions Pack, and General QA http://hl7.org/fhir/tools/0.6.0/hl7.fhir.uv.tools.r4.tgz http://hl7.org/fhir/tools/0.6.0/hl7.fhir.uv.tools.r4.tgz HL7, Inc 4.0.1 IG Sun, 20 Jul 2025 09:15:46 +1000 Publication run at 20/07/2025 by grahamegrieve using Version 2.0.9-SNAPSHOT (Git# 075070d4d163). Built 2025-07-09T19:09:48.444+10:00 (11 days old) source id Unknown (todo) hl7.fhir.uv.tools.r5#0.6.0 UML Diagrams, More IG parameters, Revise CDS-Hooks definitions, TestPlan changes, Add snapshot extensions, Deprecate resources moved to the Extensions Pack, and General QA http://hl7.org/fhir/tools/0.6.0/hl7.fhir.uv.tools.r5.tgz http://hl7.org/fhir/tools/0.6.0/hl7.fhir.uv.tools.r5.tgz HL7, Inc 5.0.0 IG Sun, 20 Jul 2025 09:15:46 +1000 Publication run at 20/07/2025 by grahamegrieve using Version 2.0.9-SNAPSHOT (Git# 075070d4d163). Built 2025-07-09T19:09:48.444+10:00 (11 days old) source id Unknown (todo) hl7.fhir.us.qicore#7.0.1 STU7 (v7.0.1) Publication http://hl7.org/fhir/us/qicore/STU7.0.1/package.tgz http://hl7.org/fhir/us/qicore/STU7.0.1/package.tgz HL7, Inc 4.0.1 IG Thu, 17 Jul 2025 04:55:30 +0000 Publication run at 17/07/2025 by EC2AMAZ-2MR79IJ using Version 2.0.9 (Git# 85234fcd604f). Built 2025-07-11T21:09:16.247Z (5 days old) source id Unknown (todo) hl7.fhir.uv.patient-corrections#1.0.0 Patient Request for Corrections Implementation Guide http://hl7.org/fhir/uv/patient-corrections/STU1/package.tgz http://hl7.org/fhir/uv/patient-corrections/STU1/package.tgz HL7, Inc 4.0.1 IG Thu, 10 Jul 2025 03:50:53 +0000 Publication run at 10/07/2025 by EC2AMAZ-2MR79IJ using Version 2.0.8 (Git# e7d965b03a28). Built 2025-06-27T22:18:09.321Z (12 days old) source id Unknown (todo) hl7.fhir.uv.tx-ecosystem#1.7.9 Rolling Update - see test history http://hl7.org/fhir/uv/tx-ecosystem/1.7.9/package.tgz http://hl7.org/fhir/uv/tx-ecosystem/1.7.9/package.tgz HL7, Inc 5.0.0 IG Thu, 10 Jul 2025 10:05:41 +1000 Publication run at 10/07/2025 by grahamegrieve using Version 2.0.9-SNAPSHOT (Git# 075070d4d163). Built 2025-07-09T19:09:48.444+10:00 (26 hours old) source id Unknown (todo) hl7.fhir.uv.tx-ecosystem#1.7.8 Rolling Update - see test history http://hl7.org/fhir/uv/tx-ecosystem/1.7.8/package.tgz http://hl7.org/fhir/uv/tx-ecosystem/1.7.8/package.tgz HL7, Inc 5.0.0 IG Thu, 10 Jul 2025 05:18:33 +1000 Publication run at 10/07/2025 by grahamegrieve using Version 2.0.9-SNAPSHOT (Git# 075070d4d163). Built 2025-07-09T19:09:48.444+10:00 (22 hours old) source id Unknown (todo) hl7.fhir.us.nhsn-dqm#1.0.0 National Healthcare Safety Network (NHSN) using digital quality measures (dQMs), 1.0.0 Ballot - US Realm STU http://hl7.org/fhir/us/nhsn-dqm/STU1/package.tgz http://hl7.org/fhir/us/nhsn-dqm/STU1/package.tgz HL7, Inc 4.0.1 IG Wed, 09 Jul 2025 08:38:10 +0000 Publication run at 09/07/2025 by EC2AMAZ-2MR79IJ using Version 2.0.8 (Git# e7d965b03a28). Built 2025-06-27T22:18:09.321Z (11 days old) source id Unknown (todo) hl7.fhir.uv.cql#2.0.0 STU 2 Release (v2.0.0) http://hl7.org/fhir/uv/cql/STU2/package.tgz http://hl7.org/fhir/uv/cql/STU2/package.tgz HL7, Inc 4.0.1 IG Tue, 08 Jul 2025 02:47:11 +0000 Publication run at 08/07/2025 by EC2AMAZ-2MR79IJ using Version 2.0.8 (Git# e7d965b03a28). Built 2025-06-27T22:18:09.321Z (10 days old) source id Unknown (todo) hl7.fhir.us.pq-cmc-fda#2.0.0 The second implementation guide release. It contains Stage 2 content: Substance Characterisation, Product Batch Formula, and Product Characterisation of Impurities. http://hl7.org/fhir/us/pq-cmc-fda/STU2/package.tgz http://hl7.org/fhir/us/pq-cmc-fda/STU2/package.tgz HL7, Inc 5.0.0 IG Tue, 08 Jul 2025 07:43:10 +0000 Publication run at 08/07/2025 by EC2AMAZ-2MR79IJ using Version 2.0.8 (Git# e7d965b03a28). Built 2025-06-27T22:18:09.321Z (10 days old) source id Unknown (todo) hl7.fhir.uv.tx-ecosystem#1.7.7 Rolling Update - see test history http://hl7.org/fhir/uv/tx-ecosystem/1.7.7/package.tgz http://hl7.org/fhir/uv/tx-ecosystem/1.7.7/package.tgz HL7, Inc 5.0.0 IG Tue, 08 Jul 2025 06:46:33 +1000 Publication run at 08/07/2025 by grahamegrieve using Version (unknown) (Git# null). Built null (?vu-duration?) source id Unknown (todo) hl7.fhir.us.davinci-ra#2.1.0 STU 2.1.0 Release http://hl7.org/fhir/us/davinci-ra/STU2.1/package.tgz http://hl7.org/fhir/us/davinci-ra/STU2.1/package.tgz HL7, Inc 4.0.1 IG Wed, 02 Jul 2025 02:08:34 +0000 Publication run at 02/07/2025 by EC2AMAZ-2MR79IJ using Version 2.0.8 (Git# e7d965b03a28). Built 2025-06-27T22:18:09.321Z (4 days old) source id Unknown (todo) hl7.fhir.uv.fhir-clinical-document#1.0.0 Version for STU 1 FHIR Clinical Documents http://hl7.org/fhir/uv/fhir-clinical-document/STU1/package.tgz http://hl7.org/fhir/uv/fhir-clinical-document/STU1/package.tgz HL7, Inc 4.0.1 IG Thu, 26 Jun 2025 09:24:20 +0000 Publication run at 26/06/2025 by EC2AMAZ-2MR79IJ using Version 2.0.7 (Git# f2fdf4e51a8d). Built 2025-06-14T10:53:27.183Z (12 days old) source id Unknown (todo) hl7.fhir.us.resp-net#1.0.0 This is the STU 1 of the RESP-NET FHIR IG. http://hl7.org/fhir/us/resp-net/STU1/package.tgz http://hl7.org/fhir/us/resp-net/STU1/package.tgz HL7, Inc 4.0.1 IG Thu, 19 Jun 2025 09:49:45 +0000 Publication run at 19/06/2025 by EC2AMAZ-2MR79IJ using Version 2.0.7 (Git# f2fdf4e51a8d). Built 2025-06-14T10:53:27.183Z (5 days old) source id Unknown (todo) hl7.fhir.us.qicore#7.0.0 STU7 (v7.0.0) Publication http://hl7.org/fhir/us/qicore/STU7/package.tgz http://hl7.org/fhir/us/qicore/STU7/package.tgz HL7, Inc 4.0.1 IG Wed, 18 Jun 2025 10:12:13 +0000 Publication run at 18/06/2025 by EC2AMAZ-2MR79IJ using Version 2.0.7 (Git# f2fdf4e51a8d). Built 2025-06-14T10:53:27.183Z (4 days old) source id Unknown (todo) hl7.fhir.us.davinci-pdex#2.1.0 This STU 2.1 specification has undergone ballot and connectathon testing. It has been evolved to meet the requirements of the Advancing Interoperability and Prior Authorization rule. As part of that process. Feedback is welcome and may be submitted through the FHIR JIRA tracker indicating US Da Vinci PDex as the specification. http://hl7.org/fhir/us/davinci-pdex/STU2.1/package.tgz http://hl7.org/fhir/us/davinci-pdex/STU2.1/package.tgz HL7, Inc 4.0.1 IG Wed, 18 Jun 2025 12:57:14 +0000 Publication run at 18/06/2025 by EC2AMAZ-2MR79IJ using Version 2.0.7 (Git# f2fdf4e51a8d). Built 2025-06-14T10:53:27.183Z (3 days old) source id Unknown (todo) hl7.fhir.us.core#8.0.0 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. These 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 15:32+0000+00:00) http://hl7.org/fhir/us/core/STU8/package.tgz http://hl7.org/fhir/us/core/STU8/package.tgz HL7, Inc 4.0.1 IG Tue, 10 Jun 2025 12:00:00 +1000 GMT hl7.fhir.us.davinci-deqm#5.0.0 http://hl7.org/fhir/us/davinci-deqm/STU5/package.tgz http://hl7.org/fhir/us/davinci-deqm/STU5/package.tgz HL7, Inc 4.0.1 IG Mon, 19 May 2025 12:00:00 +1000 GMT hl7.fhir.us.davinci-atr#2.1.0 Exchange of member attribution list between payers and providers (built Fri, May 16, 2025 16:00+0000+00:00) http://hl7.org/fhir/us/davinci-atr/STU2.1/package.tgz http://hl7.org/fhir/us/davinci-atr/STU2.1/package.tgz HL7, Inc 4.0.1 IG Fri, 16 May 2025 12:00:00 +1000 GMT hl7.fhir.us.smp#1.0.0 Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Fri, May 16, 2025 20:17+0000+00:00) http://hl7.org/fhir/us/smp/STU1/package.tgz http://hl7.org/fhir/us/smp/STU1/package.tgz HL7, Inc 4.0.1 IG Fri, 16 May 2025 12:00:00 +1000 GMT hl7.fhir.us.mdi#2.0.0 http://hl7.org/fhir/us/mdi/STU2/package.tgz http://hl7.org/fhir/us/mdi/STU2/package.tgz HL7, Inc 4.0.1 IG Thu, 15 May 2025 12:00:00 +1000 GMT hl7.fhir.us.sdoh-clinicalcare#2.3.0 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 19:58+0000+00:00) http://hl7.org/fhir/us/sdoh-clinicalcare/STU2.3/package.tgz http://hl7.org/fhir/us/sdoh-clinicalcare/STU2.3/package.tgz HL7, Inc 4.0.1 IG Thu, 15 May 2025 12:00:00 +1000 GMT hl7.fhir.us.ndh#1.0.0 http://hl7.org/fhir/us/ndh/STU1/package.tgz http://hl7.org/fhir/us/ndh/STU1/package.tgz HL7, Inc 4.0.1 IG Thu, 10 Apr 2025 12:00:00 +1000 GMT hl7.fhir.us.davinci-alerts#1.1.0 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) http://hl7.org/fhir/us/davinci-alerts/STU1.1/package.tgz http://hl7.org/fhir/us/davinci-alerts/STU1.1/package.tgz HL7, Inc 4.0.1 IG Tue, 08 Apr 2025 12:00:00 +1000 GMT hl7.fhir.us.davinci-pr#1.0.0 http://hl7.org/fhir/us/davinci-pr/STU1/package.tgz http://hl7.org/fhir/us/davinci-pr/STU1/package.tgz HL7, Inc 4.0.1 IG Tue, 08 Apr 2025 12:00:00 +1000 GMT hl7.fhir.uv.cow#1.0.0-ballot An Implementation Guide providing the foundational guidance for order-based workflow FHIR interoperability (built Mon, Apr 7, 2025 15:35+0000+00:00) http://hl7.org/fhir/uv/cow/2025May/package.tgz http://hl7.org/fhir/uv/cow/2025May/package.tgz HL7, Inc 4.0.1 IG Mon, 07 Apr 2025 12:00:00 +1000 GMT hl7.fhir.r6.core#6.0.0-ballot3 FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (built Tue, Apr 1, 2025 12:16+1100+11:00) http://hl7.org/fhir/6.0.0-ballot3/hl7.fhir.r6.core.tgz http://hl7.org/fhir/6.0.0-ballot3/hl7.fhir.r6.core.tgz HL7, Inc 6.0.0-ballot3 fhir.core Thu, 03 Apr 2025 12:00:00 +1100 GMT hl7.fhir.r6.expansions#6.0.0-ballot3 Expansions for the 6.0.0-ballot3 version of the FHIR standard (built Tue, Apr 1, 2025 12:16+1100+11:00) http://hl7.org/fhir/6.0.0-ballot3/hl7.fhir.r6.expansions.tgz http://hl7.org/fhir/6.0.0-ballot3/hl7.fhir.r6.expansions.tgz HL7, Inc 6.0.0-ballot3 fhir.core Thu, 03 Apr 2025 12:00:00 +1100 GMT hl7.fhir.r6.examples#6.0.0-ballot3 Examples for the 6.0.0-ballot3 version of the FHIR standard (built Tue, Apr 1, 2025 12:16+1100+11:00) http://hl7.org/fhir/6.0.0-ballot3/hl7.fhir.r6.examples.tgz http://hl7.org/fhir/6.0.0-ballot3/hl7.fhir.r6.examples.tgz HL7, Inc 6.0.0-ballot3 fhir.core Thu, 03 Apr 2025 12:00:00 +1100 GMT hl7.fhir.r6.search#6.0.0-ballot3 FHIR 6.0.0-ballot3 package : Search Parameters (break out combined parameters for server execution convenience) (built Tue, Apr 1, 2025 12:16+1100+11:00) http://hl7.org/fhir/6.0.0-ballot3/hl7.fhir.r6.search.tgz http://hl7.org/fhir/6.0.0-ballot3/hl7.fhir.r6.search.tgz HL7, Inc 6.0.0-ballot3 fhir.core Thu, 03 Apr 2025 12:00:00 +1100 GMT hl7.fhir.uv.phr#1.0.0-ballot2 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) http://hl7.org/fhir/uv/phr/2025May/package.tgz http://hl7.org/fhir/uv/phr/2025May/package.tgz HL7, Inc 4.0.1 IG Thu, 03 Apr 2025 12:00:00 +1100 GMT hl7.fhir.us.cql#1.0.0-ballot This implementation guide contains common CQL assets for use with FHIR in US-realm environments, including the USCore-ModelInfo and USCommon libraries. (built Tue, Apr 1, 2025 14:00+0000+00:00) http://hl7.org/fhir/us/cql/2025May/package.tgz http://hl7.org/fhir/us/cql/2025May/package.tgz HL7, Inc 4.0.1 IG Tue, 01 Apr 2025 12:00:00 +1100 GMT hl7.fhir.us.cancer-reporting#2.0.0-ballot 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 Mon, Mar 31, 2025 19:51+0000+00:00) http://hl7.org/fhir/us/cancer-reporting/2025May/package.tgz http://hl7.org/fhir/us/cancer-reporting/2025May/package.tgz HL7, Inc 4.0.1 IG Mon, 31 Mar 2025 12:00:00 +1100 GMT hl7.fhir.uv.cgm#1.0.0-ballot Communicate Continuous Glucose Monitoring (CGM) data using FHIR (built Mon, Mar 31, 2025 13:42+0000+00:00) http://hl7.org/fhir/uv/cgm/2025May/package.tgz http://hl7.org/fhir/uv/cgm/2025May/package.tgz HL7, Inc 4.0.1 IG Mon, 31 Mar 2025 12:00:00 +1100 GMT hl7.fhir.us.mdi#2.0.0-snapshot2 http://hl7.org/fhir/us/mdi/2.0.0-snapshot2/package.tgz http://hl7.org/fhir/us/mdi/2.0.0-snapshot2/package.tgz HL7, Inc 4.0.1 IG Fri, 28 Mar 2025 12:00:00 +1100 GMT hl7.fhir.us.pacio-toc#1.0.0-ballot 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) http://hl7.org/fhir/us/pacio-toc/2025May/package.tgz http://hl7.org/fhir/us/pacio-toc/2025May/package.tgz HL7, Inc 4.0.1 IG Fri, 28 Mar 2025 12:00:00 +1100 GMT hl7.fhir.us.pco#1.0.0-ballot Person-Centered Outcomes (PCO) FHIR Implementation Guide (built Fri, Mar 28, 2025 21:02+0000+00:00) http://hl7.org/fhir/us/pco/2025May/package.tgz http://hl7.org/fhir/us/pco/2025May/package.tgz HL7, Inc 4.0.1 IG Fri, 28 Mar 2025 12:00:00 +1100 GMT hl7.fhir.us.safr#1.0.0-ballot US Situational Awareness Framework for Reporting (US SAFR) (built Fri, Mar 28, 2025 19:37+0000+00:00) http://hl7.org/fhir/us/safr/2025May/package.tgz http://hl7.org/fhir/us/safr/2025May/package.tgz HL7, Inc 4.0.1 IG Fri, 28 Mar 2025 12:00:00 +1100 GMT hl7.fhir.uv.ebm#1.0.0-ballot2 http://hl7.org/fhir/uv/ebm/2025May/package.tgz http://hl7.org/fhir/uv/ebm/2025May/package.tgz HL7, Inc 6.0.0 IG Fri, 28 Mar 2025 12:00:00 +1100 GMT hl7.fhir.us.womens-health-registries#0.2.0-withdrawal http://hl7.org/fhir/us/womens-health-registries/0.2.0-withdrawal/package.tgz http://hl7.org/fhir/us/womens-health-registries/0.2.0-withdrawal/package.tgz HL7, Inc 4.0.1 IG Mon, 24 Mar 2025 12:00:00 +1100 GMT hl7.fhir.uv.ipa#1.1.0 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) http://hl7.org/fhir/uv/ipa/STU1.1/package.tgz http://hl7.org/fhir/uv/ipa/STU1.1/package.tgz HL7, Inc 4.0.1 IG Wed, 19 Mar 2025 12:00:00 +1100 GMT hl7.fhir.us.davinci-drug-formulary#2.1.0 DaVinci Payer Data Exchange (PDex) US Drug Formulary" (built Wed, Feb 26, 2025 17:11+0000+00:00) http://hl7.org/fhir/us/davinci-drug-formulary/STU2.1/package.tgz http://hl7.org/fhir/us/davinci-drug-formulary/STU2.1/package.tgz HL7, Inc 4.0.1 IG Wed, 26 Feb 2025 12:00:00 +1100 GMT hl7.fhir.uv.tx-ecosystem#1.7.6 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 Wed, Feb 26, 2025 17:18+1100+11:00) http://hl7.org/fhir/uv/tx-ecosystem/1.7.6/package.tgz http://hl7.org/fhir/uv/tx-ecosystem/1.7.6/package.tgz HL7, Inc 5.0.0 IG Wed, 26 Feb 2025 12:00:00 +1100 GMT hl7.fhir.us.davinci-pdex-plan-net#1.2.0 Da Vinci PDex Plan Net (built Tue, Feb 25, 2025 19:12+0000+00:00) http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.2/package.tgz http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.2/package.tgz HL7, Inc 4.0.1 IG Tue, 25 Feb 2025 12:00:00 +1100 GMT hl7.fhir.us.davinci-ra#2.0.0 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, Feb 19, 2025 15:09+0000+00:00) http://hl7.org/fhir/us/davinci-ra/STU2/package.tgz http://hl7.org/fhir/us/davinci-ra/STU2/package.tgz HL7, Inc 4.0.1 IG Wed, 19 Feb 2025 12:00:00 +1100 GMT hl7.fhir.us.carin-bb#2.1.0 CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) (built Tue, Feb 18, 2025 17:31+0000+00:00) http://hl7.org/fhir/us/carin-bb/STU2.1/package.tgz http://hl7.org/fhir/us/carin-bb/STU2.1/package.tgz HL7, Inc 4.0.1 IG Tue, 18 Feb 2025 12:00:00 +1100 GMT hl7.fhir.us.codex-radiation-therapy#2.0.0 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:18+0000+00:00) http://hl7.org/fhir/us/codex-radiation-therapy/STU2/package.tgz http://hl7.org/fhir/us/codex-radiation-therapy/STU2/package.tgz HL7, Inc 4.0.1 IG Tue, 18 Feb 2025 12:00:00 +1100 GMT hl7.fhir.uv.vhdir#1.0.0 This is a Healthedata1 sandbox for creation of resources and examples (built Tue, Feb 18, 2025 15:14+0000+00:00) http://hl7.org/fhir/uv/vhdir/STU1/package.tgz http://hl7.org/fhir/uv/vhdir/STU1/package.tgz HL7, Inc 4.0.1 IG Tue, 18 Feb 2025 12:00:00 +1100 GMT hl7.fhir.us.mcode#4.0.0 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 19:03+0000+00:00) http://hl7.org/fhir/us/mcode/STU4/package.tgz http://hl7.org/fhir/us/mcode/STU4/package.tgz HL7, Inc 4.0.1 IG Sun, 16 Feb 2025 12:00:00 +1100 GMT hl7.fhir.us.davinci-cdex#2.1.0 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) http://hl7.org/fhir/us/davinci-cdex/STU2.1/package.tgz http://hl7.org/fhir/us/davinci-cdex/STU2.1/package.tgz HL7, Inc 4.0.1 IG Tue, 11 Feb 2025 12:00:00 +1100 GMT hl7.fhir.uv.tx-ecosystem#1.7.5 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 Fri, Feb 7, 2025 13:58-0500-05:00) http://hl7.org/fhir/uv/tx-ecosystem/1.7.5/package.tgz http://hl7.org/fhir/uv/tx-ecosystem/1.7.5/package.tgz HL7, Inc 5.0.0 IG Fri, 07 Feb 2025 12:00:00 +1100 GMT hl7.fhir.us.davinci-dtr#2.1.0 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 Sat, Dec 21, 2024 15:48+0000+00:00) http://hl7.org/fhir/us/davinci-dtr/STU2.1/package.tgz http://hl7.org/fhir/us/davinci-dtr/STU2.1/package.tgz HL7, Inc 4.0.1 IG Sat, 21 Dec 2024 12:00:00 +1100 GMT hl7.fhir.us.davinci-pas#2.1.0 Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Fri, Dec 20, 2024 21:03+0000+00:00) http://hl7.org/fhir/us/davinci-pas/STU2.1/package.tgz http://hl7.org/fhir/us/davinci-pas/STU2.1/package.tgz HL7, Inc 4.0.1 IG Fri, 20 Dec 2024 12:00:00 +1100 GMT hl7.fhir.us.ccda#2.0.0-ballot 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. This 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). The 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. We 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. ### Scope To represent Consolidated CDA Templates for Clinical Notes (C-CDA) 2.1 templates using FHIR profiles. This first stage of the project defines all the C-CDA document-level profiles on the Composition resource and contained sections. Any 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. For 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) http://hl7.org/fhir/us/ccda/2025Jan/package.tgz http://hl7.org/fhir/us/ccda/2025Jan/package.tgz HL7, Inc 4.0.1 IG Tue, 17 Dec 2024 12:00:00 +1100 GMT hl7.fhir.us.udap-security#2.0.0-ballot 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) http://hl7.org/fhir/us/udap-security/2025Jan/package.tgz http://hl7.org/fhir/us/udap-security/2025Jan/package.tgz HL7, Inc 4.0.1 IG Tue, 17 Dec 2024 12:00:00 +1100 GMT hl7.fhir.uv.sdc#4.0.0-ballot 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) http://hl7.org/fhir/uv/sdc/2025Jan/package.tgz http://hl7.org/fhir/uv/sdc/2025Jan/package.tgz HL7, Inc 4.0.1 IG Tue, 17 Dec 2024 12:00:00 +1100 GMT hl7.fhir.us.davinci-pr#1.0.0-ballot http://hl7.org/fhir/us/davinci-pr/2025Jan/package.tgz http://hl7.org/fhir/us/davinci-pr/2025Jan/package.tgz HL7, Inc 4.0.1 IG Mon, 16 Dec 2024 12:00:00 +1100 GMT hl7.fhir.uv.cql#2.0.0-ballot 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 Mon, Dec 16, 2024 21:01+0000+00:00) http://hl7.org/fhir/uv/cql/2025Jan/package.tgz http://hl7.org/fhir/uv/cql/2025Jan/package.tgz HL7, Inc 4.0.1 IG Mon, 16 Dec 2024 12:00:00 +1100 GMT hl7.fhir.uv.cqm#1.0.0-ballot 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, Dec 16, 2024 21:47+0000+00:00) http://hl7.org/fhir/uv/cqm/2025Jan/package.tgz http://hl7.org/fhir/uv/cqm/2025Jan/package.tgz HL7, Inc 4.0.1 IG Mon, 16 Dec 2024 12:00:00 +1100 GMT hl7.fhir.us.core#8.0.0-ballot 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. These 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 Fri, Dec 13, 2024 16:53+0000+00:00) http://hl7.org/fhir/us/core/2025Jan/package.tgz http://hl7.org/fhir/us/core/2025Jan/package.tgz HL7, Inc 4.0.1 IG Fri, 13 Dec 2024 12:00:00 +1100 GMT hl7.fhir.us.mdi#2.0.0-ballot2 http://hl7.org/fhir/us/mdi/2025Jan/package.tgz http://hl7.org/fhir/us/mdi/2025Jan/package.tgz HL7, Inc 4.0.1 IG Thu, 12 Dec 2024 12:00:00 +1100 GMT hl7.fhir.us.pq-cmc-fda#2.0.0-ballot 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 Thu, Dec 12, 2024 18:53+0000+00:00) http://hl7.org/fhir/us/pq-cmc-fda/2025Jan/package.tgz http://hl7.org/fhir/us/pq-cmc-fda/2025Jan/package.tgz HL7, Inc 5.0.0 IG Thu, 12 Dec 2024 12:00:00 +1100 GMT hl7.fhir.uv.cardx-htn-mng#1.0.0 http://hl7.org/fhir/uv/cardx-htn-mng/STU1/package.tgz http://hl7.org/fhir/uv/cardx-htn-mng/STU1/package.tgz HL7, Inc 4.0.1 IG Thu, 12 Dec 2024 12:00:00 +1100 GMT hl7.fhir.uv.genomics-reporting#3.0.0 Guidelines for reporting of clinical genomics results using HL7 FHIR. (built Thu, Dec 12, 2024 20:34+0000+00:00) http://hl7.org/fhir/uv/genomics-reporting/STU3/package.tgz http://hl7.org/fhir/uv/genomics-reporting/STU3/package.tgz HL7, Inc 4.0.1 IG Thu, 12 Dec 2024 12:00:00 +1100 GMT hl7.fhir.us.davinci-alerts#1.1.0-preview 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 Wed, Dec 11, 2024 19:02+1100+11:00) http://hl7.org/fhir/us/davinci-alerts/STU1.1-snapshot/package.tgz http://hl7.org/fhir/us/davinci-alerts/STU1.1-snapshot/package.tgz HL7, Inc 4.0.1 IG Wed, 11 Dec 2024 12:00:00 +1100 GMT hl7.fhir.us.davinci-crd#2.1.0 Guidelines for conveying coverage requirements to clinicians when planning treatment (built Wed, Dec 11, 2024 18:43+0000+00:00) http://hl7.org/fhir/us/davinci-crd/STU2.1/package.tgz http://hl7.org/fhir/us/davinci-crd/STU2.1/package.tgz HL7, Inc 4.0.1 IG Wed, 11 Dec 2024 12:00:00 +1100 GMT hl7.fhir.us.pq-cmc-fda#1.0.0 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 Wed, Dec 11, 2024 13:39+0000+00:00) http://hl7.org/fhir/us/pq-cmc-fda/STU1/package.tgz http://hl7.org/fhir/us/pq-cmc-fda/STU1/package.tgz HL7, Inc 5.0.0 IG Wed, 11 Dec 2024 12:00:00 +1100 GMT hl7.fhir.us.davinci-hrex#1.1.0 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 16:43+0000+00:00) http://hl7.org/fhir/us/davinci-hrex/STU1.1/package.tgz http://hl7.org/fhir/us/davinci-hrex/STU1.1/package.tgz HL7, Inc 4.0.1 IG Tue, 10 Dec 2024 12:00:00 +1100 GMT hl7.fhir.uv.cpg#2.0.0 Implementation guidance for creating Clinical Practice Guidelines with formal artifacts to facilitate sharing and implementation of the guideline (built Tue, Nov 26, 2024 16:14+0000+00:00) http://hl7.org/fhir/uv/cpg/STU2/package.tgz http://hl7.org/fhir/uv/cpg/STU2/package.tgz HL7, Inc 4.0.1 IG Tue, 26 Nov 2024 12:00:00 +1100 GMT hl7.fhir.us.cqfmeasures#5.0.0 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) http://hl7.org/fhir/us/cqfmeasures/STU5/package.tgz http://hl7.org/fhir/us/cqfmeasures/STU5/package.tgz HL7, Inc 4.0.1 IG Mon, 04 Nov 2024 12:00:00 +1100 GMT hl7.fhir.us.ecr#2.1.2 # Introduction and Purpose With 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. With 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. For 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). For Clinical Safety Information please refer to the [FHIR Implementer’s Safety Checklist](http://hl7.org/fhir/safety.html). <div style="background-color: #ffffcc; border-left: 6px solid #ffeb3b;"> <p><b>Known Issue:</b></p> <p>The following issue is related to a publication tooling issue. A technical correction is planned once the tooling issue has been addressed.</p> <ul> <li><a href="https://jira.hl7.org/browse/FHIR-30477" rel="external" target="_blank">FHIR-30477</a>: Resolution errors for FHIRHelpers and FHIR-ModelInfo.</li> </ul> </div> # Stakeholders * Regulatory Agencies * Standards Development Organizations * Vendors: EHR, PHR; Health Care IT; Clinical Decision Support Systems, Public Health Surveillance Systems * Providers: Ambulatory and Healthcare Institutions (hospitals, long term care, mental health) * Local, State, Tribal and Federal Public Health Agencies (built Wed, Oct 30, 2024 19:49+0000+00:00) http://hl7.org/fhir/us/ecr/2.1.2/package.tgz http://hl7.org/fhir/us/ecr/2.1.2/package.tgz HL7, Inc 4.0.1 IG Wed, 30 Oct 2024 12:00:00 +1100 GMT hl7.fhir.uv.phd#1.1.0 ImplementationGuide for Personal Health Devices (PHD), used in remote patient monitoring (e.g., weight scales, blood pressure cuffs, glucose monitors, pulse-oximeters, etc.). (built Fri, Oct 18, 2024 13:22+0000+00:00) http://hl7.org/fhir/uv/phd/STU1.1/package.tgz http://hl7.org/fhir/uv/phd/STU1.1/package.tgz HL7, Inc 4.0.1 IG Fri, 18 Oct 2024 12:00:00 +1100 GMT hl7.fhir.us.vrdr#3.0.0 http://hl7.org/fhir/us/vrdr/STU3/package.tgz http://hl7.org/fhir/us/vrdr/STU3/package.tgz HL7, Inc 4.0.1 IG Wed, 16 Oct 2024 12:00:00 +1100 GMT hl7.fhir.us.bfdr#2.0.0 http://hl7.org/fhir/us/bfdr/STU2/package.tgz http://hl7.org/fhir/us/bfdr/STU2/package.tgz HL7, Inc 4.0.1 IG Tue, 15 Oct 2024 12:00:00 +1100 GMT hl7.fhir.us.pdmp#1.0.0 US Prescription Drug Monitoring Program (PDMP) FHIR IG (built Tue, Oct 15, 2024 18:20+0000+00:00) http://hl7.org/fhir/us/pdmp/STU1/package.tgz http://hl7.org/fhir/us/pdmp/STU1/package.tgz HL7, Inc 4.0.1 IG Tue, 15 Oct 2024 12:00:00 +1100 GMT hl7.fhir.us.vr-common-library#2.0.0 http://hl7.org/fhir/us/vr-common-library/STU2/package.tgz http://hl7.org/fhir/us/vr-common-library/STU2/package.tgz HL7, Inc 4.0.1 IG Fri, 11 Oct 2024 12:00:00 +1100 GMT hl7.fhir.us.davinci-cdex#2.1.0-snapshot 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) http://hl7.org/fhir/us/davinci-cdex/STU2.1-snapshot/package.tgz http://hl7.org/fhir/us/davinci-cdex/STU2.1-snapshot/package.tgz HL7, Inc 4.0.1 IG Sat, 28 Sep 2024 12:00:00 +1000 GMT hl7.fhir.us.davinci-dtr#2.1.0-preview 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, Sep 27, 2024 06:27-0400-04:00) http://hl7.org/fhir/us/davinci-dtr/2.1.0-preview/package.tgz http://hl7.org/fhir/us/davinci-dtr/2.1.0-preview/package.tgz HL7, Inc 4.0.1 IG Fri, 27 Sep 2024 12:00:00 +1000 GMT hl7.fhir.us.davinci-crd#2.1.0-preview Guidelines for conveying coverage requirements to clinicians when planning treatment (built Thu, Sep 26, 2024 14:58-0400-04:00) http://hl7.org/fhir/us/davinci-crd/STU2.1-preview/package.tgz http://hl7.org/fhir/us/davinci-crd/STU2.1-preview/package.tgz HL7, Inc 4.0.1 IG Thu, 26 Sep 2024 12:00:00 +1000 GMT hl7.fhir.us.davinci-pas#2.1.0-preview Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Thu, Sep 26, 2024 18:54-0400-04:00) http://hl7.org/fhir/us/davinci-pas/2.1.0-preview/package.tgz http://hl7.org/fhir/us/davinci-pas/2.1.0-preview/package.tgz HL7, Inc 4.0.1 IG Thu, 26 Sep 2024 12:00:00 +1000 GMT hl7.fhir.us.davinci-deqm#5.0.0-ballot http://hl7.org/fhir/us/davinci-deqm/2024Sep/package.tgz http://hl7.org/fhir/us/davinci-deqm/2024Sep/package.tgz HL7, Inc 4.0.1 IG Tue, 27 Aug 2024 12:00:00 +1000 GMT hl7.fhir.us.sdoh-clinicalcare#2.2.0 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 Tue, Aug 27, 2024 16:48+0000+00:00) http://hl7.org/fhir/us/sdoh-clinicalcare/STU2.2/package.tgz http://hl7.org/fhir/us/sdoh-clinicalcare/STU2.2/package.tgz HL7, Inc 4.0.1 IG Tue, 27 Aug 2024 12:00:00 +1000 GMT hl7.fhir.us.udap-security#1.1.0 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 Wed, Aug 21, 2024 13:14+0000+00:00) http://hl7.org/fhir/us/udap-security/STU1.1/package.tgz http://hl7.org/fhir/us/udap-security/STU1.1/package.tgz HL7, Inc 4.0.1 IG Wed, 21 Aug 2024 12:00:00 +1000 GMT hl7.fhir.us.medication-rems#1.0.0 FHIR implementation options and guidance for medication REMS participants (built Mon, Aug 19, 2024 20:02+0000+00:00) http://hl7.org/fhir/us/medication-rems/STU1/package.tgz http://hl7.org/fhir/us/medication-rems/STU1/package.tgz HL7, Inc 4.0.1 IG Mon, 19 Aug 2024 12:00:00 +1000 GMT hl7.fhir.uv.shorthand#3.0.0 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) http://hl7.org/fhir/uv/shorthand/N2/package.tgz http://hl7.org/fhir/uv/shorthand/N2/package.tgz HL7, Inc 4.0.1 IG Mon, 19 Aug 2024 12:00:00 +1000 GMT hl7.fhir.uv.phd#2.0.0-ballot ImplementationGuide for Personal Health Devices (PHD), used in remote patient monitoring (e.g., weight scales, blood pressure cuffs, glucose monitors, pulse-oximeters, etc.). (built Fri, Aug 16, 2024 03:08+0000+00:00) http://hl7.org/fhir/uv/phd/2024Sep/package.tgz http://hl7.org/fhir/uv/phd/2024Sep/package.tgz HL7, Inc 4.3.0 IG Fri, 16 Aug 2024 12:00:00 +1000 GMT hl7.fhir.us.davinci-pdex#2.1.0-ballot This specification has undergone ballot and connectathon testing. It is expected to continue to evolve, possibly significantly, as part of that process. Feedback 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. This 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. [Financial Management](https://confluence.hl7.org/display/FM/Financial+Management+Home) is the Sponsoring Work Group for this Implementation Guide. **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.** The 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_ andin STU2.1 the IG has been expanded to meet the requirements of the CMS Prior Authorization Rule (CMS-0057). This 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. This IG covers the exchange of: - Claims-based information (without financials) - Clinical Information (such as Lab Results, Allergies and Conditions) - Prior Authorization information This 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. This IG covers the exchange of a Member's Health History in the following scenarios: - Provider requested exchange using SMART-on-FHIR Bulk exchange - Health Plan Exchange using SMART-on-FHIR - Member-authorized Health Plan to Health Plan exchange - Member-authorized Health Plan to Third-Party Application exchange The latter two scenarios are provided to meet the requirements identified in the CMS Interoperability and Patient Access Final Rule. **There are items in this guide that are subject to update**. This includes: - Value Sets - Vocabularies (X12, NUBC etc.) - Examples **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). See the [Table of Contents](toc.html) for more information. (built Wed, Aug 14, 2024 19:57+0000+00:00) http://hl7.org/fhir/us/davinci-pdex/2024SEP/package.tgz http://hl7.org/fhir/us/davinci-pdex/2024SEP/package.tgz HL7, Inc 4.0.1 IG Wed, 14 Aug 2024 12:00:00 +1000 GMT hl7.fhir.us.smp#1.0.0-ballot Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Wed, Aug 14, 2024 18:30+0800+08:00) http://hl7.org/fhir/us/smp/2024Sep/package.tgz http://hl7.org/fhir/us/smp/2024Sep/package.tgz HL7, Inc 4.0.1 IG Wed, 14 Aug 2024 12:00:00 +1000 GMT hl7.fhir.uv.lab-report#1.0.0-ballot This guide describes how the Laboratory Report can be represented in the UV REALM. (built Wed, Aug 14, 2024 20:47+0000+00:00) http://hl7.org/fhir/uv/lab-report/2024Sep/package.tgz http://hl7.org/fhir/uv/lab-report/2024Sep/package.tgz HL7, Inc 4.0.1 IG Wed, 14 Aug 2024 12:00:00 +1000 GMT hl7.fhir.uv.termchangeset#1.0.0-ballot 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) http://hl7.org/fhir/uv/termchangeset/2024Sep/package.tgz http://hl7.org/fhir/uv/termchangeset/2024Sep/package.tgz HL7, Inc 4.0.1 IG Wed, 14 Aug 2024 12:00:00 +1000 GMT hl7.fhir.r6.core#6.0.0-ballot2 FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (built Mon, Aug 12, 2024 16:52+0800+08:00) http://hl7.org/fhir/6.0.0-ballot2/hl7.fhir.r6.core.tgz http://hl7.org/fhir/6.0.0-ballot2/hl7.fhir.r6.core.tgz HL7, Inc 6.0.0-ballot2 fhir.core Tue, 13 Aug 2024 12:00:00 +1000 GMT hl7.fhir.r6.expansions#6.0.0-ballot2 Expansions for the 6.0.0-ballot2 version of the FHIR standard (built Mon, Aug 12, 2024 16:52+0800+08:00) http://hl7.org/fhir/6.0.0-ballot2/hl7.fhir.r6.expansions.tgz http://hl7.org/fhir/6.0.0-ballot2/hl7.fhir.r6.expansions.tgz HL7, Inc 6.0.0-ballot2 fhir.core Tue, 13 Aug 2024 12:00:00 +1000 GMT hl7.fhir.r6.examples#6.0.0-ballot2 Examples for the 6.0.0-ballot2 version of the FHIR standard (built Mon, Aug 12, 2024 16:52+0800+08:00) http://hl7.org/fhir/6.0.0-ballot2/hl7.fhir.r6.examples.tgz http://hl7.org/fhir/6.0.0-ballot2/hl7.fhir.r6.examples.tgz HL7, Inc 6.0.0-ballot2 fhir.core Tue, 13 Aug 2024 12:00:00 +1000 GMT hl7.fhir.r6.search#6.0.0-ballot2 FHIR 6.0.0-ballot2 package : Search Parameters (break out combined parameters for server execution convenience) (built Mon, Aug 12, 2024 16:52+0800+08:00) http://hl7.org/fhir/6.0.0-ballot2/hl7.fhir.r6.search.tgz http://hl7.org/fhir/6.0.0-ballot2/hl7.fhir.r6.search.tgz HL7, Inc 6.0.0-ballot2 fhir.core Tue, 13 Aug 2024 12:00:00 +1000 GMT hl7.fhir.us.davinci-hrex#1.1.0-ballot 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, Aug 13, 2024 16:31+0000+00:00) http://hl7.org/fhir/us/davinci-hrex/2024Sep/package.tgz http://hl7.org/fhir/us/davinci-hrex/2024Sep/package.tgz HL7, Inc 4.0.1 IG Tue, 13 Aug 2024 12:00:00 +1000 GMT hl7.fhir.us.mcc#1.0.0 ### Introduction This HL7&reg; 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. A 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: 1. Query for patient data across providers and compile into a consolidated care plan representation. 2. Encourage capture of and communication of a patient's health concerns and related goals, interventions, and outcomes. 3. 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.) This 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. ### How to Read this Guide and Cautions This 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. ### Value Set Library Rather 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. This 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. ### History of the Care Plan and Electronic Care Plans The 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. Most 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. We 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. ### Project Overview More 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. Care 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. The 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. Initiated 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. The HL7-based activities of the MCC eCare Plan Project include: - Identified use cases to support the documentation and exchange of MCC eCare plan data within EHRs and related systems. - 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. - Develop, test, and ballot an HL7® Fast Health Interoperability Resources (FHIR®) Implementation Guide based on the defined use cases and MCC data elements. Non-HL7 related activities of the MCC eCare Plan project will be facilitated through the [AHRQ eCare Plan Project Confluence](https://ecareplan.ahrq.gov/collaborate): - 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. #### Project Timelines - January 2024: A For comment ballot to gather community input prior to the formal STU Ballot - September 2024: Formal STU Ballot - May 2025 Formal HL7 Publication ### Guidance The 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. #### Relationship to US Core This 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. This 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 ##### General US Core IG Conformance This 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. ##### Provenance This 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). ##### Must Support This IG will adhere to the US Core [Must Support](https://www.hl7.org/fhir/us/core/general-guidance.html#must-support) concept and rules. ### Acknowledgements This 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. This 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) (built Tue, Aug 13, 2024 20:59+0000+00:00) http://hl7.org/fhir/us/mcc/STU1/package.tgz http://hl7.org/fhir/us/mcc/STU1/package.tgz HL7, Inc 4.0.1 IG Tue, 13 Aug 2024 12:00:00 +1000 GMT hl7.fhir.us.pacio-pfe#2.0.0-ballot 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 Tue, Aug 13, 2024 15:07+0000+00:00) http://hl7.org/fhir/us/pacio-pfe/2024Sep/package.tgz http://hl7.org/fhir/us/pacio-pfe/2024Sep/package.tgz HL7, Inc 4.0.1 IG Tue, 13 Aug 2024 12:00:00 +1000 GMT hl7.fhir.uv.application-feature#1.0.0-ballot http://hl7.org/fhir/uv/application-feature/2024Sep/package.tgz http://hl7.org/fhir/uv/application-feature/2024Sep/package.tgz HL7, Inc 4.0.1 IG Tue, 13 Aug 2024 12:00:00 +1000 GMT hl7.fhir.us.identity-matching#2.0.0-ballot http://hl7.org/fhir/us/identity-matching/2024SEP/package.tgz http://hl7.org/fhir/us/identity-matching/2024SEP/package.tgz HL7, Inc 4.0.1 IG Mon, 12 Aug 2024 12:00:00 +1000 GMT hl7.fhir.us.nhsn-dqm#1.0.0-ballot 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 Mon, Aug 12, 2024 17:39+0000+00:00) http://hl7.org/fhir/us/nhsn-dqm/2024Sep/package.tgz http://hl7.org/fhir/us/nhsn-dqm/2024Sep/package.tgz HL7, Inc 4.0.1 IG Mon, 12 Aug 2024 12:00:00 +1000 GMT hl7.fhir.us.qicore#7.0.0-ballot 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 Mon, Aug 12, 2024 16:12+0000+00:00) http://hl7.org/fhir/us/qicore/2024Sep/package.tgz http://hl7.org/fhir/us/qicore/2024Sep/package.tgz HL7, Inc 4.0.1 IG Mon, 12 Aug 2024 12:00:00 +1000 GMT hl7.fhir.uv.ips#2.0.0-ballot http://hl7.org/fhir/uv/ips/2024Sep/package.tgz http://hl7.org/fhir/uv/ips/2024Sep/package.tgz HL7, Inc 4.0.1 IG Mon, 12 Aug 2024 12:00:00 +1000 GMT hl7.fhir.uv.dicom-sr#1.0.0-ballot 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) http://hl7.org/fhir/uv/dicom-sr/2024Sep/package.tgz http://hl7.org/fhir/uv/dicom-sr/2024Sep/package.tgz HL7, Inc 5.0.0 IG Fri, 09 Aug 2024 12:00:00 +1000 GMT hl7.fhir.uv.ibcm#1.0.0-ballot2 http://hl7.org/fhir/uv/ibcm/2024Sep/package.tgz http://hl7.org/fhir/uv/ibcm/2024Sep/package.tgz HL7, Inc 5.0.0 IG Fri, 09 Aug 2024 12:00:00 +1000 GMT hl7.fhir.us.home-lab-report#1.1.0 http://hl7.org/fhir/us/home-lab-report/STU1.1/package.tgz http://hl7.org/fhir/us/home-lab-report/STU1.1/package.tgz HL7, Inc 4.0.1 IG Thu, 08 Aug 2024 12:00:00 +1000 GMT hl7.fhir.uv.fhir-clinical-document#1.0.0-ballot http://hl7.org/fhir/uv/fhir-clinical-document/2024Sep/package.tgz http://hl7.org/fhir/uv/fhir-clinical-document/2024Sep/package.tgz HL7, Inc 4.0.1 IG Thu, 08 Aug 2024 12:00:00 +1000 GMT hl7.fhir.uv.smart-health-cards-and-links#1.0.0-ballot FHIR Implementation Guide for SMART Health Cards and Links (built Thu, Aug 8, 2024 20:50+0000+00:00) http://hl7.org/fhir/uv/smart-health-cards-and-links/2024Sep/package.tgz http://hl7.org/fhir/uv/smart-health-cards-and-links/2024Sep/package.tgz HL7, Inc 4.0.1 IG Thu, 08 Aug 2024 12:00:00 +1000 GMT hl7.fhir.us.carin-bb#2.1.0-snapshot1 CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) (built Sat, Jul 27, 2024 20:08+0800+08:00) http://hl7.org/fhir/us/carin-bb/2.1.0-snapshot1/package.tgz http://hl7.org/fhir/us/carin-bb/2.1.0-snapshot1/package.tgz HL7, Inc 4.0.1 IG Sat, 27 Jul 2024 12:00:00 +1000 GMT hl7.fhir.us.mdi#2.0.0-snapshot1 http://hl7.org/fhir/us/mdi/2.0.0-snapshot1/package.tgz http://hl7.org/fhir/us/mdi/2.0.0-snapshot1/package.tgz HL7, Inc 4.0.1 IG Thu, 20 Jun 2024 12:00:00 +1000 GMT hl7.fhir.us.davinci-vbpr#1.0.0 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 13:48+0000+00:00) http://hl7.org/fhir/us/davinci-vbpr/STU1/package.tgz http://hl7.org/fhir/us/davinci-vbpr/STU1/package.tgz HL7, Inc 4.0.1 IG Mon, 17 Jun 2024 12:00:00 +1000 GMT hl7.fhir.us.central-cancer-registry-reporting#1.0.0 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 12:55+0000+00:00) http://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/package.tgz http://hl7.org/fhir/us/central-cancer-registry-reporting/STU1/package.tgz HL7, Inc 4.0.1 IG Fri, 31 May 2024 12:00:00 +1000 GMT hl7.fhir.uv.cql#1.0.0 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 Fri, May 31, 2024 14:18+0000+00:00) http://hl7.org/fhir/uv/cql/STU1/package.tgz http://hl7.org/fhir/uv/cql/STU1/package.tgz HL7, Inc 4.0.1 IG Fri, 31 May 2024 12:00:00 +1000 GMT hl7.fhir.uv.crmi#1.0.0 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, May 31, 2024 16:38+0000+00:00) http://hl7.org/fhir/uv/crmi/STU1/package.tgz http://hl7.org/fhir/uv/crmi/STU1/package.tgz HL7, Inc 4.0.1 IG Fri, 31 May 2024 12:00:00 +1000 GMT hl7.fhir.us.eltss#2.0.0 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:28+0000+00:00) http://hl7.org/fhir/us/eltss/STU2/package.tgz http://hl7.org/fhir/us/eltss/STU2/package.tgz HL7, Inc 4.0.1 IG Mon, 27 May 2024 12:00:00 +1000 GMT hl7.fhir.us.core#7.0.0 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. These 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 Wed, May 8, 2024 15:33+0000+00:00) http://hl7.org/fhir/us/core/STU7/package.tgz http://hl7.org/fhir/us/core/STU7/package.tgz HL7, Inc 4.0.1 IG Wed, 08 May 2024 12:00:00 +1000 GMT hl7.fhir.uv.pharm-quality#1.0.0 This IG is developed for the HL7 International Pharmaceutical Quality (PQ) - Industry Use Case project, sponsored by the Biomedical Research and Regulation Work Group * [Project Proposal: PSS-2137](https://jira.hl7.org/browse/PSS-2137) * [Project Scope Statement: PSS-2145](https://jira.hl7.org/browse/PSS-2145) (built Wed, May 8, 2024 13:18+0000+00:00) http://hl7.org/fhir/uv/pharm-quality/STU1/package.tgz http://hl7.org/fhir/uv/pharm-quality/STU1/package.tgz HL7, Inc 5.0.0 IG Wed, 08 May 2024 12:00:00 +1000 GMT hl7.fhir.uv.ae-research-backport-ig#1.0.1 ### 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) http://hl7.org/fhir/uv/ae-research-backport-ig/STU1/package.tgz http://hl7.org/fhir/uv/ae-research-backport-ig/STU1/package.tgz HL7, Inc 4.0.1 IG Tue, 30 Apr 2024 12:00:00 +1000 GMT hl7.fhir.uv.ae-research-ig#1.0.1 ### 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) http://hl7.org/fhir/uv/ae-research-ig/STU1/package.tgz http://hl7.org/fhir/uv/ae-research-ig/STU1/package.tgz HL7, Inc 5.0.0 IG Tue, 30 Apr 2024 12:00:00 +1000 GMT hl7.fhir.uv.smart-app-launch#2.2.0 http://hl7.org/fhir/smart-app-launch/STU2.2/package.tgz http://hl7.org/fhir/smart-app-launch/STU2.2/package.tgz HL7, Inc 4.0.1 IG Tue, 30 Apr 2024 12:00:00 +1000 GMT hl7.fhir.us.cancer-reporting#1.0.1 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 to a central registry, the FHIR Messaging paradigm shall be required; however when sending between LIS and EHR systems, implementors may choose to use alterantive transport and processing modalities, such as FHIR transaciton 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 message bundle and is compliant with FHIR Release 4. (built Tue, Apr 16, 2024 18:41+0000+00:00) http://hl7.org/fhir/us/cancer-reporting/STU1.0.1/package.tgz http://hl7.org/fhir/us/cancer-reporting/STU1.0.1/package.tgz HL7, Inc 4.0.1 IG Tue, 16 Apr 2024 12:00:00 +1000 GMT hl7.fhir.us.insurance-card#1.1.0 CARIN Digital Insurance Card (built Tue, Apr 16, 2024 17:25+0000+00:00) http://hl7.org/fhir/us/insurance-card/STU1.1/package.tgz http://hl7.org/fhir/us/insurance-card/STU1.1/package.tgz HL7, Inc 4.0.1 IG Tue, 16 Apr 2024 12:00:00 +1000 GMT hl7.fhir.us.mcode#4.0.0-ballot 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, Apr 10, 2024 13:47+0000+00:00) http://hl7.org/fhir/us/mcode/2024May/package.tgz http://hl7.org/fhir/us/mcode/2024May/package.tgz HL7, Inc 4.0.1 IG Wed, 10 Apr 2024 12:00:00 +1000 GMT hl7.fhir.uv.fhircast#3.0.0-ballot 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) http://hl7.org/fhir/uv/fhircast/2024May/package.tgz http://hl7.org/fhir/uv/fhircast/2024May/package.tgz HL7, Inc 4.0.1 IG Wed, 10 Apr 2024 12:00:00 +1000 GMT hl7.fhir.us.codex-radiation-therapy#2.0.0-ballot 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) http://hl7.org/fhir/us/codex-radiation-therapy/2024May/package.tgz http://hl7.org/fhir/us/codex-radiation-therapy/2024May/package.tgz HL7, Inc 4.0.1 IG Tue, 09 Apr 2024 12:00:00 +1000 GMT hl7.fhir.us.cqfmeasures#5.0.0-ballot2 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 Tue, Apr 9, 2024 13:15+0000+00:00) http://hl7.org/fhir/us/cqfmeasures/2024May/package.tgz http://hl7.org/fhir/us/cqfmeasures/2024May/package.tgz HL7, Inc 4.0.1 IG Tue, 09 Apr 2024 12:00:00 +1000 GMT hl7.fhir.us.davinci-pct#2.0.0-ballot To support the request for cost information for specific services and items 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 Mon, Apr 8, 2024 16:49+0000+00:00) http://hl7.org/fhir/us/davinci-pct/2024May/package.tgz http://hl7.org/fhir/us/davinci-pct/2024May/package.tgz HL7, Inc 4.0.1 IG Mon, 08 Apr 2024 12:00:00 +1000 GMT hl7.fhir.us.pq-cmc-fda#1.0.0-ballot 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 Mon, Apr 8, 2024 17:45+0000+00:00) http://hl7.org/fhir/us/pq-cmc-fda/2024May/package.tgz http://hl7.org/fhir/us/pq-cmc-fda/2024May/package.tgz HL7, Inc 5.0.0 IG Mon, 08 Apr 2024 12:00:00 +1000 GMT hl7.fhir.uv.cql#1.0.0-snapshot 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 Sat, Apr 6, 2024 09:37+1100+11:00) http://hl7.org/fhir/uv/cql/1.0.0-snapshot/package.tgz http://hl7.org/fhir/uv/cql/1.0.0-snapshot/package.tgz HL7, Inc 4.0.1 IG Sat, 06 Apr 2024 12:00:00 +1100 GMT hl7.fhir.uv.crmi#1.0.0-snapshot 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 Sat, Apr 6, 2024 06:47+1100+11:00) http://hl7.org/fhir/uv/crmi/1.0.0-snapshot/package.tgz http://hl7.org/fhir/uv/crmi/1.0.0-snapshot/package.tgz HL7, Inc 4.0.1 IG Sat, 06 Apr 2024 12:00:00 +1100 GMT hl7.fhir.us.mdi#2.0.0-ballot http://hl7.org/fhir/us/mdi/2024May/package.tgz http://hl7.org/fhir/us/mdi/2024May/package.tgz HL7, Inc 4.0.1 IG Fri, 05 Apr 2024 12:00:00 +1100 GMT hl7.fhir.us.medication-rems#1.0.0-ballot FHIR implementation options and guidance for medication REMS participants (built Fri, Apr 5, 2024 14:52+0000+00:00) http://hl7.org/fhir/us/medication-rems/2024May/package.tgz http://hl7.org/fhir/us/medication-rems/2024May/package.tgz HL7, Inc 4.0.1 IG Fri, 05 Apr 2024 12:00:00 +1100 GMT hl7.fhir.us.vrdr#3.0.0-ballot http://hl7.org/fhir/us/vrdr/2024May/package.tgz http://hl7.org/fhir/us/vrdr/2024May/package.tgz HL7, Inc 4.0.1 IG Fri, 05 Apr 2024 12:00:00 +1100 GMT hl7.fhir.uv.cardx-htn-mng#1.0.0-ballot http://hl7.org/fhir/uv/cardx-htn-mng/2024May/package.tgz http://hl7.org/fhir/uv/cardx-htn-mng/2024May/package.tgz HL7, Inc 4.0.1 IG Fri, 05 Apr 2024 12:00:00 +1100 GMT hl7.fhir.us.pdmp#1.0.0-ballot US Prescription Drug Monitoring Program (PDMP) FHIR IG (built Thu, Apr 4, 2024 15:32+0000+00:00) http://hl7.org/fhir/us/pdmp/2024May/package.tgz http://hl7.org/fhir/us/pdmp/2024May/package.tgz HL7, Inc 4.0.1 IG Thu, 04 Apr 2024 12:00:00 +1100 GMT hl7.fhir.us.ccda#1.2.0 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. This 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). The 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. We 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. ### Scope To represent Consolidated CDA Templates for Clinical Notes (C-CDA) 2.1 templates using FHIR profiles. This first stage of the project defines all the C-CDA document-level profiles on the Composition resource and contained sections. Any 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. For further information see the C-CDA specification here: http://www.hl7.org/implement/standards/product_brief.cfm?product_id=408. (built Tue, Mar 12, 2024 18:59+0000+00:00) http://hl7.org/fhir/us/ccda/STU1.2/package.tgz http://hl7.org/fhir/us/ccda/STU1.2/package.tgz HL7, Inc 4.0.1 IG Tue, 12 Mar 2024 12:00:00 +1100 GMT hl7.fhir.us.qicore#6.0.0 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, Mar 1, 2024 18:46+0000+00:00) http://hl7.org/fhir/us/qicore/STU6/package.tgz http://hl7.org/fhir/us/qicore/STU6/package.tgz HL7, Inc 4.0.1 IG Fri, 01 Mar 2024 12:00:00 +1100 GMT hl7.fhir.us.davinci-dtr#2.0.1 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 Thu, Jan 11, 2024 19:19+0000+00:00) http://hl7.org/fhir/us/davinci-dtr/STU2/package.tgz http://hl7.org/fhir/us/davinci-dtr/STU2/package.tgz HL7, Inc 4.0.1 IG Thu, 11 Jan 2024 12:00:00 +1100 GMT hl7.fhir.us.pacio-adi#1.0.0 PACIO Advance Directive Interoperability Implementation Guide (built Thu, Jan 11, 2024 17:40+0000+00:00) http://hl7.org/fhir/us/pacio-adi/STU1/package.tgz http://hl7.org/fhir/us/pacio-adi/STU1/package.tgz HL7, Inc 4.0.1 IG Thu, 11 Jan 2024 12:00:00 +1100 GMT hl7.fhir.us.davinci-atr#2.0.0 Exchange of member attribution list between payers and providers (built Tue, Jan 9, 2024 20:14+0000+00:00) http://hl7.org/fhir/us/davinci-atr/STU2/package.tgz http://hl7.org/fhir/us/davinci-atr/STU2/package.tgz HL7, Inc 4.0.1 IG Tue, 09 Jan 2024 12:00:00 +1100 GMT hl7.fhir.us.davinci-crd#2.0.1 Guidelines for conveying coverage requirements to clinicians when planning treatment (built Mon, Jan 8, 2024 18:55+0000+00:00) http://hl7.org/fhir/us/davinci-crd/STU2/package.tgz http://hl7.org/fhir/us/davinci-crd/STU2/package.tgz HL7, Inc 4.0.1 IG Mon, 08 Jan 2024 12:00:00 +1100 GMT hl7.fhir.us.davinci-pdex#2.0.0 This specification has undergone ballot and connectathon testing. It is expected to evolve, possibly significantly, as part of that process. Feedback 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. This 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. [Financial Management](https://confluence.hl7.org/display/FM/Financial+Management+Home) is the Sponsoring Work Group for this Implementation Guide. **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 Profiles based on FHIR R4) which can be understood by providers and, if they choose to, committed to their Electronic Medical Records (EMR) System.** The 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. This IG uses the same Member Health History "payload" for member-authorized exchange of information with other Health Plans 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. This IG covers the exchange of: - Claims-based information - Clinical Information (such as Lab Results, Allergies and Conditions) This 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. This IG covers the exchange of a Member's Health History in the following scenarios: - Provider requested Provider-Health Plan Exchange using CDS-Hooks and SMART-on-FHIR - Member-authorized Health Plan to Health Plan exchange - Member-authorized Health Plan to Third-Party Application exchange The latter two scenarios are provided to meet the requirements identified in the CMS Interoperability and Patient Access Final Rule. **There are items in this guide that are subject to update**. This includes: - Value Sets - Vocabularies (X12, NUBC etc.) - Examples **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). See the [Table of Contents](toc.html) for more information. (built Sat, Jan 6, 2024 03:03+0000+00:00) http://hl7.org/fhir/us/davinci-pdex/STU2/package.tgz http://hl7.org/fhir/us/davinci-pdex/STU2/package.tgz HL7, Inc 4.0.1 IG Sat, 06 Jan 2024 12:00:00 +1100 GMT hl7.fhir.us.pacio-pfe#1.0.0 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 Fri, Jan 5, 2024 16:53+0000+00:00) http://hl7.org/fhir/us/pacio-pfe/STU1/package.tgz http://hl7.org/fhir/us/pacio-pfe/STU1/package.tgz HL7, Inc 4.0.1 IG Fri, 05 Jan 2024 12:00:00 +1100 GMT hl7.fhir.us.davinci-pct#1.1.0 To support the request for cost information for specific services and items 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, Jan 3, 2024 18:16+0000+00:00) http://hl7.org/fhir/us/davinci-pct/STU1.1/package.tgz http://hl7.org/fhir/us/davinci-pct/STU1.1/package.tgz HL7, Inc 4.0.1 IG Wed, 03 Jan 2024 12:00:00 +1100 GMT hl7.fhir.uv.ehrs-rle#1.1.0 EHRS Functional Model - Record Lifecycle Events - FHIR Implementation Guide (built Tue, Jan 2, 2024 21:56+0000+00:00) http://hl7.org/fhir/uv/ehrs-rle/Informative1/package.tgz http://hl7.org/fhir/uv/ehrs-rle/Informative1/package.tgz HL7, Inc 5.0.0 IG Tue, 02 Jan 2024 12:00:00 +1100 GMT hl7.fhir.us.resp-net#1.0.0-ballot 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 Thu, Dec 21, 2023 13:44+0000+00:00) http://hl7.org/fhir/us/resp-net/2024Jan/package.tgz http://hl7.org/fhir/us/resp-net/2024Jan/package.tgz HL7, Inc 4.0.1 IG Thu, 21 Dec 2023 12:00:00 +1100 GMT hl7.fhir.uv.livd#1.0.0-ballot Recommended LOINC mappings for IVD Devices (built Thu, Dec 21, 2023 20:53+0000+00:00) http://hl7.org/fhir/uv/livd/2024Jan/package.tgz http://hl7.org/fhir/uv/livd/2024Jan/package.tgz HL7, Inc 4.0.1 IG Thu, 21 Dec 2023 12:00:00 +1100 GMT hl7.fhir.uv.cql#1.0.0-ballot 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 Wed, Dec 20, 2023 01:16+0000+00:00) http://hl7.org/fhir/uv/cql/2024Jan/package.tgz http://hl7.org/fhir/uv/cql/2024Jan/package.tgz HL7, Inc 4.0.1 IG Wed, 20 Dec 2023 12:00:00 +1100 GMT hl7.fhir.uv.crmi#1.0.0-ballot2 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 Wed, Dec 20, 2023 03:22+0000+00:00) http://hl7.org/fhir/uv/crmi/2024Jan/package.tgz http://hl7.org/fhir/uv/crmi/2024Jan/package.tgz HL7, Inc 4.0.1 IG Wed, 20 Dec 2023 12:00:00 +1100 GMT hl7.fhir.uv.v2mappings#1.0.0-ballot 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 Wed, Dec 20, 2023 15:18+0000+00:00) http://hl7.org/fhir/uv/v2mappings/2024Jan/package.tgz http://hl7.org/fhir/uv/v2mappings/2024Jan/package.tgz HL7, Inc 4.0.1 IG Wed, 20 Dec 2023 12:00:00 +1100 GMT hl7.fhir.r6.core#6.0.0-ballot1 FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (built Mon, Dec 18, 2023 15:12+1100+11:00) http://hl7.org/fhir/6.0.0-ballot1/hl7.fhir.r6.core.tgz http://hl7.org/fhir/6.0.0-ballot1/hl7.fhir.r6.core.tgz HL7, Inc 6.0.0-ballot1 fhir.core Tue, 19 Dec 2023 12:00:00 +1100 GMT hl7.fhir.r6.expansions#6.0.0-ballot1 Expansions for the 6.0.0-ballot1 version of the FHIR standard (built Mon, Dec 18, 2023 15:12+1100+11:00) http://hl7.org/fhir/6.0.0-ballot1/hl7.fhir.r6.expansions.tgz http://hl7.org/fhir/6.0.0-ballot1/hl7.fhir.r6.expansions.tgz HL7, Inc 6.0.0-ballot1 fhir.core Tue, 19 Dec 2023 12:00:00 +1100 GMT hl7.fhir.r6.examples#6.0.0-ballot1 Examples for the 6.0.0-ballot1 version of the FHIR standard (built Mon, Dec 18, 2023 15:12+1100+11:00) http://hl7.org/fhir/6.0.0-ballot1/hl7.fhir.r6.examples.tgz http://hl7.org/fhir/6.0.0-ballot1/hl7.fhir.r6.examples.tgz HL7, Inc 6.0.0-ballot1 fhir.core Tue, 19 Dec 2023 12:00:00 +1100 GMT hl7.fhir.r6.search#6.0.0-ballot1 FHIR 6.0.0-ballot1 package : Search Parameters (break out combined parameters for server execution convenience) (built Mon, Dec 18, 2023 15:12+1100+11:00) http://hl7.org/fhir/6.0.0-ballot1/hl7.fhir.r6.search.tgz http://hl7.org/fhir/6.0.0-ballot1/hl7.fhir.r6.search.tgz HL7, Inc 6.0.0-ballot1 fhir.core Tue, 19 Dec 2023 12:00:00 +1100 GMT hl7.fhir.us.core#7.0.0-ballot 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. These 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, Dec 19, 2023 21:01+0000+00:00) http://hl7.org/fhir/us/core/2024Jan/package.tgz http://hl7.org/fhir/us/core/2024Jan/package.tgz HL7, Inc 4.0.1 IG Tue, 19 Dec 2023 12:00:00 +1100 GMT hl7.fhir.uv.cpg#2.0.0-ballot 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) http://hl7.org/fhir/uv/cpg/2024Jan/package.tgz http://hl7.org/fhir/uv/cpg/2024Jan/package.tgz HL7, Inc 4.0.1 IG Tue, 19 Dec 2023 12:00:00 +1100 GMT hl7.fhir.uv.smart-app-launch#2.2.0-ballot http://hl7.org/fhir/smart-app-launch/2024Jan/package.tgz http://hl7.org/fhir/smart-app-launch/2024Jan/package.tgz HL7, Inc 4.0.1 IG Tue, 19 Dec 2023 12:00:00 +1100 GMT hl7.fhir.us.bfdr#2.0.0-ballot http://hl7.org/fhir/us/bfdr/2024Jan/package.tgz http://hl7.org/fhir/us/bfdr/2024Jan/package.tgz HL7, Inc 4.0.1 IG Mon, 18 Dec 2023 12:00:00 +1100 GMT hl7.fhir.uv.genomics-reporting#3.0.0-ballot Guidelines for reporting of clinical genomics results using HL7 FHIR. (built Mon, Dec 18, 2023 22:39+0000+00:00) http://hl7.org/fhir/uv/genomics-reporting/2024Jan/package.tgz http://hl7.org/fhir/uv/genomics-reporting/2024Jan/package.tgz HL7, Inc 4.0.1 IG Mon, 18 Dec 2023 12:00:00 +1100 GMT hl7.fhir.uv.pharm-quality#1.0.0-ballot ***Content TBD*** This IG is developed for the Data exchange industry – Pharmaceutical Quality (PQ) project * [Project Proposal: PSS-2137](https://jira.hl7.org/browse/PSS-2137) * [Project Scope Statement: PSS-2145](https://jira.hl7.org/browse/PSS-2145) (built Mon, Dec 18, 2023 15:56+0000+00:00) http://hl7.org/fhir/uv/pharm-quality/2024Jan/package.tgz http://hl7.org/fhir/uv/pharm-quality/2024Jan/package.tgz HL7, Inc 5.0.0 IG Mon, 18 Dec 2023 12:00:00 +1100 GMT hl7.fhir.uv.subscriptions-backport#1.2.0-ballot 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) http://hl7.org/fhir/uv/subscriptions-backport/2024Jan/package.tgz http://hl7.org/fhir/uv/subscriptions-backport/2024Jan/package.tgz HL7, Inc 4.3.0 IG Mon, 18 Dec 2023 12:00:00 +1100 GMT hl7.fhir.uv.ebm#1.0.0-ballot http://hl7.org/fhir/uv/ebm/2024Jan/package.tgz http://hl7.org/fhir/uv/ebm/2024Jan/package.tgz HL7, Inc 5.0.0 IG Sun, 17 Dec 2023 12:00:00 +1100 GMT hl7.fhir.uv.ebm#1.0.0-ballot http://hl7.org/fhir/uv/ebm/2024Jan/package.tgz http://hl7.org/fhir/uv/ebm/2024Jan/package.tgz HL7, Inc 5.0.0 IG Sun, 17 Dec 2023 12:00:00 +1100 GMT hl7.fhir.us.vr-common-library#2.0.0-ballot http://hl7.org/fhir/us/vr-common-library/2024Jan/package.tgz http://hl7.org/fhir/us/vr-common-library/2024Jan/package.tgz HL7, Inc 4.0.1 IG Sat, 16 Dec 2023 12:00:00 +1100 GMT hl7.fhir.us.cqfmeasures#5.0.0-ballot 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 Fri, Dec 15, 2023 17:42+0000+00:00) http://hl7.org/fhir/us/cqfmeasures/2024Jan/package.tgz http://hl7.org/fhir/us/cqfmeasures/2024Jan/package.tgz HL7, Inc 4.0.1 IG Fri, 15 Dec 2023 12:00:00 +1100 GMT hl7.fhir.us.eltss#2.0.0-ballot 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) http://hl7.org/fhir/us/eltss/2024Jan/package.tgz http://hl7.org/fhir/us/eltss/2024Jan/package.tgz HL7, Inc 4.0.1 IG Fri, 15 Dec 2023 12:00:00 +1100 GMT hl7.fhir.uv.ihe-sdc-ecc#1.0.0 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) http://hl7.org/fhir/uv/ihe-sdc-ecc/STU1/package.tgz http://hl7.org/fhir/uv/ihe-sdc-ecc/STU1/package.tgz HL7, Inc 4.0.1 IG Tue, 12 Dec 2023 12:00:00 +1100 GMT hl7.fhir.us.davinci-drug-formulary#2.0.1 DaVinci Payer Data Exchange (PDex) US Drug Formulary, Release 2.0.1 - US Realm STU" (built Fri, Dec 1, 2023 22:17+0000+00:00) http://hl7.org/fhir/us/davinci-drug-formulary/STU2.0.1/package.tgz http://hl7.org/fhir/us/davinci-drug-formulary/STU2.0.1/package.tgz HL7, Inc 4.0.1 IG Fri, 01 Dec 2023 12:00:00 +1100 GMT hl7.fhir.us.davinci-pas#2.0.1 Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Fri, Dec 1, 2023 20:54+0000+00:00) http://hl7.org/fhir/us/davinci-pas/STU2/package.tgz http://hl7.org/fhir/us/davinci-pas/STU2/package.tgz HL7, Inc 4.0.1 IG Fri, 01 Dec 2023 12:00:00 +1100 GMT hl7.fhir.us.mdi#1.1.0 This US-specific implementation guide (IG) provides guidance on the exchange of information to and from medicolegal death investigation (MDI) information systems. It supports interoperability between the MDI case management systems (CMS) used by medical examiner and coroner offices; forensic toxicology and other laboratory information management systems (LIMS); electronic death registration systems (EDRS) of jurisdictional vital records offices (VROs); and ancillary workflows whose systems have the capability of using Fast Healthcare Interoperability Resources (FHIR). This guide provides MDI CMS developers with the technical details and best practices to standardize MDI fields and interfaces. Stakeholders may use the narrative portions of this guide to inform policies and practices for data exchange between systems contributing to, and using information from, death investigations. This guide can serve as a base for local specifications. (built Thu, Nov 16, 2023 21:49+0000+00:00) http://hl7.org/fhir/us/mdi/STU1.1/package.tgz http://hl7.org/fhir/us/mdi/STU1.1/package.tgz HL7, Inc 4.0.1 IG Thu, 16 Nov 2023 12:00:00 +1100 GMT hl7.fhir.us.registry-protocols#1.0.0 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) http://hl7.org/fhir/us/registry-protocols/STU1/package.tgz http://hl7.org/fhir/us/registry-protocols/STU1/package.tgz HL7, Inc 4.0.1 IG Tue, 14 Nov 2023 12:00:00 +1100 GMT hl7.fhir.us.mcode#3.0.0 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) http://hl7.org/fhir/us/mcode/STU3/package.tgz http://hl7.org/fhir/us/mcode/STU3/package.tgz HL7, Inc 4.0.1 IG Thu, 26 Oct 2023 12:00:00 +1100 GMT hl7.fhir.us.vrdr#2.2.0 http://hl7.org/fhir/us/vrdr/STU2.2/package.tgz http://hl7.org/fhir/us/vrdr/STU2.2/package.tgz HL7, Inc 4.0.1 IG Tue, 17 Oct 2023 12:00:00 +1100 GMT hl7.fhir.us.bfdr#1.1.0 ### Description Birth and fetal death reporting includes the transmission of data from health care providers to jurisdictional vital records offices and national health statistics agencies. Data associated with the mother of the baby or delivered fetus may be communicated independently from data associated directly with the labor and delivery encounter at the responsible healthcare facility. Note that for the purposes of this guide, &quot;mother&quot; always refers to the woman who delivered the infant or fetus. In cases of surrogacy or gestational carrier, the information reported should be for the surrogate or the gestational carrier, that is, the woman who delivered the infant. Also, the national statistics agency referred to in this guide is the [National Center for Health Statistics - CDC](https://www.cdc.gov/nchs/index.htm) (NCHS). This implementation guide (IG) defines a series of Health Level Seven (HL7®) Fast Healthcare Interoperability Resources (FHIR®) profiles on the Composition resource to represent electronic birth and fetal death reporting (BFDR). It includes the content of medical/health information on live births and fetal deaths for select state and federal birth and fetal death reporting, as indicated in the [2003 Revision of the U.S. Standard Certificate of Live Birth](https://www.cdc.gov/nchs/data/dvs/birth11-03final-ACC.pdf) and the [2003 Revision of the U.S. Standard Report of Fetal Death](https://www.cdc.gov/nchs/data/dvs/FDEATH11-03finalACC.pdf). Additionally, it includes the content that is exchanged between electronic health record (EHR) systems, jurisdictions, and the Centers for Disease Control and Prevention/ National Center for Health Statistics (CDC/NCHS). ### Relationship to Other Standards This BFDR IG standard complements other vital records standards to support the expansion of information flows to and from the national statistics agency. The BFDR STU 1 drew on foundational work of early standards listed in the Background section, below. This current version of the BFDR IG is informed by : * [HL7, Vital Records Death Reporting (VRDR) FHIR Implementation Guide](http://hl7.org/fhir/us/vrdr/) * [Office of the National Coordinator for Health Information Technology (ONC), United States Core Data for Interoperability (USCDI)](https://www.healthit.gov/isa/united-states-core-data-interoperability-uscdi) ### Dependencies This implementation guide re-uses and further constrains profiles from the following guides: * [US Core Implementation Guide, STU5.0.1](http://hl7.org/fhir/us/core/STU5.0.1/) * [Vital Records Common Profiles Library](http://hl7.org/fhir/us/vr-common-library) * [Occupational Data for Health (ODH)](http://hl7.org/fhir/us/odh/) ### Audience This guide is for analysts and developers who require guidance on the use of the HL7 FHIR for providing birth and fetal death reporting information. The IG is informative to health care provider organizations, jurisdictional vital records offices, CDC/NCHS, health information exchange organizations, and other vital records fetal death reporting stakeholders. ### Background This FHIR IG builds on previous electronic data standards for transmitting vital records of death, birth, and fetal death. * [HL7, Version 2.6 Implementation Guide: Vital Records Birth and Fetal Death Reporting](https://www.hl7.org/implement/standards/product_brief.cfm?product_id=320) * [HL7, CDA® R2 Implementation Guide: Birth and Fetal Death Reporting](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=387) * [IHE , Quality, Research and Public Health Technical Framework Supplement - Birth and Fetal Death Reporting-Enhanced (BFDR-E)](https://www.ihe.net/uploadedFiles/Documents/QRPH/IHE_QRPH_Suppl_BFDR-E.pdf) This IG provides standardized data strutures for transmission of reliable and relevant clinical information to jurisdictional vital records offices and transfer of information from vital records offices to the national statistics agency. Electronic vital records work started with the HL7 Vital Records Domain Analysis Model (VR DAM), published as an Informative Specification in 2011. The VR DAM was updated in 2017 with the HL7 Cross-Paradigm Domain Analysis Model: Vital Records, Release 2, in 2018, with Release 3, and in November 2020 as Release 4. [VR DAM, Release 5](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=466) was published in May 2022. Implementers who review or reference the VR DAM should note that the active vital records FHIR IGs (such as BFDR and VRDR) may no longer aligned with the VR DAM. This FHIR IG uses the US Core profiles. Where this FHIR IG is unable to use a US Core profile, we have followed the Cross Group Projects Work Group's variance request process, and have provided the US Realm Steering Committee an approved rationale for deviation in the IG. ### How to Read This Guide This Guide is divided into several pages which are listed at the top of each page in the menu bar. * Home: Introduction and background for HL7 FHIR® Vital Records Common Profiles Library * [The Specification](the_specification.html): A technical overview of implementing the specification * [Use Cases](use_cases.html): The use cases supported by this guide * Implementer Guidance: The [worksheet Questionnaire format](patient_worksheet_questionnaires.html), [IJE Mapping](ije_mapping.html), and [Vital Records Forms Mapping](vital_records_forms_mapping.html) * [Terminology](terminology.html): A listing of the value sets used in this guide * [Downloads](downloads.html): Links to downloadable artifacts * [Change Log](change_log.html): Details of changes made in each version of this IG * [Artifact Index](artifacts.html): A list of the FHIR artifacts (profiles, examples, and value sets) defined as part of this guide * Appendices: Examples of live birth and fetal death reports and worksheets ### Other Information This is an update (STU 1.1) of the first FHIR BFDR standard. This guide is compliant with FHIR Release 4. For Clinical Safety Information please refer to the [FHIR Implementer’s Safety Checklist](http://hl7.org/fhir/safety.html). Disclaimer: All 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. (built Tue, Oct 10, 2023 13:06+0000+00:00) http://hl7.org/fhir/us/bfdr/STU1.1/package.tgz http://hl7.org/fhir/us/bfdr/STU1.1/package.tgz HL7, Inc 4.0.1 IG Tue, 10 Oct 2023 12:00:00 +1100 GMT hl7.fhir.us.vr-common-library#1.1.0 ### Description This guide is a Fast Healthcare Interoperability Resources (FHIR) Profiles Library to support the needs of multiple vital records implementation guides (IGs). It does not provide any use case (scenario) specific content or additional guidance on how to use these artifacts, but serves as a source for a standard set of profiles for reuse in multiple use case specific IGs focusing on the exchange of vital records information. Implementation details such as how and when to use a given artifact will be supplied in these guides. ### Background Two FHIR IG projects, [Birth Defects](https://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=1532) and [Birth and Fetal Death Reporting](http://hl7.org/fhir/us/bfdr/), share many common data elements or concepts. The initial scope of this Vital Records Common Profiles Library included data elements common to these two FHIR projects in a US Realm framework. The current update adds data elements shared by two other vital records FHIR IGs, [Vital Records Death Reporting (VRDR)](http://hl7.org/fhir/us/vrdr/), and the [Medicolegal Death Investigation (MDI)](http://hl7.org/fhir/us/mdi/). Many of the data elements in the vital records IGs (BFDR, VRDR, and this Library) can be identified using the IJE (Inter-Jurisdictional Exchange) data element names (codes). The IJE codes are used for exchange of data among jurisdictions and with authorized data partners, such as NCHS. NCHS has implemented IJE codes for exchange of mortality data with jurisdictions via the VRDR IG, however, the use of IJE codes has not yet been implemented for birth and fetal death reporting to NCHS. [FHIR profile mappings to the IJE format are available for Mortality, Natality, and Fetal Death.](https://github.com/HL7/vr-common-library/raw/master/input/mapping/IJE_File_Layouts_Version_2021_FHIR-2023-02-22-All-Combined.xlsx) The mappings are based on information from: * [200X NCHS Mortality - Demographic File Description](https://www.cdc.gov/nchs/data/dvs/200XMOR_web_with%20clearance%20revisions-acc.pdf) * [200X NCHS Natality File Description](https://www.cdc.gov/nchs/data/dvs/200XNAT_web_with%20clearance%20revisions-acc.pdf) * [200X NCHS Fetal Death File Description](https://www.cdc.gov/nchs/data/dvs/200XFET_web_with%20clearance%20revisions-acc.pdf) A FHIR common profiles library avoids defining the same data element multiple times across IGs by allowing each IG to reference them. This profile library will provide a standard framework for vital records information to support interoperability among public health systems and reduce provider and implementer burden. This FHIR IG uses US Core profiles. Where unable to use a US Core profile, we have followed the Cross-Group Projects Work Group's variance request process and have provided the US Realm Steering Committee an approved rationale for deviation in the IG. For Clinical Safety Information please refer to the [FHIR Implementer’s Safety Checklist](http://hl7.org/fhir/safety.html). ### How to Read This Guide This Guide is divided into several pages which are listed at the top of each page in the menu bar. * Home: The introduction and background for HL7® FHIR® Vital Records Common Profiles Library * [Terminology](terminology.html): A listing of the value sets used in this guide * [Downloads](downloads.html): Links to downloadable artifacts * [Change Log](change_log.html): Details of changes made in each version of this IG * [Artifact Index](artifacts.html): A list of the defined FHIR artifacts (profiles, examples, and value sets) in this guide (built Fri, Oct 6, 2023 12:58+0000+00:00) http://hl7.org/fhir/us/vr-common-library/STU1.1/package.tgz http://hl7.org/fhir/us/vr-common-library/STU1.1/package.tgz HL7, Inc 4.0.1 IG Fri, 06 Oct 2023 12:00:00 +1100 GMT hl7.fhir.us.hsds#1.0.0 fhir-human-services-directory (built Wed, Oct 4, 2023 18:49+0000+00:00) http://hl7.org/fhir/us/hsds/STU1/package.tgz http://hl7.org/fhir/us/hsds/STU1/package.tgz HL7, Inc 4.0.1 IG Wed, 04 Oct 2023 12:00:00 +1100 GMT hl7.fhir.us.davinci-deqm#4.0.0 http://hl7.org/fhir/us/davinci-deqm/STU4/package.tgz http://hl7.org/fhir/us/davinci-deqm/STU4/package.tgz HL7, Inc 4.0.1 IG Tue, 03 Oct 2023 12:00:00 +1100 GMT hl7.fhir.us.hai#2.1.0 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. As reports are modified and new report types are defined, CDC and Health Level Seven (HL7) will develop and publish additional constraints. Throughout 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. Note 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) http://hl7.org/fhir/us/hai/STU2.1/package.tgz http://hl7.org/fhir/us/hai/STU2.1/package.tgz HL7, Inc 4.0.1 IG Wed, 06 Sep 2023 12:00:00 +1000 GMT hl7.fhir.us.icsr-ae-reporting#1.0.1 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) http://hl7.org/fhir/us/icsr-ae-reporting/STU1/package.tgz http://hl7.org/fhir/us/icsr-ae-reporting/STU1/package.tgz HL7, Inc 4.0.1 IG Tue, 29 Aug 2023 12:00:00 +1000 GMT hl7.fhir.us.cqfmeasures#4.0.0 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, Aug 28, 2023 20:07+0000+00:00) http://hl7.org/fhir/us/cqfmeasures/STU4/package.tgz http://hl7.org/fhir/us/cqfmeasures/STU4/package.tgz HL7, Inc 4.0.1 IG Mon, 28 Aug 2023 12:00:00 +1000 GMT hl7.fhir.us.physical-activity#1.0.0 This implementation guide provides standardization around patient physical activity, including:&#x0a;* measures for recording a patient's level of physical activity;&#x0a;* measures to support assertions of physical activity, including device-based measures;&#x0a;* goals and care plans related to improving a patient's physical activity level;&#x0a;* orders for interventions seeking to improve a patient's physical activity level; and&#x0a;* processes to support closing the loop and evaluating the success of such interventions. (built Fri, Aug 25, 2023 15:28+0000+00:00) http://hl7.org/fhir/us/physical-activity/STU1/package.tgz http://hl7.org/fhir/us/physical-activity/STU1/package.tgz HL7, Inc 4.0.1 IG Fri, 25 Aug 2023 12:00:00 +1000 GMT hl7.fhir.us.health-care-surveys-reporting#1.0.0 The Health Care Surveys Content IG provides healthcare organizations the necessary data exchange mechanisms to report health care survey data to public health agencies. (built Tue, Aug 22, 2023 19:16+0000+00:00) http://hl7.org/fhir/us/health-care-surveys-reporting/STU1/package.tgz http://hl7.org/fhir/us/health-care-surveys-reporting/STU1/package.tgz HL7, Inc 4.0.1 IG Tue, 22 Aug 2023 12:00:00 +1000 GMT hl7.fhir.uv.ichom-breast-cancer#1.0.0 http://hl7.org/fhir/uv/ichom-breast-cancer/STU1/package.tgz http://hl7.org/fhir/uv/ichom-breast-cancer/STU1/package.tgz HL7, Inc 4.0.1 IG Mon, 21 Aug 2023 12:00:00 +1000 GMT hl7.fhir.us.ph-library#1.0.0 http://hl7.org/fhir/us/ph-library/STU1/package.tgz http://hl7.org/fhir/us/ph-library/STU1/package.tgz HL7, Inc 4.0.1 IG Thu, 17 Aug 2023 12:00:00 +1000 GMT hl7.fhir.us.qicore#6.0.0-ballot 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 Thu, Aug 3, 2023 13:26+0000+00:00) http://hl7.org/fhir/us/qicore/2023Sep/package.tgz http://hl7.org/fhir/us/qicore/2023Sep/package.tgz HL7, Inc 4.0.1 IG Thu, 03 Aug 2023 12:00:00 +1000 GMT hl7.fhir.uv.crmi#1.0.0-ballot 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 Thu, Aug 3, 2023 14:50+0000+00:00) http://hl7.org/fhir/uv/crmi/2023Sep/package.tgz http://hl7.org/fhir/uv/crmi/2023Sep/package.tgz HL7, Inc 4.0.1 IG Thu, 03 Aug 2023 12:00:00 +1000 GMT hl7.fhir.uv.ibcm#1.0.0-ballot http://hl7.org/fhir/uv/ibcm/1.0.0-ballot/package.tgz http://hl7.org/fhir/uv/ibcm/1.0.0-ballot/package.tgz HL7, Inc 5.0.0 IG Tue, 01 Aug 2023 12:00:00 +1000 GMT hl7.fhir.us.bser#2.0.0-ballot http://hl7.org/fhir/us/bser/2023Sep/package.tgz http://hl7.org/fhir/us/bser/2023Sep/package.tgz HL7, Inc 4.0.1 IG Mon, 31 Jul 2023 12:00:00 +1000 GMT hl7.fhir.us.davinci-vbpr#1.0.0-ballot The Da Vinci Fast Healthcare Interoperability Resource (FHIR) Value-Based Performance Reporting Implementation Guide (this IG) describes exchange of value-based performance reports among stakeholders such as payers, providers, and government care programs. (built Mon, Jul 31, 2023 14:29+0000+00:00) http://hl7.org/fhir/us/davinci-vbpr/2023Sep/package.tgz http://hl7.org/fhir/us/davinci-vbpr/2023Sep/package.tgz HL7, Inc 4.0.1 IG Mon, 31 Jul 2023 12:00:00 +1000 GMT hl7.fhir.us.ndh#1.0.0-ballot http://hl7.org/fhir/us/ndh/2023Sep/package.tgz http://hl7.org/fhir/us/ndh/2023Sep/package.tgz HL7, Inc 4.0.1 IG Sun, 30 Jul 2023 12:00:00 +1000 GMT hl7.fhir.uv.shorthand#3.0.0-ballot 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) http://hl7.org/fhir/uv/shorthand/2023Sep/package.tgz http://hl7.org/fhir/uv/shorthand/2023Sep/package.tgz HL7, Inc 4.0.1 IG Sun, 30 Jul 2023 12:00:00 +1000 GMT hl7.fhir.us.codex-radiation-therapy#1.0.0 CodeX™ Radiation Therapy is an initiative intended to assemble a core set of structured data elements for radiation therapy electronic health records. (built Fri, Jul 28, 2023 13:01+0000+00:00) http://hl7.org/fhir/us/codex-radiation-therapy/STU1/package.tgz http://hl7.org/fhir/us/codex-radiation-therapy/STU1/package.tgz HL7, Inc 4.0.1 IG Fri, 28 Jul 2023 12:00:00 +1000 GMT hl7.fhir.us.mcc#1.0.0-ballot2 ### Introduction This HL7&reg; 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. A 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: 1. Query for patient data across providers and compile into a consolidated care plan representation. 2. Encourage capture of and communication of a patient's health concerns and related goals, interventions, and outcomes. 3. 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.) This 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. ### How to Read this Guide and Cautions This 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. ### Value Set Library Rather 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. This 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. ### History of the Care Plan and Electronic Care Plans The 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. Most 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. We 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. ### Project Overview More 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. Care 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. The 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. Initiated 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. The HL7-based activities of the MCC eCare Plan Project include: - Identified use cases to support the documentation and exchange of MCC eCare plan data within EHRs and related systems. - 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. - Develop, test, and ballot an HL7® Fast Health Interoperability Resources (FHIR®) Implementation Guide based on the defined use cases and MCC data elements. Non-HL7 related activities of the MCC eCare Plan project will be facilitated through the [AHRQ eCare Plan Project Confluence](https://ecareplan.ahrq.gov/collaborate): - 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. #### Project Timelines - January 2024: A For comment ballot to gather community input prior to the formal STU Ballot - September 2024: Formal STU Ballot - May 2025 Formal HL7 Publication ### Guidance The 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. #### Relationship to US Core This 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. This 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 ##### General US Core IG Conformance This 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. ##### Provenance This 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). ##### Must Support This IG will adhere to the US Core [Must Support](https://www.hl7.org/fhir/us/core/general-guidance.html#must-support) concept and rules. ### Acknowledgements This 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. This 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) (built Fri, Jul 28, 2023 17:45+0000+00:00) http://hl7.org/fhir/us/mcc/2023Sep/package.tgz http://hl7.org/fhir/us/mcc/2023Sep/package.tgz HL7, Inc 4.0.1 IG Fri, 28 Jul 2023 12:00:00 +1000 GMT hl7.fhir.uv.ae-research-backport-ig#1.0.0-ballot ### 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 Fri, Jul 28, 2023 19:51+0000+00:00) http://hl7.org/fhir/uv/ae-research-backport-ig/2023Sep/package.tgz http://hl7.org/fhir/uv/ae-research-backport-ig/2023Sep/package.tgz HL7, Inc 4.0.1 IG Fri, 28 Jul 2023 12:00:00 +1000 GMT hl7.fhir.uv.ae-research-ig#1.0.0-ballot ### 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 Fri, Jul 28, 2023 21:41+0000+00:00) http://hl7.org/fhir/uv/ae-research-ig/2023Sep/package.tgz http://hl7.org/fhir/uv/ae-research-ig/2023Sep/package.tgz HL7, Inc 5.0.0 IG Fri, 28 Jul 2023 12:00:00 +1000 GMT hl7.fhir.us.sdoh-clinicalcare#2.1.0 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, Jul 27, 2023 20:34+0000+00:00) http://hl7.org/fhir/us/sdoh-clinicalcare/STU2.1/package.tgz http://hl7.org/fhir/us/sdoh-clinicalcare/STU2.1/package.tgz HL7, Inc 4.0.1 IG Thu, 27 Jul 2023 12:00:00 +1000 GMT hl7.fhir.uv.emedicinal-product-info#1.0.0 FHIR Implementation Guide representing how to create Electronic Medicinal Product Information. (built Wed, Jul 26, 2023 13:29+0000+00:00) http://hl7.org/fhir/uv/emedicinal-product-info/STU1/package.tgz http://hl7.org/fhir/uv/emedicinal-product-info/STU1/package.tgz HL7, Inc 5.0.0 IG Wed, 26 Jul 2023 12:00:00 +1000 GMT hl7.fhir.us.cancer-reporting#1.0.0 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 to a central registry, the FHIR Messaging paradigm shall be required; however when sending between LIS and EHR systems, implementors may choose to use alterantive transport and processing modalities, such as FHIR transaciton 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 message bundle and is compliant with FHIR Release 4. (built Tue, Jul 11, 2023 15:47+0000+00:00) http://hl7.org/fhir/us/cancer-reporting/STU1/package.tgz http://hl7.org/fhir/us/cancer-reporting/STU1/package.tgz HL7, Inc 4.0.1 IG Tue, 11 Jul 2023 12:00:00 +1000 GMT hl7.fhir.us.core#6.1.0 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. These 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 Fri, Jun 30, 2023 14:02+0000+00:00) http://hl7.org/fhir/us/core/STU6.1/package.tgz http://hl7.org/fhir/us/core/STU6.1/package.tgz HL7, Inc 4.0.1 IG Fri, 30 Jun 2023 12:00:00 +1000 GMT hl7.fhir.us.medmorph#1.0.0 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) http://hl7.org/fhir/us/medmorph/STU1/package.tgz http://hl7.org/fhir/us/medmorph/STU1/package.tgz HL7, Inc 4.0.1 IG Thu, 08 Jun 2023 12:00:00 +1000 GMT hl7.fhir.us.identity-matching#1.0.0 http://hl7.org/fhir/us/identity-matching/STU1/package.tgz http://hl7.org/fhir/us/identity-matching/STU1/package.tgz HL7, Inc 4.0.1 IG Fri, 02 Jun 2023 12:00:00 +1000 GMT hl7.fhir.us.military-service#1.0.0 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) http://hl7.org/fhir/us/military-service/STU1/package.tgz http://hl7.org/fhir/us/military-service/STU1/package.tgz HL7, Inc 4.0.1 IG Tue, 30 May 2023 12:00:00 +1000 GMT hl7.fhir.us.core#6.1.0-snapshot1 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. These 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 Sat, May 27, 2023 08:07+1000+10:00) http://hl7.org/fhir/us/core/STU6.1-snapshot1/package.tgz http://hl7.org/fhir/us/core/STU6.1-snapshot1/package.tgz HL7, Inc 4.0.1 IG Sat, 27 May 2023 12:00:00 +1000 GMT hl7.fhir.uv.vulcan-rwd#1.0.0 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) http://hl7.org/fhir/uv/vulcan-rwd/STU1/package.tgz http://hl7.org/fhir/uv/vulcan-rwd/STU1/package.tgz HL7, Inc 4.0.1 IG Fri, 26 May 2023 12:00:00 +1000 GMT hl7.fhir.us.specialty-rx#2.0.0 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) http://hl7.org/fhir/us/specialty-rx/STU2/package.tgz http://hl7.org/fhir/us/specialty-rx/STU2/package.tgz HL7, Inc 4.0.1 IG Thu, 04 May 2023 12:00:00 +1000 GMT hl7.fhir.us.core#6.0.0 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. These 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 Wed, May 3, 2023 21:17+0000+00:00) http://hl7.org/fhir/us/core/STU6/package.tgz http://hl7.org/fhir/us/core/STU6/package.tgz HL7, Inc 4.0.1 IG Wed, 03 May 2023 12:00:00 +1000 GMT hl7.fhir.us.sirb#1.0.0 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) http://hl7.org/fhir/us/sirb/STU1/package.tgz http://hl7.org/fhir/us/sirb/STU1/package.tgz HL7, Inc 4.0.1 IG Thu, 20 Apr 2023 12:00:00 +1000 GMT hl7.fhir.us.hai-ltcf#1.1.0 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. As reports are modified and new report types are defined, CDC and Health Level Seven (HL7) will develop and publish additional constraints. Throughout 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. Note 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). ### Relationship to Another Standard HL7 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. In this release, the new forms included in both the CDA and FHIR standards are: * **NHSN HAI LTCF Population Summary Report**: MDRO and CDI LabID Event Reporting Monthly Summary Data for LTCF * **NHSN HAI LTCF Single-Person Event Report**: Laboratory-identified MDRO or CDI Event for LTCF For further details see the [NHSN website](https://www.cdc.gov/nhsn/) for reporting healthcare-associated infections in long-term care facilities. ### Audience The audience for this work is all developers of software systems who want to enable their systems for reporting HAI data to the NHSN. ### Change Notification Process CDC 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. ### Acknowledgements This 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). Special 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. The 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. |-----|-----|-----|-----| |Primary Editor:|Sarah Gaunt|Lantana Consulting Group|sarah.gaunt@lantanagroup.com| |Primary Editor:|Zabrina Gonzaga|Lantana Consulting Group|zabrina.gonzaga@lantanagroup.com| |Primary Editor:|Dave deRoode|Lantana Consulting Group|david.deroode@lantanagroup.com| |Co-Editor:|Jeneita Bell, MD, MPH|CDC|hpq8@cdc.gov| |Co-Editor:|Angella Antilla PhD, MSN|CDC|vtb9@cdc.gov| |Co-Editor:|Daniel Pollock, M.D.|CDC|DPollock@cdc.gov| |Co-Editor:|Ahmed Tahir|Leidos Consultant to CDC/NHSN|nmn8@cdc.gov| |Co-Editor:|Mindy Durrance|Leidos Consultant to CDC/NHSN|mdq1@cdc.gov| |Co-Editor:|Sheri Chernetsky Tejedor, MD|CDC|yei9@cdc.gov| |Co-Editor:|Sheila Abner|CDC|sha8@cdc.gov| |Co-Chair:|Erin Holt MPH|Tennessee Department of Health|erin.holt@tn.gov| |Co-Chair:|Laura Rappleye|Altarum|laura.rappleye@altarum.org| |Co-Chair:|Craig Newman|Altarum|craig.newman@altarum.org| |Co-Chair:|Danny Wise|Allscripts|danny.wise@allscripts.com| |Co-Chair:|Joginder Madra|Madra Consulting Inc.|hl7@madraconsulting.com| |Co-Chair:|Gaye Dolin M.S.N., R.N. |Intelligent Medical Objects |gdolin@imo-online.com| |Co-Chair:|Calvin Beebe|Mayo Clinic|cbeebe@mayo.edu| |Co-Chair:|Austin Kreisler|Leidos Consultant to CDC/NHSN|duz1@cdc.gov| |Co-Chair:|Andrew Statler|Cerner Corp|andrew.statler@cerner.com| |Co-Chair:|Sean McIlvenna| Lantana Consulting Group|sean.mcilvenna@lantanagroup.com| |Co-Chair:|Benjamin Flessner|Redox|benjamin@redoxengine.com| |Co-Editor:|Beau Bannerman|Lantana Consulting Group|beau.bannerman@lantanagroup.com| |Technical Editor:|Diana Wright|Lantana Consulting Group|diana.wright@lantanagroup.com| |Technical Editor:|Chris Hannigan|Lantana Consulting Group|chris.hannigan@lantanagroup.com| (built Wed, Apr 19, 2023 14:58+0000+00:00) http://hl7.org/fhir/us/hai-ltcf/STU1.1/package.tgz http://hl7.org/fhir/us/hai-ltcf/STU1.1/package.tgz HL7, Inc 4.0.1 IG Wed, 19 Apr 2023 12:00:00 +1000 GMT hl7.fhir.uv.smart-app-launch#2.1.0 http://hl7.org/fhir/smart-app-launch/STU2.1/package.tgz http://hl7.org/fhir/smart-app-launch/STU2.1/package.tgz HL7, Inc 4.0.1 IG Tue, 18 Apr 2023 12:00:00 +1000 GMT hl7.fhir.uv.vulcan-schedule#1.0.0 FHIR Implementation Guide representing a Clinical Study Schedule of Activities (built Tue, Apr 18, 2023 16:34+0000+00:00) http://hl7.org/fhir/uv/vulcan-schedule/STU1/package.tgz http://hl7.org/fhir/uv/vulcan-schedule/STU1/package.tgz HL7, Inc 4.0.1 IG Tue, 18 Apr 2023 12:00:00 +1000 GMT hl7.fhir.uv.security-label-ds4p#1.0.0 FHIR data segmentation for privacy security label implementation guide (built Mon, Apr 17, 2023 19:19+0000+00:00) http://hl7.org/fhir/uv/security-label-ds4p/STU1/package.tgz http://hl7.org/fhir/uv/security-label-ds4p/STU1/package.tgz HL7, Inc 4.0.1 IG Mon, 17 Apr 2023 12:00:00 +1000 GMT hl7.fhir.us.qicore#5.0.0 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 Tue, Apr 4, 2023 13:39+0000+00:00) http://hl7.org/fhir/us/qicore/STU5/package.tgz http://hl7.org/fhir/us/qicore/STU5/package.tgz HL7, Inc 4.0.1 IG Tue, 04 Apr 2023 12:00:00 +1000 GMT hl7.fhir.us.davinci-pct#1.0.0 To support the request for cost information for specific services and items 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 Thu, Mar 30, 2023 13:31+0000+00:00) http://hl7.org/fhir/us/davinci-pct/STU1/package.tgz http://hl7.org/fhir/us/davinci-pct/STU1/package.tgz HL7, Inc 4.0.1 IG Thu, 30 Mar 2023 12:00:00 +1100 GMT hl7.fhir.uv.rtls#1.0.0-ballot Description of IG (built Thu, Mar 30, 2023 12:51+0000+00:00) http://hl7.org/fhir/uv/rtls/2023May/package.tgz http://hl7.org/fhir/uv/rtls/2023May/package.tgz HL7, Inc 5.0.0 IG Thu, 30 Mar 2023 12:00:00 +1100 GMT hl7.fhir.us.mihr#1.0.0 ### Scope The 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. This 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. ### Background The 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). The 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. Future 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. ### Maternal Research Use Cases This 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. Initial 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: * 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. * Hypertensive Disorders of pregnancy: This use case focuses on women with a diagnosis of hypertensive disorders of pregnancy. In 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. In the future, the IG will expand this framework to a range of use cases including: * Risks for children related to maternal exposure to medications taken during pregnancy * Potential adverse maternal obstetric history impacts on child outcomes * Access to relevant sensitive health information * Retrospective population-based analysis of inherited disorders * The impacts of [work habits, work environment, and work-associated health insurance](http://hl7.org/fhir/us/odh/) impacts to pregnancy and maternal health This guide fundamentally relies on creating structural relationships between: * Maternal and child records to effectively diagnose and treat otherwise fatal child outcomes * Maternal and child birth records and/or maternal and child death records * Maternal and child records in multiple disparate systems ### Audience The 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. ### Authors & Project Team This table lists the authors, subject matter experts, and the affiliations which contributed to this standard. <style type="text/css"> .tg {border-collapse:collapse;border-spacing:0;} .tg td{border-color:black;border-style:solid;border-width:1px;font-family:Arial, sans-serif;font-size:14px; overflow:hidden;padding:10px 5px;word-break:normal;} .tg th{border-color:black;border-style:solid;border-width:1px;font-family:Arial, sans-serif;font-size:14px; font-weight:normal;overflow:hidden;padding:10px 5px;word-break:normal;} .tg .tg-4erg{border-color:inherit;font-style:italic;font-weight:bold;text-align:left;vertical-align:top} .tg .tg-0r4h{border-color:inherit;font-family:serif !important;font-weight:bold;text-align:left;vertical-align:top} .tg .tg-fymr{border-color:inherit;font-weight:bold;text-align:left;vertical-align:top} .tg .tg-0pky{border-color:inherit;text-align:left;vertical-align:top} </style> <table class="tg"> <thead> <tr> <th class="tg-fymr">Name &amp; Affiliation</th> <th class="tg-0r4h">Role</th> <th class="tg-fymr">Contact</th> </tr> </thead> <tbody> <tr> <td class="tg-4erg">Lantana Consulting Group</td> <td class="tg-0pky"> </td> <td class="tg-0pky"> </td> </tr> <tr> <td class="tg-0pky">Courtney Panaia-Rodi </td> <td class="tg-0pky">Project Executive</td> <td class="tg-0pky">courtney.panaia-rodi@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Wendy Wise</td> <td class="tg-0pky">Project Manager</td> <td class="tg-0pky">wendy.wise@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Lani Johnson</td> <td class="tg-0pky">Associate Project Manager</td> <td class="tg-0pky">lani.johnson@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Rick Geimer</td> <td class="tg-0pky">FHIR Subject Matter Expert</td> <td class="tg-0pky">rick.geimer@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Zabrina Gonzaga</td> <td class="tg-0pky">Terminology Subject Matter Expert</td> <td class="tg-0pky">zabrina.gonzaga@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Sarah Gaunt</td> <td class="tg-0pky">Senior FHIR/CDA Analyst</td> <td class="tg-0pky">sarah.gaunt@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Dave deRoode</td> <td class="tg-0pky">FHIR/CDA Analyst</td> <td class="tg-0pky">david.deroode@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Ming Dunajick</td> <td class="tg-0pky">FHIR/CDA Analyst</td> <td class="tg-0pky">ming.dunajick@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Ruby Nash</td> <td class="tg-0pky">FHIR Analyst</td> <td class="tg-0pky">ruby.nash@lantanagroup.com</td> </tr> <tr> <td class="tg-4erg">Office of the Assistant Secretary for Planning and Evaluation (ASPE)</td> <td class="tg-0pky"> </td> <td class="tg-0pky"> </td> </tr> <tr> <td class="tg-0pky">Violanda Grigorescu, MD, MSPH</td> <td class="tg-0pky">Senior Health Scientist <br>Division of Healthcare Quality and Outcomes, Office of Health Policy</td> <td class="tg-0pky">violanda.grigorescu@hhs.gov</td> </tr> <tr> <td class="tg-4erg">Centers for Disease Control and Prevention (CDC)</td> <td class="tg-0pky"> </td> <td class="tg-0pky"> </td> </tr> <tr> <td class="tg-0pky">Margaret Lampe, RN, MPH</td> <td class="tg-0pky">Nurse Epidemiologist &amp; Project Officer <br>Perinatal HIV Prevention Program</td> <td class="tg-0pky">mol0@cdc.gov</td> </tr> <tr> <td class="tg-0pky">Lisa Romero, DrPH</td> <td class="tg-0pky">Health Scientist <br>Division of Adolescent School Health</td> <td class="tg-0pky">eon1@cdc.gov</td> </tr> <tr> <td class="tg-4erg">National Institutes of Health (NIH) <br>Eunice Kennedy Shriver National Institute of Child Health and Human Development (NICHD) <br>National Information Center on Health Services Research and Health Care Technology (NICHSR)</td> <td class="tg-0pky"> </td> <td class="tg-0pky"> </td> </tr> <tr> <td class="tg-0pky">Alison Cernich</td> <td class="tg-0pky">NICHD Deputy Director</td> <td class="tg-0pky">alison.cernich@nih.hhs.gov</td> </tr> <tr> <td class="tg-0pky">John (Jack) Moye, Jr., MD</td> <td class="tg-0pky">Acting Director - National Children's Study <br>NICHD Medical Officer - Maternal &amp; Pediatric Infectious Disease Branch</td> <td class="tg-0pky">moyej@exchange.nih.gov</td> </tr> <tr> <td class="tg-0pky">Nahida Chakhtoura, MD, MsGH</td> <td class="tg-0pky">NICHD Medical Officer <br>Maternal and Pediatric Infectious Disease Branch</td> <td class="tg-0pky">nahida.chakhtoura@nih.gov</td> </tr> <tr> <td class="tg-0pky">Juanita Chinn, PhD</td> <td class="tg-0pky">NICHD Program Director <br>Population Dynamics Branch</td> <td class="tg-0pky">juanita.chinn@nih.gov</td> </tr> <tr> <td class="tg-0pky">Valerie Cotton</td> <td class="tg-0pky">NICHD Deputy Director <br>Office of Data Science and Sharing</td> <td class="tg-0pky">valerie.cotton@nih.gov</td> </tr> <tr> <td class="tg-0pky">Liz Amos, MLIS</td> <td class="tg-0pky">Special Assistant to the Chief Health Data Standards Officer <br>National Library of Medicine</td> <td class="tg-0pky">liz.amos@nih.gov</td> </tr> <tr> <td class="tg-4erg">Office of the National Coordinator for Health IT (ONC)</td> <td class="tg-0pky"> </td> <td class="tg-0pky"> </td> </tr> <tr> <td class="tg-0pky">Carmen Smiley</td> <td class="tg-0pky">IT Specialist (Systems Analysis)</td> <td class="tg-0pky">carmen.smiley@hhs.gov</td> </tr> <tr> <td class="tg-0pky">Rachel Abbey</td> <td class="tg-0pky">Public Health Analyst &amp; Program Officer</td> <td class="tg-0pky">rachel.abbey@hhs.gov</td> </tr> <tr> <td class="tg-0pky">Stephanie Garcia</td> <td class="tg-0pky">Senior Program Analyst</td> <td class="tg-0pky">stephanie.garcia@hhs.gov</td> </tr> <tr> <td class="tg-0pky">Brittney Boakye, MPH</td> <td class="tg-0pky">Program Assistant <br>Scientific Advancement Branch</td> <td class="tg-0pky">brittney.boakye@hhs.gov<br></td> </tr> <tr> <td class="tg-0pky">Alan Taylor</td> <td class="tg-0pky">Medical Informatics Officer, Standards and Terminology</td> <td class="tg-0pky">albert.taylor@hhs.gov</td> </tr> </tbody> </table> ### Acknowledgements This 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. The 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. Health Level Seven, HL7, CDA, CCD, FHIR and the [FLAME DESIGN] are registered trademarks of Health Level Seven International, registered in the US Trademark Office. This 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. This 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) http://hl7.org/fhir/us/mihr/STU1/package.tgz http://hl7.org/fhir/us/mihr/STU1/package.tgz HL7, Inc 4.0.1 IG Wed, 29 Mar 2023 12:00:00 +1100 GMT hl7.fhir.us.registry-protocols#1.0.0-ballot 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 Wed, Mar 29, 2023 01:16+0000+00:00) http://hl7.org/fhir/us/registry-protocols/2023May/package.tgz http://hl7.org/fhir/us/registry-protocols/2023May/package.tgz HL7, Inc 4.0.1 IG Wed, 29 Mar 2023 12:00:00 +1100 GMT hl7.fhir.uv.ehrs-rle#1.1.0-ballot EHRS Functional Model - Record Lifecycle Events - FHIR Implementation Guide (built Wed, Mar 29, 2023 18:54+0000+00:00) http://hl7.org/fhir/uv/ehrs-rle/2023May/package.tgz http://hl7.org/fhir/uv/ehrs-rle/2023May/package.tgz HL7, Inc 5.0.0 IG Wed, 29 Mar 2023 12:00:00 +1100 GMT hl7.fhir.us.davinci-ra#2.0.0-ballot 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 Tue, Mar 28, 2023 02:00+0000+00:00) http://hl7.org/fhir/us/davinci-ra/2023May/package.tgz http://hl7.org/fhir/us/davinci-ra/2023May/package.tgz HL7, Inc 4.0.1 IG Tue, 28 Mar 2023 12:00:00 +1100 GMT hl7.fhir.us.mcode#3.0.0-ballot 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 Tue, Mar 28, 2023 19:23+0000+00:00) http://hl7.org/fhir/us/mcode/2023May/package.tgz http://hl7.org/fhir/us/mcode/2023May/package.tgz HL7, Inc 4.0.1 IG Tue, 28 Mar 2023 12:00:00 +1100 GMT hl7.fhir.us.physical-activity#1.0.0-ballot This implementation guide provides standardization around patient physical activity, including:&#x0a;* measures for recording a patient's level of physical activity;&#x0a;* measures to support assertions of physical activity, including device-based measures;&#x0a;* goals and care plans related to improving a patient's physical activity level;&#x0a;* orders for interventions seeking to improve a patient's physical activity level; and&#x0a;* processes to support closing the loop and evaluating the success of such interventions. (built Tue, Mar 28, 2023 18:26+0000+00:00) http://hl7.org/fhir/us/physical-activity/2023May/package.tgz http://hl7.org/fhir/us/physical-activity/2023May/package.tgz HL7, Inc 4.0.1 IG Tue, 28 Mar 2023 12:00:00 +1100 GMT hl7.fhir.us.ccda#1.2.0-ballot 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. This 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). The 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. We 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. ### Scope To represent Consolidated CDA Templates for Clinical Notes (C-CDA) 2.1 templates using FHIR profiles. This first stage of the project defines all the C-CDA document-level profiles on the Composition resource and contained sections. Any 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. For further information see the C-CDA specification here: http://www.hl7.org/implement/standards/product_brief.cfm?product_id=408. (built Mon, Mar 27, 2023 20:41+0000+00:00) http://hl7.org/fhir/us/ccda/2023May/package.tgz http://hl7.org/fhir/us/ccda/2023May/package.tgz HL7, Inc 4.0.1 IG Mon, 27 Mar 2023 12:00:00 +1100 GMT hl7.fhir.us.odh#1.3.0 **HL7 FHIR Profile: Occupational Data for Health (ODH), Release 1.3 (Standard for Trial Use)** This 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. **Introduction and Guidance** This 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. This 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. While 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. **Background** The 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. The 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. **Scope** The 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: • Employment Status • Retirement Date • Combat Zone Period • Past or Present Job for the patient or a household member, which includes: o Past or Present Job Occupation o Past or Present Job Industry o Work Classification o Work Schedule, which includes: - Weekly Work Days - Daily Work Hours o Job Duty o Occupational Hazard o Employer name o Employer address o Related Subject (when it is Past or Present Job of a household member of the person) o Start/End Dates • Usual Work of the patient or a household member, which includes: o Usual Occupation o Usual Industry o Usual Occupation Duration o Related Subject (when it is Usual Work of a household member of the person) o Start Date **Known Issues and Limitations** This 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. While multiple retirement dates are supported, the retirement date is not linked to any specific job, or usual occupation. **Credits** Co-Editor: Lori Reed-Fourquet e-HealthSign, LLC lfourquet@ehealthsign.com Co-Editor: Rob Hausam Hausam Consulting rob@hausamconsulting.com Co-Editor: Mark Kramer MITRE Corporation mkramer@mitre.org This 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). The 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. **Authors** Name Email/URL HL7 International - Public Health http://www.hl7.org/Special/committees/pher (built Mon, Mar 27, 2023 09:54+1100+11:00) http://hl7.org/fhir/us/odh/STU1.3/package.tgz http://hl7.org/fhir/us/odh/STU1.3/package.tgz HL7, Inc 4.0.1 IG Mon, 27 Mar 2023 12:00:00 +1100 GMT hl7.fhir.r5.core#5.0.0 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) http://hl7.org/fhir/R5/hl7.fhir.r5.core.tgz http://hl7.org/fhir/R5/hl7.fhir.r5.core.tgz HL7, Inc 5.0.0 fhir.core Sun, 26 Mar 2023 12:00:00 +1100 GMT hl7.fhir.r5.expansions#5.0.0 Expansions for the 5.0.0 version of the FHIR standard (built Sun, Mar 26, 2023 15:21+1100+11:00) http://hl7.org/fhir/R5/hl7.fhir.r5.expansions.tgz http://hl7.org/fhir/R5/hl7.fhir.r5.expansions.tgz HL7, Inc 5.0.0 fhir.core Sun, 26 Mar 2023 12:00:00 +1100 GMT hl7.fhir.r5.examples#5.0.0 Examples for the 5.0.0 version of the FHIR standard (built Sun, Mar 26, 2023 15:21+1100+11:00) http://hl7.org/fhir/R5/hl7.fhir.r5.examples.tgz http://hl7.org/fhir/R5/hl7.fhir.r5.examples.tgz HL7, Inc 5.0.0 fhir.core Sun, 26 Mar 2023 12:00:00 +1100 GMT hl7.fhir.r5.search#5.0.0 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) http://hl7.org/fhir/R5/hl7.fhir.r5.search.tgz http://hl7.org/fhir/R5/hl7.fhir.r5.search.tgz HL7, Inc 5.0.0 fhir.core Sun, 26 Mar 2023 12:00:00 +1100 GMT hl7.fhir.core#5.0.0 Group Wrapper that includes all the R5 packages http://hl7.org/fhir/R5/package.tgz http://hl7.org/fhir/R5/package.tgz HL7, Inc 5.0.0 fhir.core Sun, 26 Mar 2023 12:00:00 +1100 GMT hl7.fhir.uv.extensions#1.0.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00) http://hl7.org/fhir/extensions/1.0.0/package.tgz http://hl7.org/fhir/extensions/1.0.0/package.tgz HL7, Inc 5.0.0 IG Sun, 26 Mar 2023 12:00:00 +1100 GMT hl7.fhir.uv.ipa#1.0.0 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 Sun, Mar 26, 2023 20:50+0000+00:00) http://hl7.org/fhir/uv/ipa/STU1/package.tgz http://hl7.org/fhir/uv/ipa/STU1/package.tgz HL7, Inc 4.0.1 IG Sun, 26 Mar 2023 12:00:00 +1100 GMT hl7.fhir.us.home-lab-report#1.0.0 |Implementation Guide (IG) Characteristic | Value | |------------------------------------------------------|--------------------------------------------| |**FHIR Version:** | FHIR R4 | |**IG Realm:** | US | |**IG Type:** | STU Ballot | |**Exchange Methods:** | RESTfulAPI, Messages, Transactions, Tasks | |**IG Note:** | This HL7 FHIR Guide utilizes and adopts guidance or profiles developed in the US Core FHIR&reg; Implementation Guide. This FHIR IG has narrative pages describing the HL7 V2 Message for At-Home In-Vitro Test Reporting and provides some example messages. Presently public health departments usually only can handle and store HL7 V2| {:.table-striped} |IG Dependencies | |----------------------------------| | [HL7 FHIR US Core Version 5.0.1](http://hl7.org/fhir/us/core/STU5.0.1/) | {:.table-striped} ### Background Point-of-care (POC) and At-Home In-Vitro Tests offer increased accessibility to needed diagnostic solutions during a pandemic. Test results provide value to both the individual taking the tests and also to public health authorities responsible for coordinating a regional and national response. Digital platforms are being developed that allow individual test results, with permission of the individual, to be captured, organized, and transmitted to public health systems. Test manufacturers, working in partnership with these digital platforms, are seeking guidance on how to send test results. With multiple tests already entering the market, there is a need for a unified strategy on data flow of test results from the apps to downstream systems. A national data exchange standard should be supported that guides data exchange from test results residing on individual users’ digital test applications to public health authorities, at both the federal and regional levels. ### Introduction This implementation guide (IG) constrains the FHIR [US Core Diagnostic Report for Laboratory Results](http://hl7.org/fhir/us/core/StructureDefinition/us-core-diagnosticreport-lab) and the [US Core Laboratory Observation Profile](http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab) for use in transmitting At-Home In-Vitro Test results to local, state, territorial and federal health agencies. The IG will be be used in real world testing. It was developed as part of a collaborative project with the NIH/NIBIB, ONC, a vendor manufacturer of diagnostic healthcare products that makes one of the FDA approved At-Home In-Vitro Test kits, and an app developer who is a leading provider of secure interoperability solutions. The intention of this guide is to assist developers in producing and sending standardized FHIR test result data from tests perfomed at home. FHIR eases app development and the FHIR US Core IG is in a rapid adoption curve. This guide points to already existing US Core Guidance and other guidance with respect to FHIR Parameters, FHIR operations, and RESTful and SMART on FHIR information. Due to Public Health Departments' familiarity with V2, a test implementation project related to this implementation guide will initially send COVID-19 At-Home In-Vitro Test Reports as V2 lab messages. Longer term the intent is to leverage FHIR for app creativity, growth, and interoperability. For as long as needed to comply with Public Health Department dependecies on V2, the apps will be designed to transform from FHIR to V2. In addition, as a parallel effort, a V2 <-> FHIR data mapping table has been developed [In-Vitro At-Home Test V2 FHIR Mapping.xlsx]. **Please note** : This guide is a framework for future work. It contains "framework" profiles that contain constraints common to all At-Home In-Vitro Test Reporting use cases. These framework profiles can be further constrained to a particular use case such as the COVID-19 At-Home In-Vitro Test Reporting use case. The COVID-19 use case profiles have been created and included in this guide. ### Further Information [RADx® MARS - Mobile Application Reporting through Standards](https://www.nibib.nih.gov/covid-19/radx-tech-program/mars) [LOINC In Vitro Diagnostic (LIVD) Test Code Mapping for SARS-CoV-2 Tests](https://www.cdc.gov/csels/dls/sars-cov-2-livd-codes.html) [Test-Specific HL7v2 Field Values Tool](https://app.powerbigov.us/view?r=eyJrIjoiNjQyZjBkOGEtNjE0ZS00NjUyLTg3NjEtZTIxN2JmODE0ZGE1IiwidCI6IjE0Yjc3NTc4LTk3NzMtNDJkNS04NTA3LTI1MWNhMmRjMmIwNiJ9&pageName=ReportSectionhttps://app.powerbigov.us/view?r=eyJrIjoiNjQyZjBkOGEtNjE0ZS00NjUyLTg3NjEtZTIxN2JmODE0ZGE1IiwidCI6IjE0Yjc3NTc4LTk3NzMtNDJkNS04NTA3LTI1MWNhMmRjMmIwNiJ9&pageName=ReportSection3147535a75468ee60d16) ### Acknowledgements/Primary Authors * [NIBIB-Interagency Project Team](mailto:krishna.Juluru@pif.gov) * [CareEvolution](https://careevolution.com) * [Association of Public Health Laboratories](https://www.aphl.org/Pages/default.aspx) * [Gay Dolin MSN RN (Namaste Informatics)](mailto:gdolin@NamasteInformatics.com) * [Sarah Gaunt](mailto:sarah.gaunt@lantanaconsulting.com) (built Sat, Mar 25, 2023 16:44+0000+00:00) http://hl7.org/fhir/us/home-lab-report/STU1/package.tgz http://hl7.org/fhir/us/home-lab-report/STU1/package.tgz HL7, Inc 4.0.1 IG Sat, 25 Mar 2023 12:00:00 +1100 GMT hl7.fhir.us.vrdr#2.1.0 http://hl7.org/fhir/us/vrdr/STU2.1/package.tgz http://hl7.org/fhir/us/vrdr/STU2.1/package.tgz HL7, Inc 4.0.1 IG Fri, 24 Mar 2023 12:00:00 +1100 GMT hl7.fhir.us.davinci-cdex#2.0.0 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 Wed, Mar 22, 2023 00:14+1100+11:00) http://hl7.org/fhir/us/davinci-cdex/STU2/package.tgz http://hl7.org/fhir/us/davinci-cdex/STU2/package.tgz HL7, Inc 4.0.1 IG Wed, 22 Mar 2023 12:00:00 +1100 GMT hl7.fhir.us.mcode#2.1.0 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 Tue, Mar 21, 2023 04:49+1100+11:00) http://hl7.org/fhir/us/mcode/STU2.1/package.tgz http://hl7.org/fhir/us/mcode/STU2.1/package.tgz HL7, Inc 4.0.1 IG Tue, 21 Mar 2023 12:00:00 +1100 GMT hl7.fhir.uv.extensions#0.1.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sat, Mar 4, 2023 10:11+1100+11:00) http://hl7.org/fhir/extensions/0.1.0/package.tgz http://hl7.org/fhir/extensions/0.1.0/package.tgz HL7, Inc 5.0.0 IG Sat, 04 Mar 2023 12:00:00 +1100 GMT hl7.fhir.r5.core#5.0.0-draft-final FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (built Wed, Mar 1, 2023 23:03+1100+11:00) http://hl7.org/fhir/5.0.0-draft-final/hl7.fhir.r5.core.tgz http://hl7.org/fhir/5.0.0-draft-final/hl7.fhir.r5.core.tgz HL7, Inc 5.0.0-draft-final fhir.core Wed, 01 Mar 2023 12:00:00 +1100 GMT hl7.fhir.r5.expansions#5.0.0-draft-final Expansions for the 5.0.0-draft-final version of the FHIR standard (built Wed, Mar 1, 2023 23:03+1100+11:00) http://hl7.org/fhir/5.0.0-draft-final/hl7.fhir.r5.expansions.tgz http://hl7.org/fhir/5.0.0-draft-final/hl7.fhir.r5.expansions.tgz HL7, Inc 5.0.0-draft-final fhir.core Wed, 01 Mar 2023 12:00:00 +1100 GMT hl7.fhir.r5.examples#5.0.0-draft-final Examples for the 5.0.0-draft-final version of the FHIR standard (built Wed, Mar 1, 2023 23:03+1100+11:00) http://hl7.org/fhir/5.0.0-draft-final/hl7.fhir.r5.examples.tgz http://hl7.org/fhir/5.0.0-draft-final/hl7.fhir.r5.examples.tgz HL7, Inc 5.0.0-draft-final fhir.core Wed, 01 Mar 2023 12:00:00 +1100 GMT hl7.fhir.r5.search#5.0.0-draft-final FHIR 5.0.0-draft-final package : Search Parameters (break out combined parmaeters for server execution convenience) (built Wed, Mar 1, 2023 23:03+1100+11:00) http://hl7.org/fhir/5.0.0-draft-final/hl7.fhir.r5.search.tgz http://hl7.org/fhir/5.0.0-draft-final/hl7.fhir.r5.search.tgz HL7, Inc 5.0.0-draft-final fhir.core Wed, 01 Mar 2023 12:00:00 +1100 GMT hl7.fhir.core#5.0.0-draft-final FHIR Core - Group package for R5 Final QA http://hl7.org/fhir/5.0.0-draft-final/package.tgz http://hl7.org/fhir/5.0.0-draft-final/package.tgz HL7, Inc 5.0.0-draft-final fhir.core Wed, 01 Mar 2023 12:00:00 +1100 GMT hl7.fhir.uv.subscriptions-backport#1.1.0 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 Wed, Jan 11, 2023 15:34+1100+11:00) http://hl7.org/fhir/uv/subscriptions-backport/STU1.1/package.tgz http://hl7.org/fhir/uv/subscriptions-backport/STU1.1/package.tgz HL7, Inc 4.3.0 IG Wed, 11 Jan 2023 12:00:00 +1100 GMT hl7.fhir.us.hai-ltcf#1.0.0 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. As reports are modified and new report types are defined, CDC and Health Level Seven (HL7) will develop and publish additional constraints. Throughout 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. Note 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). ### Relationship to Another Standard HL7 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. In this release, the new forms included in both the CDA and FHIR standards are: * **NHSN HAI LTCF Population Summary Report**: MDRO and CDI LabID Event Reporting Monthly Summary Data for LTCF * **NHSN HAI LTCF Single-Person Event Report**: Laboratory-identified MDRO or CDI Event for LTCF For further details see the [NHSN website](https://www.cdc.gov/nhsn/) for reporting healthcare-associated infections in long-term care facilities. ### Audience The audience for this work is all developers of software systems who want to enable their systems for reporting HAI data to the NHSN. ### Change Notification Process CDC 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. ### Acknowledgements This 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). Special 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. The 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. |-----|-----|-----|-----| |Primary Editor:|Sarah Gaunt|Lantana Consulting Group|sarah.gaunt@lantanagroup.com| |Primary Editor:|Zabrina Gonzaga|Lantana Consulting Group|zabrina.gonzaga@lantanagroup.com| |Primary Editor:|Dave deRoode|Lantana Consulting Group|david.deroode@lantanagroup.com| |Co-Editor:|Jeneita Bell, MD, MPH|CDC|hpq8@cdc.gov| |Co-Editor:|Angella Antilla PhD, MSN|CDC|vtb9@cdc.gov| |Co-Editor:|Daniel Pollock, M.D.|CDC|DPollock@cdc.gov| |Co-Editor:|Ahmed Tahir|Leidos Consultant to CDC/NHSN|nmn8@cdc.gov| |Co-Editor:|Mindy Durrance|Leidos Consultant to CDC/NHSN|mdq1@cdc.gov| |Co-Editor:|Sheri Chernetsky Tejedor, MD|CDC|yei9@cdc.gov| |Co-Editor:|Sheila Abner|CDC|sha8@cdc.gov| |Co-Chair:|Erin Holt MPH|Tennessee Department of Health|erin.holt@tn.gov| |Co-Chair:|Laura Rappleye|Altarum|laura.rappleye@altarum.org| |Co-Chair:|Craig Newman|Altarum|craig.newman@altarum.org| |Co-Chair:|Danny Wise|Allscripts|danny.wise@allscripts.com| |Co-Chair:|Joginder Madra|Madra Consulting Inc.|hl7@madraconsulting.com| |Co-Chair:|Gaye Dolin M.S.N., R.N. |Intelligent Medical Objects |gdolin@imo-online.com| |Co-Chair:|Calvin Beebe|Mayo Clinic|cbeebe@mayo.edu| |Co-Chair:|Austin Kreisler|Leidos Consultant to CDC/NHSN|duz1@cdc.gov| |Co-Chair:|Andrew Statler|Cerner Corp|andrew.statler@cerner.com| |Co-Chair:|Sean McIlvenna| Lantana Consulting Group|sean.mcilvenna@lantanagroup.com| |Co-Chair:|Benjamin Flessner|Redox|benjamin@redoxengine.com| |Co-Editor:|Beau Bannerman|Lantana Consulting Group|beau.bannerman@lantanagroup.com| |Technical Editor:|Diana Wright|Lantana Consulting Group|diana.wright@lantanagroup.com| |Technical Editor:|Chris Hannigan|Lantana Consulting Group|chris.hannigan@lantanagroup.com| (built Mon, Jan 9, 2023 21:55+0000+00:00) http://hl7.org/fhir/us/hai-ltcf/STU1/package.tgz http://hl7.org/fhir/us/hai-ltcf/STU1/package.tgz HL7, Inc 4.0.1 IG Mon, 09 Jan 2023 12:00:00 +1100 GMT hl7.fhir.r5.core#5.0.0-snapshot3 FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (built Wed, Dec 14, 2022 07:12+1100+11:00) http://hl7.org/fhir/5.0.0-snapshot3/hl7.fhir.r5.core.tgz http://hl7.org/fhir/5.0.0-snapshot3/hl7.fhir.r5.core.tgz HL7, Inc 5.0.0-snapshot3 fhir.core Wed, 14 Dec 2022 12:00:00 +1100 GMT hl7.fhir.r5.expansions#5.0.0-snapshot3 Expansions for the 5.0.0-snapshot3 version of the FHIR standard (built Wed, Dec 14, 2022 07:12+1100+11:00) http://hl7.org/fhir/5.0.0-snapshot3/hl7.fhir.r5.expansions.tgz http://hl7.org/fhir/5.0.0-snapshot3/hl7.fhir.r5.expansions.tgz HL7, Inc 5.0.0-snapshot3 fhir.core Wed, 14 Dec 2022 12:00:00 +1100 GMT hl7.fhir.r5.examples#5.0.0-snapshot3 Examples for the 5.0.0-snapshot3 version of the FHIR standard (built Wed, Dec 14, 2022 07:12+1100+11:00) http://hl7.org/fhir/5.0.0-snapshot3/hl7.fhir.r5.examples.tgz http://hl7.org/fhir/5.0.0-snapshot3/hl7.fhir.r5.examples.tgz HL7, Inc 5.0.0-snapshot3 fhir.core Wed, 14 Dec 2022 12:00:00 +1100 GMT hl7.fhir.core#5.0.0-snapshot3 FHIR Core - Group package for Snapshot 3: Connectathon 32 Base http://hl7.org/fhir/5.0.0-snapshot3/package.tgz http://hl7.org/fhir/5.0.0-snapshot3/package.tgz HL7, Inc 5.0.0-snapshot3 fhir.core Wed, 14 Dec 2022 12:00:00 +1100 GMT hl7.fhir.us.hsds#1.0.0-ballot fhir-human-services-directory (built Thu, Dec 8, 2022 20:19+0000+00:00) http://hl7.org/fhir/us/hsds/2023Jan/package.tgz http://hl7.org/fhir/us/hsds/2023Jan/package.tgz HL7, Inc 4.0.1 IG Thu, 08 Dec 2022 12:00:00 +1100 GMT hl7.fhir.uv.ehrs-rle#1.0.0-ballot EHRS Functional Model - Record Lifecycle Events - FHIR Implementation Guide (built Wed, Dec 7, 2022 16:55+0000+00:00) http://hl7.org/fhir/uv/ehrs-rle/2023Jan/package.tgz http://hl7.org/fhir/uv/ehrs-rle/2023Jan/package.tgz HL7, Inc 4.0.1 IG Wed, 07 Dec 2022 12:00:00 +1100 GMT hl7.fhir.uv.ichom-breast-cancer#1.0.0-ballot http://hl7.org/fhir/uv/ichom-breast-cancer/2023Jan/package.tgz http://hl7.org/fhir/uv/ichom-breast-cancer/2023Jan/package.tgz HL7, Inc 4.0.1 IG Wed, 07 Dec 2022 12:00:00 +1100 GMT hl7.fhir.uv.pddi#1.0.0-ballot http://hl7.org/fhir/uv/pddi/2023Jan/package.tgz http://hl7.org/fhir/uv/pddi/2023Jan/package.tgz HL7, Inc 4.0.1 IG Wed, 07 Dec 2022 12:00:00 +1100 GMT hl7.fhir.us.core#6.0.0-ballot 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. These 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 Mon, Dec 5, 2022 15:26+0000+00:00) http://hl7.org/fhir/us/core/2023Jan/package.tgz http://hl7.org/fhir/us/core/2023Jan/package.tgz HL7, Inc 4.0.1 IG Mon, 05 Dec 2022 12:00:00 +1100 GMT hl7.fhir.us.davinci-atr#2.0.0-ballot Exchange of member attribution list between payers and providers (built Mon, Dec 5, 2022 16:58+0000+00:00) http://hl7.org/fhir/us/davinci-atr/2023Jan/package.tgz http://hl7.org/fhir/us/davinci-atr/2023Jan/package.tgz HL7, Inc 4.0.1 IG Mon, 05 Dec 2022 12:00:00 +1100 GMT hl7.fhir.us.davinci-deqm#4.0.0-ballot http://hl7.org/fhir/us/davinci-deqm/2023Jan/package.tgz http://hl7.org/fhir/us/davinci-deqm/2023Jan/package.tgz HL7, Inc 4.0.1 IG Mon, 05 Dec 2022 12:00:00 +1100 GMT hl7.fhir.us.cqfmeasures#4.0.0-ballot The Fast Healthcare Interoperability Resource (FHIR) Quality Measure Implementation Guide (this IG) describes an approach to representing electronic Clinical Quality Measures (eCQMs) 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 Sun, Dec 4, 2022 15:27+0000+00:00) http://hl7.org/fhir/us/cqfmeasures/2023Jan/package.tgz http://hl7.org/fhir/us/cqfmeasures/2023Jan/package.tgz HL7, Inc 4.0.1 IG Sun, 04 Dec 2022 12:00:00 +1100 GMT hl7.fhir.us.mcc#1.0.0-ballot ### Introduction This HL7&reg; 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. A 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: 1. Query for patient data across providers and compile into a consolidated care plan representation. 2. Encourage capture of and communication of a patient's health concerns and related goals, interventions, and outcomes. 3. 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.) This 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. ### How to Read this Guide and Cautions This 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. ### Value Set Library Rather 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. This 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. ### History of the Care Plan and Electronic Care Plans The 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. Most 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. We 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. ### Project Overview More 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. Care 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. The 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. Initiated 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. The HL7-based activities of the MCC eCare Plan Project include: - Identified use cases to support the documentation and exchange of MCC eCare plan data within EHRs and related systems. - 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. - Develop, test, and ballot an HL7® Fast Health Interoperability Resources (FHIR®) Implementation Guide based on the defined use cases and MCC data elements. Non-HL7 related activities of the MCC eCare Plan project will be facilitated through the [AHRQ eCare Plan Project Confluence](https://ecareplan.ahrq.gov/collaborate): - 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. #### Project Timelines - January 2024: A For comment ballot to gather community input prior to the formal STU Ballot - September 2024: Formal STU Ballot - May 2025 Formal HL7 Publication ### Guidance The 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. #### Relationship to US Core This 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. This 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 ##### General US Core IG Conformance This 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. ##### Provenance This 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). ##### Must Support This IG will adhere to the US Core [Must Support](https://www.hl7.org/fhir/us/core/general-guidance.html#must-support) concept and rules. ### Acknowledgements This 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. This 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) **Implementation Guide Contributors:** <table border="1" cellspacing="0" style="width:100.0%"> <tbody> <tr> <td style="background-color:#d9e2f3; width:89.75pt"> <p><strong>Contributor</strong></p> </td> <td style="background-color:#d9e2f3; width:148.5pt"> <p><strong>Organization</strong></p> </td> <td style="background-color:#d9e2f3; width:229.5pt"> <p><strong>Role</strong></p> </td> <td style="background-color:#d9e2f3; width:211.5pt"> <p><strong>email</strong></p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Jenna Norton</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>NIH/NIDDK</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Project Champion</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>jenna.norton@nih.gov</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Kevin Abbott</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>NIH/NIDDK</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Project Champion</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>kevin.abbott@nih.gov</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Arlene Bierman</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>AHRQ</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Project Champion</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>arlene.bierman@ahrq.hhs.gov</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Evelyn Gallego</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>EMI Advisors</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Project Champion</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>evelyn.gallego@emiadvisors.net</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Gay Dolin</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>Namaste Informatics</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>IG Design Lead</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>gdolin@namasteinformatics.com</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Bret Heale</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>Humanized Health Consulting</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>IG Developer</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>bheale@humanizedhealthconsulting.com</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Himali Saitwal</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>EMI Advisors</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Terminologist</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>himali.saitwal@emiadvisors.net</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Sara Armson</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>RTI/ONC</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Terminologist</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>sara.armson@hhs.gov</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Karen Bertodatti</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>EMI Advisors</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Project Manager</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>karen.bertodatti@emiadvisors.net</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Savanah Mueller</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>EMI Advisors</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Analyst</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>savanah.mueller@emiadvisors.net</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Emma Jones</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>Allscripts Veradigm</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Domain Expert</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>emma.jones@allscripts.com</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Dave Carlson</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>Clinical Cloud Solutions</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Solutions Architect, Test Implementations</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>dcarlson@clinicalcloud.solutions</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Sean Muir</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>JKM Software</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Developer, Test Implementations</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>sean.muir@jkmsoftware.com</p> </td> </tr> </tbody> </table> (built Sun, Dec 4, 2022 03:53+0000+00:00) http://hl7.org/fhir/us/mcc/2023Jan/package.tgz http://hl7.org/fhir/us/mcc/2023Jan/package.tgz HL7, Inc 4.0.1 IG Sun, 04 Dec 2022 12:00:00 +1100 GMT hl7.fhir.uv.emedicinal-product-info#1.0.0-ballot BR&R creates and promotes standards to facilitate biomedical research and any subsequent regulatory evaluation of the safety, efficacy and quality of medical products that may arise from research. (built Sun, Dec 4, 2022 18:48+0000+00:00) http://hl7.org/fhir/uv/emedicinal-product-info/2023Jan/package.tgz http://hl7.org/fhir/uv/emedicinal-product-info/2023Jan/package.tgz HL7, Inc 5.0.0-ballot IG Sun, 04 Dec 2022 12:00:00 +1100 GMT hl7.fhir.uv.smart-app-launch#2.1.0-ballot http://hl7.org/fhir/smart-app-launch/2023Jan/package.tgz http://hl7.org/fhir/smart-app-launch/2023Jan/package.tgz HL7, Inc 4.0.1 IG Sun, 04 Dec 2022 12:00:00 +1100 GMT hl7.fhir.uv.vulcan-rwd#1.0.0-ballot 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 Sun, Dec 4, 2022 19:33+0000+00:00) http://hl7.org/fhir/uv/vulcan-rwd/2023Jan/package.tgz http://hl7.org/fhir/uv/vulcan-rwd/2023Jan/package.tgz HL7, Inc 4.0.1 IG Sun, 04 Dec 2022 12:00:00 +1100 GMT hl7.fhir.uv.vulcan-schedule#1.0.0-ballot FHIR Implementation Guide representing a Clinical Study Schedule of Activites (built Sun, Dec 4, 2022 20:06+0000+00:00) http://hl7.org/fhir/uv/vulcan-schedule/2023Jan/package.tgz http://hl7.org/fhir/uv/vulcan-schedule/2023Jan/package.tgz HL7, Inc 4.0.1 IG Sun, 04 Dec 2022 12:00:00 +1100 GMT hl7.fhir.us.carin-bb#2.0.0 CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) (built Mon, Nov 28, 2022 15:15+0000+00:00) http://hl7.org/fhir/us/carin-bb/STU2/package.tgz http://hl7.org/fhir/us/carin-bb/STU2/package.tgz HL7, Inc 4.0.1 IG Mon, 28 Nov 2022 12:00:00 +1100 GMT hl7.fhir.uv.ips#1.1.0 International Patient Summary (IPS) FHIR Implementation Guide (built Tue, Nov 22, 2022 03:24+0000+00:00) http://hl7.org/fhir/uv/ips/STU1.1/package.tgz http://hl7.org/fhir/uv/ips/STU1.1/package.tgz HL7, Inc 4.0.1 IG Tue, 22 Nov 2022 12:00:00 +1100 GMT hl7.fhir.us.davinci-deqm#3.1.0 http://hl7.org/fhir/us/davinci-deqm/STU3.1/package.tgz http://hl7.org/fhir/us/davinci-deqm/STU3.1/package.tgz HL7, Inc 4.0.1 IG Mon, 21 Nov 2022 12:00:00 +1100 GMT hl7.fhir.us.sdoh-clinicalcare#2.0.0 Social Determinants of Health (SDOH) are increasingly being recognized as essential factors that influence healthcare outcomes. This HL7 Implementation Guide (IG) defines how to exchange SDOH content defined by the [Gravity Project]( https://confluence.hl7.org/display/GRAV/The+Gravity+Project) using the HL7 FHIR standard. It defines how to represent coded content used to support the following care activities: screening, clinical assessment/diagnosis, goal setting, and the planning and performing of interventions. This IG addresses the need to gather SDOH information in multiple settings, share that information between stakeholders, and exchange referrals between organizations to address specific social risk needs, all with appropriate patient consent. In addition, the IG demonstrates how to share clinical data to support secondary purposes such as population health, quality, and research. The guide supports the following use cases: * Document SDOH data in conjunction with patient encounters with providers, payers, and community services * Document and track SDOH-related interventions to completion * Identify cohorts of individuals that have a common relationship to another entity (e.g., covered by the same payer) This implementation guide was developed by the Gravity Project, which specifically focuses on using HL7 FHIR to define standards for the exchange of SDOH-related information. Both the project and this implementation guide are focused on the U.S. environment. This implementation guide leverages content from the [US Core Implementation Guide](https://www.hl7.org/fhir/us/core/) and binds to US-specific terminology. However, the basic constructs and interaction patterns may well be applicable outside the U.S. Additional information regarding the background and use of this IG can be found on the [Gravity Confluence Technology Pages](https://confluence.hl7.org/display/GRAV/Technical+Workstream+Dashboard) ### Content and organization The implementation guide is organized into the following sections: * Background: Includes [Gravity Background](gravity_background.html), [SDOH Clinical Care Background](sdoh_clinical_care_background.html), [Functional Use Cases](functional_use_cases.html), and [Technical Background](technical_background.html), thesedescribe the environment in which this implementation guide establishes standards for information exchange * [Change History](stu2_ballot_changes.html) describes the changes included in the STU 2 ballot version of the IG and [Change History](stu2_publication_changes.html) describes the changes applied to the balloted version * Context: Describes the [Survey Instrument Support](survey_instrument_support.html),[ QuestionnaireResponse Mapping Instructions](mapping_instructions.html), [Support for Multiple Domains](support_for_multiple_domains.html), [Exchange Workflow](exchange_workflow.html) and [Synchronizing Applications with API Data Sources](synchronizing_applications_with_api_data_sources.html) that details a high-level overview of expected process flow * Specifications: Provides an overview of the [FHIR Artifacts](fhir_artifacts_overview.html) defined and used in this IG, [Checking Task Status](checking_task_status.html) to describe managing task status, [Privacy and Security](privacy_and_security.html) issues, [MustSupport and Missing Data](mustsupport_and_missing_data.html) concepts and [Draft Specifications for Personal Characteristics](draft_specifications_for_personal_characteristics.html) * [Downloads](downloads.html): Provides for the download of various IG related artifacts * [Credits](credits.html): Identifies the individuals and organizations involved in developing this implementation guide * [Artifacts Index](artifacts.html): Introduces and provides links to the FHIR R4 profiles, examples and other FHIR artifacts used in this implementation guide ### Note to Implementers Implementers should pay specific attention to the following sections: * [Technical Background](technical_background.html) if the implementer needs basic FHIR information references * [Survey Instrument Support](survey_instrument_support.html), and [ QuestionnaireResponse Mapping Instructions](mapping_instructions.html) if implementing support for structured assessment instruments * [Support for Multiple Domains](support_for_multiple_domains.html) to understand this IG's approach to domain specific value sets * [Exchange Workflow diagram](exchange_workflow.html) to understand the exchange workflows * [Synchronizing Applications with API Data Sources](synchronizing_applications_with_api_data_sources.html) that describes the suggested method for synchronizing patient/client or Community Based Organization applications with referral systems FHIR APIs * [FHIR Artifacts](fhir_artifacts_overview.html) to understand the individual FHIR artifacts described in this IG * [Privacy and Security](privacy_and_security.html) for implementers that are concerned with privacy and security aspects related to implementing the information exchanges defined in this IG * [MustSupport and Missing Data](mustsupport_and_missing_data.html) to understand the interpretation of the MustSupport flags and the treatment of Missing Data used in this IG * [Draft Specifications for Personal Characteristics](draft_specifications_for_personal_characteristics.html) for an introduction to draft observation profiles to exchange personal characteristics data, which includes the source and method of acquisition * [Artifacts Index](artifacts.html) provides easy access for all implementers the FHIR R4 profiles, examples and other FHIR artifacts defined in this implementation guide and linked from this section -- this section also includes details for the declared capability statements for espective servers and clients * [Downloads](downloads.html) links to allow implementers to download the IG and various artifacts ### Support for external terminologies for ServiceRequest and Procedure If implementers of this IG wish to use terminologies that are not part of the required value sets for specific elements that have a type of CodableConcept (such as ServiceRequest.code and Procedure.code) they may include a specific Coding that specifies a system (URL that is defined and supported by the terminology author) as well as the specific code (define in the terminology) as long as the meaning of the code is a concept that is logically the same as, or contained in the concept, of the required code. The following is an example for a ServiceRequest or Procedure where the external terminology URL is : http://terminologysystem and the code is : SummerProgram "code" : { "coding" : [ { "system" : "http://snomed.info/sct", "code" : "467681000124101", "display" : "Assistance with application for Summer Food Service Program" } ] }, { "coding" : [ { "system" : "http://terminologysystem", "code" : "SummerProgram", "display" : "Summer Food Service Program" } ] } ], ### Intellectual Property {% include ip-statements.xhtml %} ### Cross Version Analysis {% include cross-version-analysis.xhtml %} ### Dependencies {% include dependency-table.xhtml %} ### Globals {% include globals-table.xhtml %} (built Mon, Nov 21, 2022 18:33+0000+00:00) http://hl7.org/fhir/us/sdoh-clinicalcare/STU2/package.tgz http://hl7.org/fhir/us/sdoh-clinicalcare/STU2/package.tgz HL7, Inc 4.0.1 IG Mon, 21 Nov 2022 12:00:00 +1100 GMT hl7.fhir.us.mdi#1.0.0 This US-specific implementation guide (IG) provides guidance on the exchange of information to and from medicolegal death investigation (MDI) information systems. It supports interoperability between the MDI systems of medical examiner and coroner (ME/C) offices, forensic toxicology and other laboratory information management systems (LIMS), electronic death reporting systems (EDRS) of jurisdictional vital records offices, and ancillary workflows whose systems have the capability of utilizing Fast Healthcare Interoperability Resources (FHIR). The guide provides MDI system developers with the technical details and best practices to standardize MDI fields and interfaces. Stakeholders may use the narrative portions of this guide to inform policies and practices for data exchange between systems contributing to death investigations.This guide can serve as a base for local specifications. This MDI specification is designed to be flexible to accommodate a variety of systems, recognizing that information management systems used for assembling MDI data vary widely by state, jurisdiction, and agency. (built Fri, Sep 30, 2022 20:14+0000+00:00) http://hl7.org/fhir/us/mdi/STU1/package.tgz http://hl7.org/fhir/us/mdi/STU1/package.tgz HL7, Inc 4.0.1 IG Fri, 30 Sep 2022 12:00:00 +1000 GMT hl7.fhir.us.pacio-rt#1.0.0 PACIO Re-Assessment Timepoints Implementation Guide (built Wed, Sep 28, 2022 16:27+0000+00:00) http://hl7.org/fhir/us/pacio-rt/STU1/package.tgz http://hl7.org/fhir/us/pacio-rt/STU1/package.tgz HL7, Inc 4.0.1 IG Wed, 28 Sep 2022 12:00:00 +1000 GMT hl7.fhir.uv.fhir-for-fair#1.0.0 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 Wed, Sep 28, 2022 16:10+0000+00:00) http://hl7.org/fhir/uv/fhir-for-fair/STU1/package.tgz http://hl7.org/fhir/uv/fhir-for-fair/STU1/package.tgz HL7, Inc 4.3.0 IG Wed, 28 Sep 2022 12:00:00 +1000 GMT hl7.fhir.us.udap-security#1.0.0 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, Sep 27, 2022 18:31+0000+00:00) http://hl7.org/fhir/us/udap-security/STU1/package.tgz http://hl7.org/fhir/us/udap-security/STU1/package.tgz HL7, Inc 4.0.1 IG Tue, 27 Sep 2022 12:00:00 +1000 GMT hl7.fhir.us.exchange-routing#1.0.0 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) http://hl7.org/fhir/us/exchange-routing/STU1/package.tgz http://hl7.org/fhir/us/exchange-routing/STU1/package.tgz HL7, Inc 4.0.1 IG Mon, 26 Sep 2022 12:00:00 +1000 GMT hl7.fhir.us.vitals#1.0.0 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) http://hl7.org/fhir/us/vitals/STU1/package.tgz http://hl7.org/fhir/us/vitals/STU1/package.tgz HL7, Inc 4.0.1 IG Mon, 12 Sep 2022 12:00:00 +1000 GMT hl7.fhir.r5.core#5.0.0-ballot FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (built Sat, Sep 10, 2022 04:52+1000+10:00) http://hl7.org/fhir/2022Sep/hl7.fhir.r5.core.tgz http://hl7.org/fhir/2022Sep/hl7.fhir.r5.core.tgz HL7, Inc 5.0.0-ballot fhir.core Sat, 10 Sep 2022 12:00:00 +1000 GMT hl7.fhir.r5.expansions#5.0.0-ballot Expansions for the 5.0.0-ballot version of the FHIR standard (built Sat, Sep 10, 2022 04:52+1000+10:00) http://hl7.org/fhir/2022Sep/hl7.fhir.r5.expansions.tgz http://hl7.org/fhir/2022Sep/hl7.fhir.r5.expansions.tgz HL7, Inc 5.0.0-ballot fhir.core Sat, 10 Sep 2022 12:00:00 +1000 GMT hl7.fhir.r5.examples#5.0.0-ballot Examples for the 5.0.0-ballot version of the FHIR standard (built Sat, Sep 10, 2022 04:52+1000+10:00) http://hl7.org/fhir/2022Sep/hl7.fhir.r5.examples.tgz http://hl7.org/fhir/2022Sep/hl7.fhir.r5.examples.tgz HL7, Inc 5.0.0-ballot fhir.core Sat, 10 Sep 2022 12:00:00 +1000 GMT hl7.fhir.core#5.0.0-ballot FHIR Core - Group package for R5 Draft http://hl7.org/fhir/2022Sep/package.tgz http://hl7.org/fhir/2022Sep/package.tgz HL7, Inc 5.0.0-ballot fhir.core Sat, 10 Sep 2022 12:00:00 +1000 GMT hl7.fhir.us.ecr#2.1.0 # Introduction and Purpose With 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. With 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. For 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). For Clinical Safety Information please refer to the [FHIR Implementer’s Safety Checklist](http://hl7.org/fhir/safety.html). <div style="background-color: #ffffcc; border-left: 6px solid #ffeb3b;"> <p><b>Known Issue:</b></p> <p>The following issue is related to a publication tooling issue. A technical correction is planned once the tooling issue has been addressed.</p> <ul> <li><a href="https://jira.hl7.org/browse/FHIR-30477" rel="external" target="_blank">FHIR-30477</a>: Resolution errors for FHIRHelpers and FHIR-ModelInfo.</li> </ul> </div> # Stakeholders * Regulatory Agencies * Standards Development Organizations * Vendors: EHR, PHR; Health Care IT; Clinical Decision Support Systems, Public Health Surveillance Systems * Providers: Ambulatory and Healthcare Institutions (hospitals, long term care, mental health) * Local, State, Tribal and Federal Public Health Agencies (built Wed, Aug 31, 2022 17:39+0000+00:00) http://hl7.org/fhir/us/ecr/2.1.0/package.tgz http://hl7.org/fhir/us/ecr/2.1.0/package.tgz HL7, Inc 4.0.1 IG Wed, 31 Aug 2022 12:00:00 +1000 GMT hl7.fhir.us.vrdr#2.0.0 http://hl7.org/fhir/us/vrdr/STU2/package.tgz http://hl7.org/fhir/us/vrdr/STU2/package.tgz HL7, Inc 4.0.1 IG Wed, 31 Aug 2022 12:00:00 +1000 GMT hl7.fhir.us.davinci-drug-formulary#2.0.0 DaVinci Payer Data Exchange (PDex) US Drug Formulary, Release 2.0.0 - US Realm STU" (built Thu, Aug 25, 2022 13:09+0000+00:00) http://hl7.org/fhir/us/davinci-drug-formulary/STU2/package.tgz http://hl7.org/fhir/us/davinci-drug-formulary/STU2/package.tgz HL7, Inc 4.0.1 IG Thu, 25 Aug 2022 12:00:00 +1000 GMT hl7.fhir.us.odh#1.2.0 **HL7 FHIR Profile: Occupational Data for Health (ODH), Release 1.2 (Standard for Trial Use)** This 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. **Introduction and Guidance** This 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. This 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. While 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. **Background** The 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. The 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. **Scope** The 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: • Employment Status • Retirement Date • Combat Zone Period • Past or Present Job for the patient or a household member, which includes: o Past or Present Job Occupation o Past or Present Job Industry o Work Classification o Work Schedule, which includes: - Weekly Work Days - Daily Work Hours o Job Duty o Occupational Hazard o Employer name o Employer address o Related Subject (when it is Past or Present Job of a household member of the person) o Start/End Dates • Usual Work of the patient or a household member, which includes: o Usual Occupation o Usual Industry o Usual Occupation Duration o Related Subject (when it is Usual Work of a household member of the person) o Start Date **Known Issues and Limitations** This 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. While multiple retirement dates are supported, the retirement date is not linked to any specific job, or usual occupation. **Credits** Co-Editor: Lori Reed-Fourquet e-HealthSign, LLC lfourquet@ehealthsign.com Co-Editor: Rob Hausam Hausam Consulting rob@hausamconsulting.com Co-Editor: Mark Kramer MITRE Corporation mkramer@mitre.org This 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). The 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. **Authors** Name Email/URL HL7 International - Public Health http://www.hl7.org/Special/committees/pher (built Wed, Aug 17, 2022 16:01+0000+00:00) http://hl7.org/fhir/us/odh/STU1.2/package.tgz http://hl7.org/fhir/us/odh/STU1.2/package.tgz HL7, Inc 4.0.1 IG Wed, 17 Aug 2022 12:00:00 +1000 GMT hl7.fhir.uv.ihe-sdc-ecc#1.0.0-ballot 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 Thu, Aug 11, 2022 13:48+0000+00:00) http://hl7.org/fhir/uv/ihe-sdc-ecc/2022Sep/package.tgz http://hl7.org/fhir/uv/ihe-sdc-ecc/2022Sep/package.tgz HL7, Inc 4.0.1 IG Thu, 11 Aug 2022 12:00:00 +1000 GMT hl7.fhir.us.directory-attestation#1.0.0-ballot National Directory (built Tue, Aug 9, 2022 12:51+0000+00:00) http://hl7.org/fhir/us/directory-attestation/2022Sep/package.tgz http://hl7.org/fhir/us/directory-attestation/2022Sep/package.tgz HL7, Inc 4.0.1 IG Tue, 09 Aug 2022 12:00:00 +1000 GMT hl7.fhir.us.directory-exchange#1.0.0-ballot National Directory (built Tue, Aug 9, 2022 16:36+0000+00:00) http://hl7.org/fhir/us/directory-exchange/2022Sep/package.tgz http://hl7.org/fhir/us/directory-exchange/2022Sep/package.tgz HL7, Inc 4.0.1 IG Tue, 09 Aug 2022 12:00:00 +1000 GMT hl7.fhir.us.directory-query#1.0.0-ballot National Directory Query (built Tue, Aug 9, 2022 18:48+0000+00:00) http://hl7.org/fhir/us/directory-query/2022Sep/package.tgz http://hl7.org/fhir/us/directory-query/2022Sep/package.tgz HL7, Inc 4.0.1 IG Tue, 09 Aug 2022 12:00:00 +1000 GMT hl7.fhir.us.home-lab-report#1.0.0-ballot |IG Characteristic | Value | |------------------------------------------------------|--------------------------------------------| |**FHIR Version:** | FHIR R4 | |**IG Realm:** | US | |**IG Type:** | STU Ballot | |**Exchange Methods:** | RESTfulAPI, Messages, Transactions, Tasks | |**IG Note:** | This HL7 FHIR Guide utilizes and adopts guidance or profiles developed in the US Core FHIR&reg; Implementation Guide. This FHIR IG has narrative pages describing the HL7 V2 Message for At-Home In-Vitro Test Reporting and provides some example messages. Presently public health departments usually only can handle and store HL7 V2| {:.table-striped} |IG Dependencies | |----------------------------------| | [HL7 FHIR US Core Version 5.0.1](http://hl7.org/fhir/us/core/STU5.0.1/) | {:.table-striped} ### Background Point-of-care (POC) and At-Home In-Vitro Tests offer increased accessibility to needed diagnostic solutions during a pandemic. Test results provide value to both the individual taking the tests and also to public health authorities responsible for coordinating a regional and national response. Digital platforms are being developed that allow individual test results, with permission of the individual, to be captured, organized, and transmitted to public health systems. Test manufacturers, working in partnership with these digital platforms, are seeking guidance on how to send test results. With multiple tests already entering the market, there is a need for a unified strategy on data flow of test results from the apps to downstream systems. A national data exchange standard should be supported that guides data exchange from test results residing on individual users’ digital test applications to public health authorities, at both the federal and regional levels. ### Introduction This implementation guide constrains the [US Core Diagnostic Report for Laboratory Results](http://hl7.org/fhir/us/core/StructureDefinition/us-core-diagnosticreport-lab) and the [US Core Laboratory Observation Profile](http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab) for use for transmitting At-Home In-Vitro Test results to local, state, territorial and federal health agencies. It is an STU IG to be used in real world testing. It was developed in a collaborative project with the NIH/NIBIB, ONC, a vendor manufacturer of diagnostic healthcare products that makes one of the FDA approved At-Home In-Vitro Test kits and an App developer - who is a leading provider of secure interoperability solutions. The intention of this guide is to assist developers in producing and sending standardized FHIR test result data perfomed at home. FHIRs eases app development and US Core is in a rapid adoption curve. This guide points to already existing US Core Guidance and other guidance with respect to FHIR Parameters, FHIR operations and RESTful and SMART on FHIR information. It is also understood that, in general, public health agencies are at present primarily prepared to only receive V2 messages. The App developer is poised to transform this to V2 messages. In addition, as a parallel effort, a V2 <-> FHIR data mapping table has been developed [In-Vitro At-Home Test V2 FHIR Mapping.xlsx](https://docs.google.com/spreadsheets/d/1Vx7WesZzihNiAsHCVPQtSiEJLBQZr8Iy/edit?usp=sharing&ouid=112434457756659409284&rtpof=true&sd=true). **Please note** : This guide is a framework for future work. It contains "framework" profiles that contain constraints common to all At-Home In-Vitro Test Reporting use cases. These framework profiles can be further constrained to a particular use case such as the COVID-19 At-Home In-Vitro Test Reporting use case. The COVID-19 use case profiles have been created and included in this guide. ### Further Information [RADx® MARS - Mobile Application Reporting through Standards](https://www.nibib.nih.gov/covid-19/radx-tech-program/mars) [LOINC In Vitro Diagnostic (LIVD) Test Code Mapping for SARS-CoV-2 Tests](https://www.cdc.gov/csels/dls/sars-cov-2-livd-codes.html) [Test-Specific HL7v2 Field Values Tool](https://app.powerbigov.us/view?r=eyJrIjoiNjQyZjBkOGEtNjE0ZS00NjUyLTg3NjEtZTIxN2JmODE0ZGE1IiwidCI6IjE0Yjc3NTc4LTk3NzMtNDJkNS04NTA3LTI1MWNhMmRjMmIwNiJ9&pageName=ReportSectionhttps://app.powerbigov.us/view?r=eyJrIjoiNjQyZjBkOGEtNjE0ZS00NjUyLTg3NjEtZTIxN2JmODE0ZGE1IiwidCI6IjE0Yjc3NTc4LTk3NzMtNDJkNS04NTA3LTI1MWNhMmRjMmIwNiJ9&pageName=ReportSection3147535a75468ee60d16) (built Mon, Aug 8, 2022 23:58+0000+00:00) http://hl7.org/fhir/us/home-lab-report/2022Sep/package.tgz http://hl7.org/fhir/us/home-lab-report/2022Sep/package.tgz HL7, Inc 4.0.1 IG Tue, 09 Aug 2022 12:00:00 +1000 GMT hl7.fhir.us.codex-radiation-therapy#1.0.0-ballot CodeX™ Radiation Therapy is an initiative intended to assemble a core set of structured data elements for radiation therapy electronic health records. (built Mon, Aug 8, 2022 14:41+0000+00:00) http://hl7.org/fhir/us/codex-radiation-therapy/2022Sep/package.tgz http://hl7.org/fhir/us/codex-radiation-therapy/2022Sep/package.tgz HL7, Inc 4.0.1 IG Mon, 08 Aug 2022 12:00:00 +1000 GMT hl7.fhir.us.davinci-cdex#2.0.0-ballot 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 Mon, Aug 8, 2022 20:11+0000+00:00) http://hl7.org/fhir/us/davinci-cdex/2022Sep/package.tgz http://hl7.org/fhir/us/davinci-cdex/2022Sep/package.tgz HL7, Inc 4.0.1 IG Mon, 08 Aug 2022 12:00:00 +1000 GMT hl7.fhir.us.davinci-cdex#1.1.0 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 Mon, Aug 8, 2022 15:11+0000+00:00) http://hl7.org/fhir/us/davinci-cdex/STU1.1/package.tgz http://hl7.org/fhir/us/davinci-cdex/STU1.1/package.tgz HL7, Inc 4.0.1 IG Mon, 08 Aug 2022 12:00:00 +1000 GMT hl7.fhir.us.qicore#5.0.0-ballot 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 Mon, Aug 8, 2022 16:47+0000+00:00) http://hl7.org/fhir/us/qicore/2022Sep/package.tgz http://hl7.org/fhir/us/qicore/2022Sep/package.tgz HL7, Inc 4.0.1 IG Mon, 08 Aug 2022 12:00:00 +1000 GMT hl7.fhir.us.pacio-pfe#1.0.0-ballot 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 Fri, Aug 5, 2022 17:36+0000+00:00) http://hl7.org/fhir/us/pacio-pfe/2022Sep/package.tgz http://hl7.org/fhir/us/pacio-pfe/2022Sep/package.tgz HL7, Inc 4.0.1 IG Fri, 05 Aug 2022 12:00:00 +1000 GMT hl7.fhir.us.ph-library#1.0.0-ballot The US Public Health Profiles Library is a collection of reusable architecture and content profiles representing common public health concepts and patterns. It is intended as a complement to US Core that is used to ease implementation burden of healthcare organizations, electronic health record companies, public health agencies, and others involved in the US public health endeavor. The US Public Health Profiles Library will be instituted in close conjunction with US Core and have an analogous process for implementation, moderation, review, and approval. The intent is to re-use US Core profiles wherever possible and only add profiles that are needed for common public health needs. The library will evolve over time and may be supported by an adjunct profiles registry that includes developing and informational profiles for public health use. After evaluation and harmonization analysis of two large multi-condition and multi-use case public health projects – eCR and MedMorph, it was determined that there are many common elements between the two IGs. The short-term scope of this library includes elements common to the above-mentioned FHIR IGs and will define a US Realm specific framework that defines common elements for the implementation guides. The longer-term scope of this will include analysis and inclusion of data elements from Vital Records Death Reporting, Vital Records Birth and Fetal Death Reporting, and other Public Health use cases. To avoid defining the same profiles multiple times, we have created a US Public Health Profiles Library for use by Public Health and other FHIR standards development efforts to define appropriate FHIR profiles, value sets, etc., once and allow them to be referenced by each of the specific implementation guides. This USPHPL will provide a starting point and framework for inclusion in multiple use case specific implementation guides focused on the exchange of Public Health information to support interoperability among public health systems and reduce provider and implementer burden. (built Fri, Aug 5, 2022 18:56+0000+00:00) http://hl7.org/fhir/us/ph-library/2022Sep/package.tgz http://hl7.org/fhir/us/ph-library/2022Sep/package.tgz HL7, Inc 4.0.1 IG Fri, 05 Aug 2022 12:00:00 +1000 GMT hl7.fhir.us.specialty-rx#2.0.0-ballot 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 Fri, Aug 5, 2022 22:26+0000+00:00) http://hl7.org/fhir/us/specialty-rx/2022Sep/package.tgz http://hl7.org/fhir/us/specialty-rx/2022Sep/package.tgz HL7, Inc 4.0.1 IG Fri, 05 Aug 2022 12:00:00 +1000 GMT hl7.fhir.us.covid19library#1.0.0 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) http://hl7.org/fhir/us/covid19library/informative1/package.tgz http://hl7.org/fhir/us/covid19library/informative1/package.tgz HL7, Inc 4.0.1 IG Mon, 25 Jul 2022 12:00:00 +1000 GMT hl7.fhir.uv.subscriptions-backport#1.0.0 The Subscription R5 Backport Implementation Guide enables servers running verions of FHIR earlier than R5 to implement a subset of R5 Subscriptions in a standardized way. (built Mon, Jul 18, 2022 19:59+0000+00:00) http://hl7.org/fhir/uv/subscriptions-backport/STU1/package.tgz http://hl7.org/fhir/uv/subscriptions-backport/STU1/package.tgz HL7, Inc 4.3.0 IG Mon, 18 Jul 2022 12:00:00 +1000 GMT hl7.fhir.us.insurance-card#1.0.0 CARIN Digital Insurance Card (built Wed, Jul 13, 2022 17:21+0000+00:00) http://hl7.org/fhir/us/insurance-card/STU1/package.tgz http://hl7.org/fhir/us/insurance-card/STU1/package.tgz HL7, Inc 4.0.1 IG Wed, 13 Jul 2022 12:00:00 +1000 GMT hl7.fhir.us.core#5.0.1 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. These 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 Wed, Jun 22, 2022 19:44+0000+00:00) http://hl7.org/fhir/us/core/STU5.0.1/package.tgz http://hl7.org/fhir/us/core/STU5.0.1/package.tgz HL7, Inc 4.0.1 IG Wed, 22 Jun 2022 12:00:00 +1000 GMT hl7.fhir.us.davinci-ra#1.0.0 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 Thu, Jun 16, 2022 14:23+0000+00:00) http://hl7.org/fhir/us/davinci-ra/STU1/package.tgz http://hl7.org/fhir/us/davinci-ra/STU1/package.tgz HL7, Inc 4.0.1 IG Thu, 16 Jun 2022 12:00:00 +1000 GMT hl7.fhir.r4b.core#4.3.0 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) http://hl7.org/fhir/R4B/hl7.fhir.r4b.core.tgz http://hl7.org/fhir/R4B/hl7.fhir.r4b.core.tgz HL7, Inc 4.3.0 fhir.core Sat, 28 May 2022 12:00:00 +1000 GMT hl7.fhir.r4b.examples#4.3.0 Example resources in the R4B version of the FHIR standard http://hl7.org/fhir/R4B/hl7.fhir.r4b.examples.tgz http://hl7.org/fhir/R4B/hl7.fhir.r4b.examples.tgz HL7, Inc 4.3.0 fhir.core Sat, 28 May 2022 12:00:00 +1000 GMT hl7.fhir.r4b.expansions#4.3.0 Expansions for the 4.3.0 version of the FHIR standard (built Sat, May 28, 2022 12:47+1000+10:00) http://hl7.org/fhir/R4B/hl7.fhir.r4b.expansions.tgz http://hl7.org/fhir/R4B/hl7.fhir.r4b.expansions.tgz HL7, Inc 4.3.0 fhir.core Sat, 28 May 2022 12:00:00 +1000 GMT hl7.fhir.r4b.elements#4.3.0 Element Definitions for types defined in the R4B version of the FHIR standard http://hl7.org/fhir/R4B/hl7.fhir.r4b.elements.tgz http://hl7.org/fhir/R4B/hl7.fhir.r4b.elements.tgz HL7, Inc 4.3.0 fhir.core Sat, 28 May 2022 12:00:00 +1000 GMT hl7.fhir.r4b.corexml#4.3.0 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) http://hl7.org/fhir/R4B/hl7.fhir.r4b.corexml.tgz http://hl7.org/fhir/R4B/hl7.fhir.r4b.corexml.tgz HL7, Inc 4.3.0 fhir.core Sat, 28 May 2022 12:00:00 +1000 GMT hl7.fhir.core#4.3.0 Group Wrapper that includes all the R4B packages http://hl7.org/fhir/R4B/package.tgz http://hl7.org/fhir/R4B/package.tgz HL7, Inc 4.3.0 fhir.core Sat, 28 May 2022 12:00:00 +1000 GMT hl7.fhir.us.core#5.0.0 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. These 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 Fri, May 13, 2022 19:50+0000+00:00) http://hl7.org/fhir/us/core/STU5/package.tgz http://hl7.org/fhir/us/core/STU5/package.tgz HL7, Inc 4.0.1 IG Fri, 13 May 2022 12:00:00 +1000 GMT hl7.fhir.uv.phd#1.0.0 ImplementationGuide for Personal Health Devices (PHD), used in remote patient monitoring (e.g., weight scales, blood pressure cuffs, glucose monitors, pulse-oximeters, etc.). (built Thu, May 12, 2022 20:20+0000+00:00) http://hl7.org/fhir/uv/phd/STU1/package.tgz http://hl7.org/fhir/uv/phd/STU1/package.tgz HL7, Inc 4.0.1 IG Thu, 12 May 2022 12:00:00 +1000 GMT hl7.fhir.uv.genomics-reporting#2.0.0 Guidelines for reporting of clinical genomics results using HL7 FHIR. (built Mon, May 9, 2022 16:52+0000+00:00) http://hl7.org/fhir/uv/genomics-reporting/STU2/package.tgz http://hl7.org/fhir/uv/genomics-reporting/STU2/package.tgz HL7, Inc 4.0.1 IG Mon, 09 May 2022 12:00:00 +1000 GMT hl7.fhir.uv.smart-web-messaging#1.0.0 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) http://hl7.org/fhir/uv/smart-web-messaging/STU1/package.tgz http://hl7.org/fhir/uv/smart-web-messaging/STU1/package.tgz HL7, Inc 4.0.1 IG Fri, 06 May 2022 12:00:00 +1000 GMT hl7.fhir.us.cqfmeasures#3.0.0 The Fast Healthcare Interoperability Resource (FHIR) Quality Measure Implementation Guide (this IG) describes an approach to representing electronic Clinical Quality Measures (eCQMs) 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, Apr 28, 2022 14:46+0000+00:00) http://hl7.org/fhir/us/cqfmeasures/STU3/package.tgz http://hl7.org/fhir/us/cqfmeasures/STU3/package.tgz HL7, Inc 4.0.1 IG Thu, 28 Apr 2022 12:00:00 +1000 GMT hl7.fhir.us.davinci-pdex-plan-net#1.1.0 Davinci PDEX Plan Net (built Mon, Apr 4, 2022 14:01+0000+00:00) http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/package.tgz http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.1/package.tgz HL7, Inc 4.0.1 IG Mon, 04 Apr 2022 12:00:00 +1000 GMT hl7.fhir.uv.fhircast#2.1.0-ballot FHIRcast synchronizes healthcare applications in real time to show the same clinical content to a common user. (built Fri, Apr 1, 2022 01:46+0000+00:00) http://hl7.org/fhir/uv/fhircast/2022May/package.tgz http://hl7.org/fhir/uv/fhircast/2022May/package.tgz HL7, Inc 4.0.1 IG Fri, 01 Apr 2022 12:00:00 +1100 GMT hl7.fhir.us.identity-matching#1.0.0-ballot http://hl7.org/fhir/us/identity-matching/2022May/package.tgz http://hl7.org/fhir/us/identity-matching/2022May/package.tgz HL7, Inc 4.0.1 IG Thu, 31 Mar 2022 12:00:00 +1100 GMT hl7.fhir.us.qicore#4.1.1 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 Thu, Mar 31, 2022 16:41+0000+00:00) http://hl7.org/fhir/us/qicore/STU4.1.1/package.tgz http://hl7.org/fhir/us/qicore/STU4.1.1/package.tgz HL7, Inc 4.0.1 IG Thu, 31 Mar 2022 12:00:00 +1100 GMT hl7.fhir.us.mihr#1.0.0-ballot ### Scope The 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. This 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. ### Background The 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). The 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. Future 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. ### Maternal Research Use Cases This 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. Initial use cases of this IG focus on pregnancy and subsequent death within a specific timeframe and hypertensive disorders of pregnancy pre, ante, and postpartum. 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 research use case populations: * 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. * Hypertensive Disorders of pregnancy: This use case focuses on women with a diagnosis of hypertensive disorders of pregnancy. In 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. In the future, the IG will expand this framework to a range of use cases including: * Risks for children related to maternal exposure to medications taken during pregnancy * Potential adverse maternal obstetric history impacts on child outcomes * Access to relevant sensitive health information * Retrospective population-based analysis of inherited disorders This guide fundamentally relies on creating structural relationships between: * Maternal and child records to effectively diagnose and treat otherwise fatal child outcomes * Maternal and birth records and/or maternal and child death records * Maternal and child records in multiple disparate systems ### Audience The 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. ### Authors & Project Team This table lists the authors, subject matter experts, and the affiliations which contributed to this standard. <style type="text/css"> .tg {border-collapse:collapse;border-spacing:0;} .tg td{border-color:black;border-style:solid;border-width:1px;font-family:Arial, sans-serif;font-size:14px; overflow:hidden;padding:10px 5px;word-break:normal;} .tg th{border-color:black;border-style:solid;border-width:1px;font-family:Arial, sans-serif;font-size:14px; font-weight:normal;overflow:hidden;padding:10px 5px;word-break:normal;} .tg .tg-4erg{border-color:inherit;font-style:italic;font-weight:bold;text-align:left;vertical-align:top} .tg .tg-0r4h{border-color:inherit;font-family:serif !important;font-weight:bold;text-align:left;vertical-align:top} .tg .tg-fymr{border-color:inherit;font-weight:bold;text-align:left;vertical-align:top} .tg .tg-0pky{border-color:inherit;text-align:left;vertical-align:top} </style> <table class="tg"> <thead> <tr> <th class="tg-fymr">Name &amp; Affiliation</th> <th class="tg-0r4h">Role</th> <th class="tg-fymr">Contact</th> </tr> </thead> <tbody> <tr> <td class="tg-4erg">Lantana Consulting Group</td> <td class="tg-0pky"> </td> <td class="tg-0pky"> </td> </tr> <tr> <td class="tg-0pky">Courtney Panaia-Rodi </td> <td class="tg-0pky">Project Executive</td> <td class="tg-0pky">courtney.panaia-rodi@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Wendy Wise</td> <td class="tg-0pky">Project Manager</td> <td class="tg-0pky">wendy.wise@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Lani Johnson</td> <td class="tg-0pky">Associate Project Manager</td> <td class="tg-0pky">lani.johnson@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Rick Geimer</td> <td class="tg-0pky">FHIR Subject Matter Expert</td> <td class="tg-0pky">rick.geimer@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Zabrina Gonzaga</td> <td class="tg-0pky">Terminology Subject Matter Expert</td> <td class="tg-0pky">zabrina.gonzaga@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Sarah Gaunt</td> <td class="tg-0pky">Senior FHIR/CDA Analyst</td> <td class="tg-0pky">sarah.gaunt@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Dave deRoode</td> <td class="tg-0pky">FHIR/CDA Analyst</td> <td class="tg-0pky">david.deroode@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Ming Dunajick</td> <td class="tg-0pky">FHIR/CDA Analyst</td> <td class="tg-0pky">ming.dunajick@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Ruby Nash</td> <td class="tg-0pky">FHIR Analyst</td> <td class="tg-0pky">ruby.nash@lantanagroup.com</td> </tr> <tr> <td class="tg-4erg">Office of the Assistant Secretary for Planning and Evaluation (ASPE)</td> <td class="tg-0pky"> </td> <td class="tg-0pky"> </td> </tr> <tr> <td class="tg-0pky">Violanda Grigorescu, MD, MSPH</td> <td class="tg-0pky">Senior Health Scientist <br>Division of Healthcare Quality and Outcomes, Office of Health Policy</td> <td class="tg-0pky">violanda.grigorescu@hhs.gov</td> </tr> <tr> <td class="tg-4erg">Centers for Disease Control and Prevention (CDC)</td> <td class="tg-0pky"> </td> <td class="tg-0pky"> </td> </tr> <tr> <td class="tg-0pky">Margaret Lampe, RN, MPH</td> <td class="tg-0pky">Nurse Epidemiologist &amp; Project Officer <br>Perinatal HIV Prevention Program</td> <td class="tg-0pky">mol0@cdc.gov</td> </tr> <tr> <td class="tg-0pky">Lisa Romero, DrPH</td> <td class="tg-0pky">Health Scientist <br>Division of Adolescent School Health</td> <td class="tg-0pky">eon1@cdc.gov</td> </tr> <tr> <td class="tg-4erg">National Institutes of Health (NIH) <br>Eunice Kennedy Shriver National Institute of Child Health and Human Development (NICHD) <br>National Information Center on Health Services Research and Health Care Technology (NICHSR)</td> <td class="tg-0pky"> </td> <td class="tg-0pky"> </td> </tr> <tr> <td class="tg-0pky">Alison Cernich</td> <td class="tg-0pky">NICHD Deputy Director</td> <td class="tg-0pky">alison.cernich@nih.hhs.gov</td> </tr> <tr> <td class="tg-0pky">John (Jack) Moye, Jr., MD</td> <td class="tg-0pky">Acting Director - National Children's Study <br>NICHD Medical Officer - Maternal &amp; Pediatric Infectious Disease Branch</td> <td class="tg-0pky">moyej@exchange.nih.gov</td> </tr> <tr> <td class="tg-0pky">Nahida Chakhtoura, MD, MsGH</td> <td class="tg-0pky">NICHD Medical Officer <br>Maternal and Pediatric Infectious Disease Branch</td> <td class="tg-0pky">nahida.chakhtoura@nih.gov</td> </tr> <tr> <td class="tg-0pky">Juanita Chinn, PhD</td> <td class="tg-0pky">NICHD Program Director <br>Population Dynamics Branch</td> <td class="tg-0pky">juanita.chinn@nih.gov</td> </tr> <tr> <td class="tg-0pky">Valerie Cotton</td> <td class="tg-0pky">NICHD Deputy Director <br>Office of Data Science and Sharing</td> <td class="tg-0pky">valerie.cotton@nih.gov</td> </tr> <tr> <td class="tg-0pky">Liz Amos, MLIS</td> <td class="tg-0pky">Special Assistant to the Chief Health Data Standards Officer <br>National Library of Medicine</td> <td class="tg-0pky">liz.amos@nih.gov</td> </tr> <tr> <td class="tg-4erg">Office of the National Coordinator for Health IT (ONC)</td> <td class="tg-0pky"> </td> <td class="tg-0pky"> </td> </tr> <tr> <td class="tg-0pky">Carmen Smiley</td> <td class="tg-0pky">IT Specialist (Systems Analysis)</td> <td class="tg-0pky">carmen.smiley@hhs.gov</td> </tr> <tr> <td class="tg-0pky">Rachel Abbey</td> <td class="tg-0pky">Public Health Analyst &amp; Program Officer</td> <td class="tg-0pky">rachel.abbey@hhs.gov</td> </tr> <tr> <td class="tg-0pky">Stephanie Garcia</td> <td class="tg-0pky">Senior Program Analyst</td> <td class="tg-0pky">stephanie.garcia@hhs.gov</td> </tr> <tr> <td class="tg-0pky">Brittney Boakye, MPH</td> <td class="tg-0pky">Program Assistant <br>Scientific Advancement Branch</td> <td class="tg-0pky">brittney.boakye@hhs.gov<br></td> </tr> <tr> <td class="tg-0pky">Alan Taylor</td> <td class="tg-0pky">Medical Informatics Officer, Standards and Terminology</td> <td class="tg-0pky">albert.taylor@hhs.gov</td> </tr> </tbody> </table> ### Acknowledgements This 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. The 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. Health Level Seven, HL7, CDA, CCD, FHIR and the [FLAME DESIGN] are registered trademarks of Health Level Seven International, registered in the US Trademark Office. This value set 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. This 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 Tue, Mar 29, 2022 18:46+0000+00:00) http://hl7.org/fhir/us/mihr/2022May/package.tgz http://hl7.org/fhir/us/mihr/2022May/package.tgz HL7, Inc 4.0.1 IG Tue, 29 Mar 2022 12:00:00 +1100 GMT hl7.fhir.uv.patient-corrections#1.0.0-ballot 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 Tue, Mar 29, 2022 16:29+0000+00:00) http://hl7.org/fhir/uv/patient-corrections/2022May/package.tgz http://hl7.org/fhir/uv/patient-corrections/2022May/package.tgz HL7, Inc 4.0.1 IG Tue, 29 Mar 2022 12:00:00 +1100 GMT hl7.fhir.us.davinci-cdex#1.0.0 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 Mon, Mar 28, 2022 13:46+0000+00:00) http://hl7.org/fhir/us/davinci-cdex/STU1/package.tgz http://hl7.org/fhir/us/davinci-cdex/STU1/package.tgz HL7, Inc 4.0.1 IG Mon, 28 Mar 2022 12:00:00 +1100 GMT hl7.fhir.us.mdi#1.0.0-ballot This US-specific implementation guide (IG) provides guidance on the exchange of information to and from medicolegal death investigation (MDI) information systems. It supports interoperability between the MDI systems of medical examiner and coroner (ME/C) offices, forensic toxicology and other laboratory information management systems (LIMS), electronic death reporting systems (EDRS) of jurisdictional vital records offices, and ancillary workflows whose systems have the capability of utilizing Fast Healthcare Interoperability Resources (FHIR). The guide provides MDI systems developers with the technical details and best practices to standardized MDI fields and interfaces. Stakeholders may use the narrative portions of this guide to inform policies and practices for data exchange between systems contributing to death investigations.This guide can serve as a base for local specifications. This MDI FHIR IG is designed to be light-weight and flexible, recognizing that information management systems used for assembling medicolegal death investigation data vary widely by state, jurisdiction, and agency. (built Mon, Mar 28, 2022 18:44+0000+00:00) http://hl7.org/fhir/us/mdi/2022May/package.tgz http://hl7.org/fhir/us/mdi/2022May/package.tgz HL7, Inc 4.0.1 IG Mon, 28 Mar 2022 12:00:00 +1100 GMT hl7.fhir.us.davinci-hrex#1.0.0 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. Da 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. The 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. HRex 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 Wed, Mar 23, 2022 18:55+0000+00:00) http://hl7.org/fhir/us/davinci-hrex/STU1/package.tgz http://hl7.org/fhir/us/davinci-hrex/STU1/package.tgz HL7, Inc 4.0.1 IG Wed, 23 Mar 2022 12:00:00 +1100 GMT hl7.fhir.uv.sdc#3.0.0 The SDC specification provides an infrastructure to standardize the capture and expanded use of patient-level data collected within an EHR.<br/>This includes two components:<br/>* Support more sophisticated questionnaire/form use-cases such as those needed for research, oncology, pathology and other clinical domains.<br/>*Support pre-population and auto-population of EHR data into forms/questionnaires for uses outside direct clinical care (patient safety, adverse event reporting, public health reporting, etc.). (built Tue, Mar 8, 2022 18:36+0000+00:00) http://hl7.org/fhir/uv/sdc/STU3/hl7.fhir.uv.sdc.tgz http://hl7.org/fhir/uv/sdc/STU3/hl7.fhir.uv.sdc.tgz HL7, Inc 4.0.1 IG Tue, 08 Mar 2022 12:00:00 +1100 GMT hl7.fhir.uv.sdc.r4#3.0.0 The SDC specification provides an infrastructure to standardize the capture and expanded use of patient-level data collected within an EHR.<br/>This includes two components:<br/>* Support more sophisticated questionnaire/form use-cases such as those needed for research, oncology, pathology and other clinical domains.<br/>*Support pre-population and auto-population of EHR data into forms/questionnaires for uses outside direct clinical care (patient safety, adverse event reporting, public health reporting, etc.). (built Tue, Mar 8, 2022 18:36+0000+00:00) http://hl7.org/fhir/uv/sdc/STU3/hl7.fhir.uv.sdc.r4.tgz http://hl7.org/fhir/uv/sdc/STU3/hl7.fhir.uv.sdc.r4.tgz HL7, Inc 4.0.1 IG Tue, 08 Mar 2022 12:00:00 +1100 GMT hl7.fhir.uv.sdc.r4b#3.0.0 The SDC specification provides an infrastructure to standardize the capture and expanded use of patient-level data collected within an EHR.<br/>This includes two components:<br/>* Support more sophisticated questionnaire/form use-cases such as those needed for research, oncology, pathology and other clinical domains.<br/>*Support pre-population and auto-population of EHR data into forms/questionnaires for uses outside direct clinical care (patient safety, adverse event reporting, public health reporting, etc.). (built Tue, Mar 8, 2022 18:36+0000+00:00) http://hl7.org/fhir/uv/sdc/STU3/hl7.fhir.uv.sdc.r4b.tgz http://hl7.org/fhir/uv/sdc/STU3/hl7.fhir.uv.sdc.r4b.tgz HL7, Inc 4.0.1 IG Tue, 08 Mar 2022 12:00:00 +1100 GMT hl7.fhir.uv.sdc#3.0.0 The SDC specification provides an infrastructure to standardize the capture and expanded use of patient-level data collected within an EHR.<br/>This includes two components:<br/>* Support more sophisticated questionnaire/form use-cases such as those needed for research, oncology, pathology and other clinical domains.<br/>*Support pre-population and auto-population of EHR data into forms/questionnaires for uses outside direct clinical care (patient safety, adverse event reporting, public health reporting, etc.). (built Tue, Mar 8, 2022 18:32+0000+00:00) http://hl7.org/fhir/uv/sdc/STU3/package.tgz http://hl7.org/fhir/uv/sdc/STU3/package.tgz HL7, Inc 4.0.1 IG Tue, 08 Mar 2022 12:00:00 +1100 GMT hl7.fhir.us.davinci-dtr#1.1.0-ballot 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, Feb 18, 2022 15:42+0000+00:00) http://hl7.org/fhir/us/davinci-dtr/2022May/package.tgz http://hl7.org/fhir/us/davinci-dtr/2022May/package.tgz HL7, Inc 4.0.1 IG Fri, 18 Feb 2022 12:00:00 +1100 GMT hl7.fhir.us.davinci-pdex#2.0.0-ballot This specification is currently undergoing ballot and connectathon testing. It is expected to evolve, possibly significantly, as part of that process. Feedback 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. This 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. [Financial Management](https://confluence.hl7.org/display/FM/Financial+Management+Home) is the Sponsoring Work Group for this Implementation Guide. **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 Profiles based on FHIR R4) which can be understood by providers and, if they choose to, committed to their Electronic Medical Records (EMR) System.** The 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. This IG uses the same Member Health History "payload" for member-authorized exchange of information with other Health Plans 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. This IG covers the exchange of: - Claims-based information - Clinical Information (such as Lab Results, Allergies and Conditions) This 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. This IG covers the exchange of a Member's Health History in the following scenarios: - Provider requested Provider-Health Plan Exchange using CDS-Hooks and SMART-on-FHIR - Member-authorized Health Plan to Health Plan exchange - Member-authorized Health Plan to Third-Party Application exchange The latter two scenarios are provided to meet the requirements identified in the CMS Interoperability Notice for Proposed Rule Making issued on February 11, 2019. **There are items in this guide that are subject to update**. This includes: - Value Sets - Vocabularies (X12, NUBC etc.) - Examples **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). See the [Table of Contents](toc.html) for more information. (built Fri, Feb 18, 2022 14:02+0000+00:00) http://hl7.org/fhir/us/davinci-pdex/2022May/package.tgz http://hl7.org/fhir/us/davinci-pdex/2022May/package.tgz HL7, Inc 4.0.1 IG Fri, 18 Feb 2022 12:00:00 +1100 GMT hl7.fhir.us.davinci-crd#1.1.0-ballot Guidelines for conveying coverage requirements to clinicians when planning treatment (built Thu, Feb 17, 2022 08:04+0000+00:00) http://hl7.org/fhir/us/davinci-crd/2022May/package.tgz http://hl7.org/fhir/us/davinci-crd/2022May/package.tgz HL7, Inc 4.0.1 IG Thu, 17 Feb 2022 12:00:00 +1100 GMT hl7.fhir.us.davinci-pas#1.2.0-ballot Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Thu, Feb 17, 2022 07:50+0000+00:00) http://hl7.org/fhir/us/davinci-pas/2022May/package.tgz http://hl7.org/fhir/us/davinci-pas/2022May/package.tgz HL7, Inc 4.0.1 IG Thu, 17 Feb 2022 12:00:00 +1100 GMT hl7.fhir.uv.shorthand#2.0.0 Describes FHIR Shorthand (FSH), a domain-specific language (DSL) for defining the content of FHIR Implementation Guides (IG). (built Thu, Feb 17, 2022 08:28+0000+00:00) http://hl7.org/fhir/uv/shorthand/N1/package.tgz http://hl7.org/fhir/uv/shorthand/N1/package.tgz HL7, Inc 4.0.1 IG Thu, 17 Feb 2022 12:00:00 +1100 GMT hl7.fhir.uv.sdc#3.0.0-preview The SDC specification provides an infrastructure to standardize the capture and expanded use of patient-level data collected within an EHR.<br/>This includes two components:<br/>* Support more sophisticated questionnaire/form use-cases such as those needed for research, oncology, pathology and other clinical domains.<br/>*Support pre-population and auto-population of EHR data into forms/questionnaires for uses outside direct clinical care (patient safety, adverse event reporting, public health reporting, etc.). (built Wed, Feb 16, 2022 19:39+1100+11:00) http://hl7.org/fhir/uv/sdc/3.0.0-preview/package.tgz http://hl7.org/fhir/uv/sdc/3.0.0-preview/package.tgz HL7, Inc 4.0.1 IG Wed, 16 Feb 2022 12:00:00 +1100 GMT hl7.fhir.us.ecr#2.0.0 # Introduction and Purpose With 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. With 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. For 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). For Clinical Safety Information please refer to the [FHIR Implementer’s Safety Checklist](http://hl7.org/fhir/safety.html). <div style="background-color: #ffffcc; border-left: 6px solid #ffeb3b;"> <p><b>Known Issue:</b></p> <p>The following issue is related to a publication tooling issue. A technical correction is planned once the tooling issue has been addressed.</p> <ul> <li><a href="https://jira.hl7.org/browse/FHIR-30477" rel="external" target="_blank">FHIR-30477</a>: Resolution errors for FHIRHelpers and FHIR-ModelInfo.</li> </ul> </div> # Stakeholders * Regulatory Agencies * Standards Development Organizations * Vendors: EHR, PHR; Health Care IT; Clinical Decision Support Systems, Public Health Surveillance Systems * Providers: Ambulatory and Healthcare Institutions (hospitals, long term care, mental health) * Local, State, Tribal and Federal Public Health Agencies (built Tue, Jan 18, 2022 12:56+0000+00:00) http://hl7.org/fhir/us/ecr/STU2/package.tgz http://hl7.org/fhir/us/ecr/STU2/package.tgz HL7, Inc 4.0.1 IG Tue, 18 Jan 2022 12:00:00 +1100 GMT hl7.fhir.us.ecr#2.0.0 # Introduction and Purpose With 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. With 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. For 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). For Clinical Safety Information please refer to the [FHIR Implementer’s Safety Checklist](http://hl7.org/fhir/safety.html). <div style="background-color: #ffffcc; border-left: 6px solid #ffeb3b;"> <p><b>Known Issue:</b></p> <p>The following issue is related to a publication tooling issue. A technical correction is planned once the tooling issue has been addressed.</p> <ul> <li><a href="https://jira.hl7.org/browse/FHIR-30477" rel="external" target="_blank">FHIR-30477</a>: Resolution errors for FHIRHelpers and FHIR-ModelInfo.</li> </ul> </div> # Stakeholders * Regulatory Agencies * Standards Development Organizations * Vendors: EHR, PHR; Health Care IT; Clinical Decision Support Systems, Public Health Surveillance Systems * Providers: Ambulatory and Healthcare Institutions (hospitals, long term care, mental health) * Local, State, Tribal and Federal Public Health Agencies (built Tue, Jan 18, 2022 12:56+0000+00:00) http://hl7.org/fhir/us/ecr/STU2/package.tgz http://hl7.org/fhir/us/ecr/STU2/package.tgz HL7, Inc 4.0.1 IG Tue, 18 Jan 2022 12:00:00 +1100 GMT hl7.fhir.us.mcode#2.0.0 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 Tue, Jan 18, 2022 03:16+0000+00:00) http://hl7.org/fhir/us/mcode/STU2/package.tgz http://hl7.org/fhir/us/mcode/STU2/package.tgz HL7, Inc 4.0.1 IG Tue, 18 Jan 2022 12:00:00 +1100 GMT hl7.fhir.us.qicore#4.1.0 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 Tue, Jan 18, 2022 15:24+0000+00:00) http://hl7.org/fhir/us/qicore/STU4.1/package.tgz http://hl7.org/fhir/us/qicore/STU4.1/package.tgz HL7, Inc 4.0.1 IG Tue, 18 Jan 2022 12:00:00 +1100 GMT hl7.fhir.us.davinci-pas#1.1.0 Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Mon, Dec 20, 2021 21:46+0000+00:00) http://hl7.org/fhir/us/davinci-pas/STU1.1/package.tgz http://hl7.org/fhir/us/davinci-pas/STU1.1/package.tgz HL7, Inc 4.0.1 IG Mon, 20 Dec 2021 12:00:00 +1100 GMT hl7.fhir.r5.core#5.0.0-snapshot1 FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (built Sun, Dec 19, 2021 08:15+1100+11:00) http://hl7.org/fhir/5.0.0-snapshot1/hl7.fhir.r5.core.tgz http://hl7.org/fhir/5.0.0-snapshot1/hl7.fhir.r5.core.tgz HL7, Inc 5.0.0-snapshot1 fhir.core Sun, 19 Dec 2021 12:00:00 +1100 GMT hl7.fhir.r5.expansions#5.0.0-snapshot1 Expansions for the 5.0.0-snapshot1 version of the FHIR standard (built Sun, Dec 19, 2021 08:15+1100+11:00) http://hl7.org/fhir/5.0.0-snapshot1/hl7.fhir.r5.expansions.tgz http://hl7.org/fhir/5.0.0-snapshot1/hl7.fhir.r5.expansions.tgz HL7, Inc 5.0.0-snapshot1 fhir.core Sun, 19 Dec 2021 12:00:00 +1100 GMT hl7.fhir.r5.examples#5.0.0-snapshot1 FHIR Examples package - the NPM package that contains all the examples in the base FHIR specification (built Tue, Dec 21, 2021 15:26+1100+11:00) http://hl7.org/fhir/5.0.0-snapshot1/hl7.fhir.r5.examples.tgz http://hl7.org/fhir/5.0.0-snapshot1/hl7.fhir.r5.examples.tgz HL7, Inc 5.0.0-snapshot1 fhir.core Sun, 19 Dec 2021 12:00:00 +1100 GMT hl7.fhir.core#5.0.0-snapshot1 FHIR Core - Group package for Release 5 Snapshot #1 http://hl7.org/fhir/5.0.0-snapshot1/package.tgz http://hl7.org/fhir/5.0.0-snapshot1/package.tgz HL7, Inc 5.0.0-snapshot1 fhir.core Sun, 19 Dec 2021 12:00:00 +1100 GMT hl7.fhir.us.central-cancer-registry-reporting#0.1.0 The Central Cancer Registry Reporting Content IG provides healthcare organizations the necessary data exchange mechanisms to report cancer data to public health agencies. (built Thu, Dec 9, 2021 14:20+0000+00:00) http://hl7.org/fhir/us/central-cancer-registry-reporting/2022Jan/package.tgz http://hl7.org/fhir/us/central-cancer-registry-reporting/2022Jan/package.tgz HL7, Inc 4.0.1 IG Thu, 09 Dec 2021 12:00:00 +1100 GMT hl7.fhir.us.health-care-surveys-reporting#0.1.0 The Health Care Surveys Content IG provides healthcare organizations the necessary data exchange mechanisms to report health care survey data to public health agencies. (built Thu, Dec 9, 2021 14:08+0000+00:00) http://hl7.org/fhir/us/health-care-surveys-reporting/2022Jan/package.tgz http://hl7.org/fhir/us/health-care-surveys-reporting/2022Jan/package.tgz HL7, Inc 4.0.1 IG Thu, 09 Dec 2021 12:00:00 +1100 GMT hl7.fhir.us.medmorph-research-dex#0.1.0 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) http://hl7.org/fhir/us/medmorph-research-dex/2022Jan/package.tgz http://hl7.org/fhir/us/medmorph-research-dex/2022Jan/package.tgz HL7, Inc 4.0.1 IG Thu, 09 Dec 2021 12:00:00 +1100 GMT hl7.fhir.us.covid19library#0.14.0 The COVID-19 IG describes structured data to be collected and communicated between providers and aggregators. (built Wed, Dec 8, 2021 02:46+0000+00:00) http://hl7.org/fhir/us/covid19library/2022Jan/package.tgz http://hl7.org/fhir/us/covid19library/2022Jan/package.tgz HL7, Inc 4.0.1 IG Wed, 08 Dec 2021 12:00:00 +1100 GMT hl7.fhir.us.medmorph#0.2.0 MedMorph describes a framework to enable submission of data from healthcare organizations to public health and research organizations. (built Wed, Dec 8, 2021 21:16+0000+00:00) http://hl7.org/fhir/us/medmorph/2022Jan/package.tgz http://hl7.org/fhir/us/medmorph/2022Jan/package.tgz HL7, Inc 4.0.1 IG Wed, 08 Dec 2021 12:00:00 +1100 GMT hl7.fhir.uv.radiation-dose-summary#0.1.0 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) http://hl7.org/fhir/uv/radiation-dose-summary/2022Jan/package.tgz http://hl7.org/fhir/uv/radiation-dose-summary/2022Jan/package.tgz HL7, Inc 4.0.1 IG Wed, 08 Dec 2021 12:00:00 +1100 GMT hl7.fhir.us.sdoh-clinicalcare#1.1.0 Social Determinants of Health (SDOH) are increasingly being recognized as essential factors that influence healthcare outcomes. This HL7 Implementation Guide (IG) defines how to exchange SDOH content defined by the Gravity Project using the Fast Healthcare Interoperability Resources (FHIR) standard. It defines how to represent coded content used to support the following care activities: screening, clinical assessment/diagnosis, goal setting, and the planning and performing of interventions. This IG addresses the need to gather SDOH information in multiple settings, share that information between stakeholders, and exchange referrals between organizations to address specific social risk needs, all with appropriate patient consent. In addition, the IG demonstrates how to share clinical data to support secondary purposes such as population health, quality, and research. The guide supports the following use cases: * Document SDOH data in conjunction with the patient encounters with providers, payers, and community services * Document and track SDOH related interventions to completion * Identify cohorts of individuals that have a common relationship to another entity (e.g., covered by the same payer) This implementation guide was developed by the Gravity Project, which specifically focuses on using HL7 FHIR to define standards for the exchange of SDOH-related information. Both the project and this implementation guide are focused on the U.S. environment. This implementation guide leverages content from the US Core implementation guide and binds to US-specific terminology. However, the basic constructs and interaction patterns may well be applicable outside the U.S. ### Content and organization The implementation guide is organized into the following sections: * Background: Includes [Gravity Background](gravity_background.html), [SDOH Clinical Care Scope](sdoh_clinical_care_scope.html), [Functional Use Cases](functional_use_cases.html), and [Technical Background](technical_background.html), that describe the environment in which this implementation guide establishes standards for information exchange * Context: Describes the [Survey Instrument Support](survey_instrument_support.html),[ QuestionnaireResponse Mapping Instructions](mapping_instructions.html), [Support for Multiple Domains](support_for_multiple_domains.html), and [Exchange Workflow diagram](exchange_workflow.html) that describes a high-level overview of expected process flow * Specifications: Provides a overview of the [FHIR Artifacts](fhir_artifacts_overview.html) defined and used in this IG, description of [Privacy and Security](privacy_and_security.html) issues, and explains [MustSupport and Missing Data](mustsupport_and_missing_data.html) concepts * [Downloads](downloads.html): Provides for the download of various IG related artifacts * [Credits](credits.html): Identifies the individuals and organizations involved in developing this implementation guide * [Artifacts Index](artifacts.html): Introduces and provides links to the FHIR R4 profiles, examples and other FHIR artifacts used in this implementation guide ### Note to Implementers Implementers should pay specific attention to the following sections: * [Technical Background](technical_background.html) if the implementer needs basic FHIR information references * [Survey Instrument Support](survey_instrument_support.html), and [ QuestionnaireResponse Mapping Instructions](mapping_instructions.html) if implementing support for structured assessment instruments * [Support for Multiple Domains](support_for_multiple_domains.html) to understand this IG's approach to domain specific value sets * [Exchange Workflow diagram](exchange_workflow.html) to understand the exchange workflows * [FHIR Artifacts](fhir_artifacts_overview.html) to understand the individual FHIR artifacts described in this IG * [Privacy and Security](privacy_and_security.html) for implementers that are concerned with privacy and security aspects related to implementing the information exchanges defined in this IG * [MustSupport and Missing Data](mustsupport_and_missing_data.html) to understand the interpretation of the MustSupport flags and the treatment of Missing Data used in this IG * [Artifacts Index](artifacts.html) all implementers need to understand the FHIR R4 profiles, examples and other FHIR artifacts defined in this implementation guide and linked from this section * [Downloads](downloads.html) links to allow implementers to download the IG and various artifacts New updates Includes all changes as of 12/1/2021 5:47 AM CT (built Tue, Dec 7, 2021 14:29+0000+00:00) http://hl7.org/fhir/us/sdoh-clinicalcare/2022Jan/package.tgz http://hl7.org/fhir/us/sdoh-clinicalcare/2022Jan/package.tgz HL7, Inc 4.0.1 IG Tue, 07 Dec 2021 12:00:00 +1100 GMT hl7.fhir.us.carin-bb#1.2.0 CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) (built Mon, Dec 6, 2021 20:26+0000+00:00) http://hl7.org/fhir/us/carin-bb/2022Jan/package.tgz http://hl7.org/fhir/us/carin-bb/2022Jan/package.tgz HL7, Inc 4.0.1 IG Mon, 06 Dec 2021 12:00:00 +1100 GMT hl7.fhir.us.cdmh#1.0.0 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) http://hl7.org/fhir/us/cdmh/STU1/package.tgz http://hl7.org/fhir/us/cdmh/STU1/package.tgz HL7, Inc 4.0.1 IG Mon, 06 Dec 2021 12:00:00 +1100 GMT hl7.fhir.us.davinci-ra#0.1.0 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 Mon, Dec 6, 2021 22:32+0000+00:00) http://hl7.org/fhir/us/davinci-ra/2022Jan/package.tgz http://hl7.org/fhir/us/davinci-ra/2022Jan/package.tgz HL7, Inc 4.0.1 IG Mon, 06 Dec 2021 12:00:00 +1100 GMT hl7.fhir.us.insurance-card#0.1.0 CARIN Digital Insurance Card (built Mon, Dec 6, 2021 22:18+0000+00:00) http://hl7.org/fhir/us/insurance-card/2022Jan/package.tgz http://hl7.org/fhir/us/insurance-card/2022Jan/package.tgz HL7, Inc 4.0.1 IG Mon, 06 Dec 2021 12:00:00 +1100 GMT hl7.fhir.us.pacio-adi#0.1.0 PACIO Advance Directive Interoperability Implementation Guide (built Mon, Dec 6, 2021 20:50+0000+00:00) http://hl7.org/fhir/us/pacio-adi/2022Jan/package.tgz http://hl7.org/fhir/us/pacio-adi/2022Jan/package.tgz HL7, Inc 4.0.1 IG Mon, 06 Dec 2021 12:00:00 +1100 GMT hl7.fhir.uv.ipa#0.1.0 http://hl7.org/fhir/uv/ipa/2022Jan/package.tgz http://hl7.org/fhir/uv/ipa/2022Jan/package.tgz HL7, Inc 4.0.1 IG Mon, 06 Dec 2021 12:00:00 +1100 GMT hl7.fhir.uv.fhir-for-fair#0.1.0 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) http://hl7.org/fhir/uv/fhir-for-fair/2022Jan/package.tgz http://hl7.org/fhir/uv/fhir-for-fair/2022Jan/package.tgz HL7, Inc 4.1.0 IG Sun, 05 Dec 2021 12:00:00 +1100 GMT hl7.fhir.us.davinci-pct#0.1.0 To support the request for cost information for specific services and items 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 Sat, Dec 4, 2021 21:54+0000+00:00) http://hl7.org/fhir/us/davinci-pct/2022Jan/package.tgz http://hl7.org/fhir/us/davinci-pct/2022Jan/package.tgz HL7, Inc 4.0.1 IG Sat, 04 Dec 2021 12:00:00 +1100 GMT hl7.fhir.us.pacio-rt#0.1.0 PACIO Re-Assessment Timepoints Implementation Guide (built Sat, Dec 4, 2021 14:09+0000+00:00) http://hl7.org/fhir/us/pacio-rt/2022Jan/package.tgz http://hl7.org/fhir/us/pacio-rt/2022Jan/package.tgz HL7, Inc 4.0.1 IG Sat, 04 Dec 2021 12:00:00 +1100 GMT hl7.fhir.us.davinci-drug-formulary#1.2.0 Da Vinci Payer Data Exchange (PDex) US Drug Formulary (STU2 ballot) (built Fri, Dec 3, 2021 18:36+0000+00:00) http://hl7.org/fhir/us/davinci-drug-formulary/2022Jan/package.tgz http://hl7.org/fhir/us/davinci-drug-formulary/2022Jan/package.tgz HL7, Inc 4.0.1 IG Fri, 03 Dec 2021 12:00:00 +1100 GMT hl7.fhir.us.exchange-routing#0.1.0 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 Fri, Dec 3, 2021 20:16+0000+00:00) http://hl7.org/fhir/us/exchange-routing/2022Jan/package.tgz http://hl7.org/fhir/us/exchange-routing/2022Jan/package.tgz HL7, Inc 4.0.1 IG Fri, 03 Dec 2021 12:00:00 +1100 GMT hl7.fhir.us.core#4.1.0 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. These 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 Mon, Dec 6, 2021 21:52+0000+00:00) http://hl7.org/fhir/us/core/2022Jan/package.tgz http://hl7.org/fhir/us/core/2022Jan/package.tgz HL7, Inc 4.0.1 IG Tue, 30 Nov 2021 12:00:00 +1100 GMT hl7.fhir.uv.bulkdata#2.0.0 FHIR based approach for exporting large data sets from a FHIR server to a client application (built Fri, Nov 26, 2021 05:56+1100+11:00) http://hl7.org/fhir/uv/bulkdata/STU2/package.tgz http://hl7.org/fhir/uv/bulkdata/STU2/package.tgz HL7, Inc 4.0.1 IG Fri, 26 Nov 2021 12:00:00 +1100 GMT hl7.fhir.uv.smart-app-launch#2.0.0 http://hl7.org/fhir/smart-app-launch/STU2/package.tgz http://hl7.org/fhir/smart-app-launch/STU2/package.tgz HL7, Inc 4.0.1 IG Fri, 26 Nov 2021 12:00:00 +1100 GMT hl7.fhir.us.pacio-cs#1.0.0 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) http://hl7.org/fhir/us/pacio-cs/STU1/package.tgz http://hl7.org/fhir/us/pacio-cs/STU1/package.tgz HL7, Inc 4.0.1 IG Wed, 03 Nov 2021 12:00:00 +1100 GMT hl7.fhir.us.pacio-fs#1.0.0 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) http://hl7.org/fhir/us/pacio-fs/STU1/package.tgz http://hl7.org/fhir/us/pacio-fs/STU1/package.tgz HL7, Inc 4.0.1 IG Wed, 03 Nov 2021 12:00:00 +1100 GMT hl7.fhir.us.dental-data-exchange#1.0.0 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. This 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. This guide defines 7 new profiles: * Dental Bundle * Dental Referral Note * Dental Service Request * Dental Consult Note * Dental Condition * Dental Finding * Dental Communication All 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. This HL7 FHIR® R4 Implementation Guide: Dental Data Exchange is developed in parallel to the HL7 CDA® R2 Implementation Guide: Dental Data Exchange. (built Tue, Nov 2, 2021 16:19+0000+00:00) http://hl7.org/fhir/us/dental-data-exchange/STU1/package.tgz http://hl7.org/fhir/us/dental-data-exchange/STU1/package.tgz HL7, Inc 4.0.1 IG Tue, 02 Nov 2021 12:00:00 +1100 GMT hl7.fhir.us.bfdr#1.0.0 Birth and fetal death reporting includes the transmission of data from health care providers to jurisdictional Vital Records Offices and national health statistics agencies. Data associated with the mother of the baby or fetus may be communicated independently from that associated directly with the labor and delivery encounter at the responsible healthcare facility. Note that for the purposes of this guide, "mother" always refers to the woman who delivered the infant. In cases of surrogacy or gestational carrier, the information reported should be for the surrogate or the gestational carrier, that is, the woman who delivered the infant. Also, the national statistics agency referred to in this guide is the [National Center for Health Statistics - CDC](https://www.cdc.gov/nchs/index.htm) (NCHS). This implementation guide (IG) defines a series of FHIR profiles on the Composition resource to represent electronic birth and fetal death reporting (BFDR) reports. It includes the content of medical/health information on live births and fetal deaths for select state and federal birth and fetal death reporting, as indicated in the 2003 Revision of the U.S. Standard Certificate of Live Birth and the U.S. Standard Report of Fetal Death. Additionally, it includes the content that is exchanged between electronic health record (EHR) systems, jurisdictions, and the Centers for Disease Control and Prevention/ National Center for Health Statistics (CDC/NCHS). ### Relationship to Other Standards This BFDR implementation guide standard complements other vital records standards to support the expansion of information flow to and from the national statistics agency. It is informed by: * [HL7, Version 2.6 Implementation Guide: Vital Records Birth and Fetal Death Reporting, Release 1,STU Release 2.1 - US Realm (April 2020)](https://www.hl7.org/implement/standards/product_brief.cfm?product_id=320) * [HL7, CDA® R2 Implementation Guide: Birth and Fetal Death Reporting, Release 1, STU Release 2 - US Realm (June 2019)](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=387) * [HL7, Vital Records Mortality and Morbidity Reporting (VRDR) FHIR Implementation Guide 1.0.0, STU 1 (October 2020)](http://hl7.org/fhir/us/vrdr/) * [IHE , Quality, Research and Public Health Technical Framework Supplement - Birth and Fetal Death Reporting-Enhanced (BFDR-E) (September 2018)](https://www.ihe.net/uploadedFiles/Documents/QRPH/IHE_QRPH_Suppl_BFDR-E.pdf) * [ONC, United States Core Data for Interoperability (USCDI) (April 2020)](https://www.healthit.gov/isa/united-states-core-data-interoperability-uscdi) ### Dependencies This implementation guide re-uses profiles from the following guides: * [Vital Records Common Profiles Library](http://hl7.org/fhir/us/vr-common-library) * [US Core Implementation Guide](http://hl7.org/fhir/us/core) ### Audience This guide is for analysts and developers who require guidance on the use of the HL7 FHIR for providing birth and fetal death reporting information. The implementation guide is informative to health care provider organizations, jurisdictional Vital Records Offices, CDC/NCHS, health information exchange organizations, and other vital records fetal death reporting stakeholders. ### Background This FHIR implementation guide builds on previous electronic data standards for transmitting vital records of death, birth, and fetal death. The goal has been to transmit reliable and relevant clinical information to jurisdictional Vital Records Offices and to transfer information from Vital Records Offices to the national statistics agency. Electronic vital records work started with the HL7 Vital Records Domain Analysis Model (VR DAM), published as an Informative Specification in 2011. The VR DAM was updated in 2017 with the HL7 Cross-Paradigm Domain Analysis Model: Vital Records, Release 2, in 2018, with Release 3, and in November 2020 as Release 4. This FHIR implementation guide uses the US Core profiles. Where this FHIR implementation guide is unable to use a US Core profile, we have followed the Cross Group Projects WG's variance request process, and have provided the US Realm Steering Committee an approved rationale for deviation in the implementation guide. ### How to Read This Guide This Guide is divided into several pages which are listed at the top of each page in the menu bar. * Home: The home page provides the introduction and background for HL7 FHIR® Vital Records Common Profiles Library. * Use Cases: This page details the use cases supported by this guide. * Implementer Guidance: This page details the worksheet Questionnaire format and the relationship to the IHE specification. * Terminology: This page provides a listing of the value sets used in this guide. * Downloads: This page provides links to downloadable artifacts. * Artifact Index: This page provides a list of the FHIR artifacts (profiles, examples, and value sets) defined as part of this guide. * Appendices: This pages provides examples of live birth and fetal death reports and worksheets. ### Author [HL7 International - Public Health](http://www.hl7.org/Special/committees/pher) ### Other Information This is the first FHIR BFDR standard. This guide is compliant with FHIR Release 4. For Clinical Safety Information please refer to the [FHIR Implementer’s Safety Checklist](http://hl7.org/fhir/safety.html). Disclaimer: All 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. (built Fri, Oct 22, 2021 14:56+0000+00:00) http://hl7.org/fhir/us/bfdr/STU1/package.tgz http://hl7.org/fhir/us/bfdr/STU1/package.tgz HL7, Inc 4.0.1 IG Fri, 22 Oct 2021 12:00:00 +1100 GMT hl7.fhir.us.davinci-drug-formulary#1.1.0 Da Vinci Payer Data Exchange (PDex) US Drug Formulary STU 1.1.0 (built Fri, Oct 15, 2021 15:46+0000+00:00) http://hl7.org/fhir/us/davinci-drug-formulary/STU1.1/package.tgz http://hl7.org/fhir/us/davinci-drug-formulary/STU1.1/package.tgz HL7, Inc 4.0.1 IG Fri, 15 Oct 2021 12:00:00 +1100 GMT hl7.fhir.us.nhsn-ade#1.0.0 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. This 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. The 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) http://hl7.org/fhir/us/nhsn-ade/STU1/package.tgz http://hl7.org/fhir/us/nhsn-ade/STU1/package.tgz HL7, Inc 4.0.1 IG Tue, 12 Oct 2021 12:00:00 +1100 GMT hl7.fhir.us.nhsn-med-admin#1.0.0 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. Medication 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. ### IG This implementation guide provides HL7 FHIR resources to define standards for exchange between a hospital and NHSN. This 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. This 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. This guide defines 4 new Profiles: * [Composition - Inpatient Medication Administration](StructureDefinition-Composition-inpatient-med-admin.html) * [Condition - Lab Confirmed COVID-19](StructureDefinition-Condition-lab-confirmed-covid.html) * [Condition - Suspected COVID-19](StructureDefinition-Condition-suspected-covid.html) * [Observation - Laboratory SARS COVID-19](StructureDefinition-Observation-lab-sars-cov.html) (built Tue, Oct 12, 2021 13:08+0000+00:00) http://hl7.org/fhir/us/nhsn-med-admin/STU1/package.tgz http://hl7.org/fhir/us/nhsn-med-admin/STU1/package.tgz HL7, Inc 4.0.1 IG Tue, 12 Oct 2021 12:00:00 +1100 GMT hl7.fhir.us.vr-common-library#1.0.0 The purpose of this project is to create an HL7 Fast Healthcare Interoperability Resources (FHIR) Library standard to support the needs of multiple Vital Records Implementation Guides. This guide is a FHIR Resources (FHIR) Library to support the needs of multiple Vital Records Implementation Guides. It does not provide any use case or scenario specific content or additional guidance on how to use these artifacts, but serves as a source for a standard set of profiles for reuse in multiple use case specific implementation guides focusing on the exchange of Vital Records information. Implementation details such as how and when to use a given artifact will be supplied in these guides. ### Background After evaluation and analysis of two separate FHIR IG projects - [Birth Defects Reporting](https://build.fhir.org/ig/HL7/fhir-birthdefectsreporting-ig/) and [Birth and Fetal Death Reporting](http://build.fhir.org/ig/HL7/fhir-bfdr), it was determined that there are many common data elements between the two IGs. The short-term scope of this common profiles library will include data elements common to the above-mentioned FHIR IGs and will define a US Realm specific framework that defines common elements for the implementation guides. The longer-term scope of this profiles library will include analysis and possible inclusion of data elements from other Vital Records projects (such as [Vital Records Mortality and Morbidity Reporting FHIR IG](https://build.fhir.org/ig/HL7/vrdr/)). To avoid defining the same profiles multiple times, this IG contains a US Realm focused profile library for use by Vital Records and other FHIR standards development efforts to define the appropriate FHIR profiles, value sets, etc., once and allow them to be referenced by each of the specific implementation guides. This profile library will provide a standard framework for inclusion in multiple use case specific implementation guides focused on the exchange of Vital Records information to support interoperability among public health systems and reduce provider and implementer burden. This FHIR implementation guide uses the US Core profiles. Where this FHIR implementation guide is unable to use a US Core profile, we have followed the Cross Group Projects WG's variance request process, and have provided the US Realm Steering Committee an approved rationale for deviation in the implementation guide. For Clinical Safety Information please refer to the [FHIR Implementer’s Safety Checklist](http://hl7.org/fhir/safety.html). ### How to Read This Guide This Guide is divided into several pages which are listed at the top of each page in the menu bar. * Home: The home page provides the introduction and background for HL7 FHIR® Vital Records Common Profiles Library. * Terminology: This page provides a listing of the value sets used in this guide. * Downloads: This page provides links to downloadable artifacts. * Artifact Index: This page provides a list of the FHIR artifacts (profiles, examples, and value sets) defined as part of this guide. (built Tue, Oct 12, 2021 12:37+0000+00:00) http://hl7.org/fhir/us/vr-common-library/STU1/package.tgz http://hl7.org/fhir/us/vr-common-library/STU1/package.tgz HL7, Inc 4.0.1 IG Tue, 12 Oct 2021 12:00:00 +1100 GMT hl7.fhir.uv.saner#1.0.0 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) http://hl7.org/fhir/uv/saner/STU1/package.tgz http://hl7.org/fhir/uv/saner/STU1/package.tgz HL7, Inc 4.0.1 IG Tue, 07 Sep 2021 12:00:00 +1000 GMT hl7.fhir.uv.cdisc-mapping#1.0.0 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) http://hl7.org/fhir/uv/cdisc-mapping/STU1/package.tgz http://hl7.org/fhir/uv/cdisc-mapping/STU1/package.tgz HL7, Inc 4.0.1 IG Tue, 31 Aug 2021 12:00:00 +1000 GMT hl7.fhir.us.covid19library#0.13.0 The COVID-19 IG describes structured data to be collected and communicated between providers and aggregators. (built Fri, Aug 27, 2021 17:16+0000+00:00) http://hl7.org/fhir/us/covid19library/2021Sep/package.tgz http://hl7.org/fhir/us/covid19library/2021Sep/package.tgz HL7, Inc 4.0.1 IG Fri, 27 Aug 2021 12:00:00 +1000 GMT hl7.fhir.uv.pocd#0.3.0 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) http://hl7.org/fhir/uv/pocd/2021Sep/package.tgz http://hl7.org/fhir/uv/pocd/2021Sep/package.tgz HL7, Inc 4.0.1 IG Sat, 14 Aug 2021 12:00:00 +1000 GMT hl7.fhir.us.military-service#0.1.0 Military Service History and Status is an implementation guide for veteran status and history verification and confirmation. (built Fri, Aug 13, 2021 16:25+0000+00:00) http://hl7.org/fhir/us/military-service/2021Sep/package.tgz http://hl7.org/fhir/us/military-service/2021Sep/package.tgz HL7, Inc 4.0.1 IG Fri, 13 Aug 2021 12:00:00 +1000 GMT hl7.fhir.us.vrdr#1.2.0 The VRDR FHIR IG provides guidance regarding the use of FHIR resources as a conduit for data required in the bidirectional exchange of mortality data between State-run Public Health Agencies (PHA) Vital Records offices and U.S. Centers for Disease Control and Prevention (CDC)/National Center for Health Statistics (NCHS). Bidirectional exchange of mortality data between PHA Vital Records offices and NCHS is essential to effective public health surveillance and emergency response efforts. Automation of the reporting process adds efficiencies that dramatically improves the efficacy of event response, data analysis, and evidence-based measurable prevention of the causes of death. The VRDR FHIR IG will provide guidance for the use of standard FHIR resources as a conduit for data required by vital records death reporting. The use of FHIR as a platform for automation of vital records death reporting is expected to improve existing automation by enabling wide-scale adoption and leveraging the potential of electronic health records and clinical decision support systems. The VRDR FHIR IG will lay a foundation for expansion of automated standards-driven information exchange to include tributary flows of information from entities such as physicians, medical examiners, coroners, funeral directors, and family members to public health agencies and between public health agencies and secondary users of detailed mortality data and aggregate statistics. This FHIR implementation guide is the primary work product of [project #1475](https://bit.ly/34DRIoA) "Vital Records Mortality and Morbidity Reporting FHIR IG" sponsored by the Health Level Seven (HL7) Public Health Work Group (PHWG). The scope of the project is to produce and ballot a Standard for Trail Use (STU) Fast Healthcare Interoperability Resources (FHIR) implementation guide (IG) for use in reporting of death events to the U.S. National Center for Health Statistics (NCHS) by State and Local Public Health Agencies (PHA). The VRDR FHIR IG is based upon FHIR R4. The VRDR FHIR IG was successfully balloted as a standard for trial use (STU) in May 2019. This is a U.S. Realm Specification. This guide and related materials are based on reporting specifications in U.S. jurisdictions. The data content of this IG are based upon the [U.S. Standard Certificate of Death](https://www.cdc.gov/nchs/data/dvs/DEATH11-03final-ACC.pdf). (built Fri, Aug 13, 2021 12:58+0000+00:00) http://hl7.org/fhir/us/vrdr/2021Sep/package.tgz http://hl7.org/fhir/us/vrdr/2021Sep/package.tgz HL7, Inc 4.0.1 IG Fri, 13 Aug 2021 12:00:00 +1000 GMT hl7.fhir.uv.shc-vaccination#0.6.2 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) http://hl7.org/fhir/uv/shc-vaccination/2021Sep/package.tgz http://hl7.org/fhir/uv/shc-vaccination/2021Sep/package.tgz HL7, Inc 4.0.1 IG Fri, 13 Aug 2021 12:00:00 +1000 GMT hl7.fhir.us.cancer-reporting#0.1.0 This implementation guide provides 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. 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 message bundle and is compliant with FHIR Release 4. (built Thu, Aug 12, 2021 15:45+0000+00:00) http://hl7.org/fhir/us/cancer-reporting/2021Sep/package.tgz http://hl7.org/fhir/us/cancer-reporting/2021Sep/package.tgz HL7, Inc 4.0.1 IG Thu, 12 Aug 2021 12:00:00 +1000 GMT hl7.fhir.uv.eyecare#0.1.0 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) http://hl7.org/fhir/uv/eyecare/2021Sep/package.tgz http://hl7.org/fhir/uv/eyecare/2021Sep/package.tgz HL7, Inc 4.0.1 IG Thu, 12 Aug 2021 12:00:00 +1000 GMT hl7.fhir.uv.security-label-ds4p#0.3.0 Application of FHIR meta.security to segment FHIR Bundles and Resources per applicable policy. (built Thu, Aug 12, 2021 14:25+0000+00:00) http://hl7.org/fhir/uv/security-label-ds4p/2021Sep/package.tgz http://hl7.org/fhir/uv/security-label-ds4p/2021Sep/package.tgz HL7, Inc 4.0.1 IG Thu, 12 Aug 2021 12:00:00 +1000 GMT hl7.fhir.us.sirb#0.1.0 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 Tue, Aug 10, 2021 13:14+0000+00:00) http://hl7.org/fhir/us/sirb/2021Sep/package.tgz http://hl7.org/fhir/us/sirb/2021Sep/package.tgz HL7, Inc 4.0.1 IG Tue, 10 Aug 2021 12:00:00 +1000 GMT hl7.fhir.uv.shorthand#1.2.0 Describes FHIR Shorthand (FSH), a domain-specific language (DSL) for defining the content of FHIR Implementation Guides (IG). (built Tue, Aug 10, 2021 15:07+0000+00:00) http://hl7.org/fhir/uv/shorthand/2021Sep/package.tgz http://hl7.org/fhir/uv/shorthand/2021Sep/package.tgz HL7, Inc 4.0.1 IG Tue, 10 Aug 2021 12:00:00 +1000 GMT hl7.fhir.us.udap-security#0.1.0 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 Fri, Aug 6, 2021 15:57+0000+00:00) http://hl7.org/fhir/us/udap-security/2021Sep/package.tgz http://hl7.org/fhir/us/udap-security/2021Sep/package.tgz HL7, Inc 4.0.1 IG Fri, 06 Aug 2021 12:00:00 +1000 GMT hl7.fhir.us.icsr-ae-reporting#0.1.0 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 Thu, Aug 5, 2021 14:33+0000+00:00) http://hl7.org/fhir/us/icsr-ae-reporting/2021Sep/package.tgz http://hl7.org/fhir/us/icsr-ae-reporting/2021Sep/package.tgz HL7, Inc 4.0.1 IG Thu, 05 Aug 2021 12:00:00 +1000 GMT hl7.fhir.us.sdoh-clinicalcare#1.0.0 Social Determinants of Health (SDOH) are increasingly being recognized as essential factors that influence healthcare outcomes. This HL7 Implementation Guide (IG) defines how to exchange SDOH content defined by the Gravity Project using the Fast Healthcare Interoperability Resources (FHIR) standard. It defines how to represent coded content used to support the following care activities: screening, clinical assessment/diagnosis, goal setting, and the planning and performing of interventions. This IG addresses the need to gather SDOH information in multiple settings, share that information between stakeholders, and exchange referrals between organizations to address specific social risk needs, all with appropriate patient consent. In addition, the IG demonstrates how to share clinical data to support secondary purposes such as population health, quality, and research. The guide supports the following use cases: * Document SDOH data in conjunction with the patient encounters with providers, payers, and community services * Document and track SDOH related interventions to completion * Identify cohorts of individuals that have a common relationship to another entity (e.g., covered by the same payer) This implementation guide was developed by the Gravity Project, which specifically focuses on using HL7 FHIR to define standards for the exchange of SDOH-related information. Both the project and this implementation guide are focused on the U.S. environment. This implementation guide leverages content from the US Core implementation guide and binds to US-specific terminology. However, the basic constructs and interaction patterns may well be applicable outside the U.S. ### Content and organization The implementation guide is organized into the following sections: * Background: Includes [Gravity Background](gravity_background.html), [SDOH Clinical Care Scope](sdoh_clinical_care_scope.html), [Functional Use Cases](functional_use_cases.html), and [Technical Background](technical_background.html), that describe the environment in which this implementation guide establishes standards for information exchange * Context: Describes the [Survey Instrument Support](survey_instrument_support.html),[ QuestionnaireResponse Mapping Instructions](mapping_instructions.html), [Support for Multiple Domains](support_for_multiple_domains.html), and [Exchange Workflow diagram](exchange_workflow.html) that describes a high-level overview of expected process flow * Specifications: Provides a overview of the [FHIR Artifacts](fhir_artifacts_overview.html) defined and used in this IG, description of [Privacy and Security](privacy_and_security.html) issues, and explains [MustSupport and Missing Data](mustsupport_and_missing_data.html) concepts * [Downloads](downloads.html): Provides for the download of various IG related artifacts * [Credits](credits.html): Identifies the individuals and organizations involved in developing this implementation guide * [Artifacts Index](artifacts.html): Introduces and provides links to the FHIR R4 profiles, examples and other FHIR artifacts used in this implementation guide ### Note to Implementers Implementers should pay specific attention to the following sections: * [Technical Background](technical_background.html) if the implementer needs basic FHIR information references * [Survey Instrument Support](survey_instrument_support.html), and [ QuestionnaireResponse Mapping Instructions](mapping_instructions.html) if implementing support for structured assessment instruments * [Support for Multiple Domains](support_for_multiple_domains.html) to understand this IG's approach to domain specific value sets * [Exchange Workflow diagram](exchange_workflow.html) to understand the exchange workflows * [FHIR Artifacts](fhir_artifacts_overview.html) to understand the individual FHIR artifacts described in this IG * [Privacy and Security](privacy_and_security.html) for implementers that are concerned with privacy and security aspects related to implementing the information exchanges defined in this IG * [MustSupport and Missing Data](mustsupport_and_missing_data.html) to understand the interpretation of the MustSupport flags and the treatment of Missing Data used in this IG * [Artifacts Index](artifacts.html) all implementers need to understand the FHIR R4 profiles, examples and other FHIR artifacts defined in this implementation guide and linked from this section * [Downloads](downloads.html) links to allow implementers to download the IG and various artifacts (built Thu, Aug 5, 2021 20:07+0000+00:00) http://hl7.org/fhir/us/sdoh-clinicalcare/STU1/package.tgz http://hl7.org/fhir/us/sdoh-clinicalcare/STU1/package.tgz HL7, Inc 4.0.1 IG Thu, 05 Aug 2021 12:00:00 +1000 GMT hl7.fhir.us.odh#1.1.0 **HL7 FHIR Profile: Occupational Data for Health (ODH), Release 1.1 (Standard for Trial Use)** This 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. **Introduction and Guidance** This 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. This 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. While 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. **Background** The 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. The 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. **Scope** The 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: • Employment Status • Retirement Date • Combat Zone Period • Past or Present Job for the patient or a household member, which includes: o Past or Present Job Occupation o Past or Present Job Industry o Work Classification o Work Schedule, which includes: - Weekly Work Days - Daily Work Hours o Job Duty o Occupational Hazard o Employer name o Employer address o Related Subject (when it is Past or Present Job of a household member of the person) o Start/End Dates • Usual Work of the patient or a household member, which includes: o Usual Occupation o Usual Industry o Usual Occupation Duration o Related Subject (when it is Usual Work of a household member of the person) o Start Date **Known Issues and Limitations** This 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. While multiple retirement dates are supported, the retirement date is not linked to any specific job, or usual occupation. **Credits** Co-Editor: Lori Reed-Fourquet e-HealthSign, LLC lfourquet@ehealthsign.com Co-Editor: Rob Hausam Hausam Consulting rob@hausamconsulting.com Co-Editor: Mark Kramer MITRE Corporation mkramer@mitre.org This 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). The 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. **Authors** Name Email/URL HL7 International - Public Health http://www.hl7.org/Special/committees/pher (built Mon, Jul 12, 2021 17:46+0000+00:00) http://hl7.org/fhir/us/odh/STU1.1/package.tgz http://hl7.org/fhir/us/odh/STU1.1/package.tgz HL7, Inc 4.0.1 IG Mon, 12 Jul 2021 12:00:00 +1000 GMT hl7.fhir.us.carin-bb#1.1.0 CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) (built Fri, Jul 2, 2021 17:52+0000+00:00) http://hl7.org/fhir/us/carin-bb/STU1.1/package.tgz http://hl7.org/fhir/us/carin-bb/STU1.1/package.tgz HL7, Inc 4.0.1 IG Fri, 02 Jul 2021 12:00:00 +1000 GMT hl7.fhir.us.core#4.0.0 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. These 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 Mon, Jun 28, 2021 19:09+0000+00:00) http://hl7.org/fhir/us/core/STU4/package.tgz http://hl7.org/fhir/us/core/STU4/package.tgz HL7, Inc 4.0.1 IG Mon, 28 Jun 2021 12:00:00 +1000 GMT hl7.fhir.us.immds#1.0.0 An IG for querying a decision support engine for a personalized immunization forecast. (built Fri, Jun 25, 2021 15:56+1000+10:00) http://hl7.org/fhir/us/immds/STU1/package.tgz http://hl7.org/fhir/us/immds/STU1/package.tgz HL7, Inc 4.0.1 IG Fri, 25 Jun 2021 12:00:00 +1000 GMT hl7.fhir.us.davinci-deqm#3.0.0 http://hl7.org/fhir/us/davinci-deqm/STU3/package.tgz http://hl7.org/fhir/us/davinci-deqm/STU3/package.tgz HL7, Inc 4.0.1 IG Mon, 21 Jun 2021 12:00:00 +1000 GMT hl7.fhir.us.specialty-rx#1.0.0 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 Mon, Jun 21, 2021 14:20+0000+00:00) http://hl7.org/fhir/us/specialty-rx/STU1/package.tgz http://hl7.org/fhir/us/specialty-rx/STU1/package.tgz HL7, Inc 4.0.1 IG Mon, 21 Jun 2021 12:00:00 +1000 GMT hl7.fhir.uv.bulkdata#1.1.0 FHIR based approach for exporting large data sets from a FHIR server to a client application (built Fri, Apr 16, 2021 11:36+1000+10:00) http://hl7.org/fhir/uv/bulkdata/2021May/package.tgz http://hl7.org/fhir/uv/bulkdata/2021May/package.tgz HL7, Inc 4.0.1 IG Fri, 16 Apr 2021 12:00:00 +1000 GMT hl7.fhir.uv.smart-app-launch#1.1.0 http://hl7.org/fhir/smart-app-launch/2021May/package.tgz http://hl7.org/fhir/smart-app-launch/2021May/package.tgz HL7, Inc 4.0.1 IG Fri, 16 Apr 2021 12:00:00 +1000 GMT hl7.fhir.r5.core#4.6.0 FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (built Thu, Apr 15, 2021 12:25+1000+10:00) http://hl7.org/fhir/2021May/hl7.fhir.r5.core.tgz http://hl7.org/fhir/2021May/hl7.fhir.r5.core.tgz HL7, Inc 4.6.0 fhir.core Thu, 15 Apr 2021 12:00:00 +1000 GMT hl7.fhir.r5.expansions#4.6.0 Expansions for the 4.6.0 version of the FHIR standard (built Thu, Apr 15, 2021 12:25+1000+10:00) http://hl7.org/fhir/2021May/hl7.fhir.r5.expansions.tgz http://hl7.org/fhir/2021May/hl7.fhir.r5.expansions.tgz HL7, Inc 4.6.0 fhir.core Thu, 15 Apr 2021 12:00:00 +1000 GMT hl7.fhir.r5.examples#4.6.0 Example resources in the R5 version of the FHIR standard (Ballot #1) http://hl7.org/fhir/2021May/hl7.fhir.r5.examples.tgz http://hl7.org/fhir/2021May/hl7.fhir.r5.examples.tgz HL7, Inc 4.6.0 fhir.core Thu, 15 Apr 2021 12:00:00 +1000 GMT hl7.fhir.core#4.6.0 FHIR Core - Group package for Release 5 Draft Ballot http://hl7.org/fhir/2021May/package.tgz http://hl7.org/fhir/2021May/package.tgz HL7, Inc 4.6.0 fhir.core Thu, 15 Apr 2021 12:00:00 +1000 GMT hl7.fhir.us.mcode#1.16.0 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 Thu, Apr 15, 2021 12:44+0000+00:00) http://hl7.org/fhir/us/mcode/2021May/package.tgz http://hl7.org/fhir/us/mcode/2021May/package.tgz HL7, Inc 4.0.1 IG Thu, 15 Apr 2021 12:00:00 +1000 GMT hl7.fhir.us.cqfmeasures#2.1.0 The Fast Healthcare Interoperability Resource (FHIR) Quality Measure Implementation Guide (this IG) describes an approach to representing electronic Clinical Quality Measures (eCQMs) 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 Tue, Apr 13, 2021 15:56+0000+00:00) http://hl7.org/fhir/us/cqfmeasures/2021May/package.tgz http://hl7.org/fhir/us/cqfmeasures/2021May/package.tgz HL7, Inc 4.0.1 IG Tue, 13 Apr 2021 12:00:00 +1000 GMT hl7.fhir.us.nhsn-med-admin#0.1.0 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. Medication 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. ### IG This implementation guide provides HL7 FHIR resources to define standards for exchange between a hospital and NHSN. This 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 wtih the Health Level Seven (HL7) Pharmacy Work Group. Resources in this US Realm implementation guide are specific to reporting medication administration data to NHSN. This guide contains a library of FHIR profiles and is compliant with FHIR Release 4. At a minimum, a Document Bundle amd Composition will be exchanged along with a Patient, and associated COVID-19 Condition and laboratory results. This guide defines 4 new Profiles: * [Composition - Inpatient Medication Administration](StructureDefinition-Composition-inpatient-med-admin.html) * [Condition - Lab Confirmed COVID-19](StructureDefinition-Condition-lab-confirmed-covid.html) * [Condition - Suspected COVID-19](StructureDefinition-Condition-suspected-covid.html) * [Observation - Laboratory SARS COVID-19](StructureDefinition-Observation-lab-sars-cov.html) (built Tue, Apr 13, 2021 00:12+0000+00:00) http://hl7.org/fhir/us/nhsn-med-admin/2021May/package.tgz http://hl7.org/fhir/us/nhsn-med-admin/2021May/package.tgz HL7, Inc 4.0.1 IG Tue, 13 Apr 2021 12:00:00 +1000 GMT hl7.fhir.uv.genomics-reporting#1.1.0 Guidelines for reporting of clinical genomics results using HL7 FHIR (built Tue, Apr 13, 2021 19:12+0000+00:00) http://hl7.org/fhir/uv/genomics-reporting/2021May/package.tgz http://hl7.org/fhir/uv/genomics-reporting/2021May/package.tgz HL7, Inc 4.0.1 IG Tue, 13 Apr 2021 12:00:00 +1000 GMT hl7.fhir.uv.security-label-ds4p#0.2.0 Application of FHIR meta.security to segment FHIR Bundles and Resources per applicable policy. (built Tue, Apr 13, 2021 13:39+0000+00:00) http://hl7.org/fhir/uv/security-label-ds4p/2021May/package.tgz http://hl7.org/fhir/uv/security-label-ds4p/2021May/package.tgz HL7, Inc 4.0.1 IG Tue, 13 Apr 2021 12:00:00 +1000 GMT hl7.fhir.us.nhsn-ade#0.1.0 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. This 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. The 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 Mon, Apr 12, 2021 23:58+0000+00:00) http://hl7.org/fhir/us/nhsn-ade/2021May/package.tgz http://hl7.org/fhir/us/nhsn-ade/2021May/package.tgz HL7, Inc 4.0.1 IG Mon, 12 Apr 2021 12:00:00 +1000 GMT hl7.fhir.r4b.core#4.1.0 FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (built Thu, Mar 11, 2021 17:06+1100+11:00) http://hl7.org/fhir/2021Mar/hl7.fhir.r4b.core.tgz http://hl7.org/fhir/2021Mar/hl7.fhir.r4b.core.tgz HL7, Inc 4.1.0 fhir.core Thu, 11 Mar 2021 12:00:00 +1100 GMT hl7.fhir.r4b.expansions#4.1.0 Expansions for the 4.1.0 version of the FHIR standard (built Thu, Mar 11, 2021 17:06+1100+11:00) http://hl7.org/fhir/2021Mar/hl7.fhir.r4b.expansions.tgz http://hl7.org/fhir/2021Mar/hl7.fhir.r4b.expansions.tgz HL7, Inc 4.1.0 fhir.core Thu, 11 Mar 2021 12:00:00 +1100 GMT hl7.fhir.core#4.1.0 FHIR Core - Group package for Release 4B Ballot #1 http://hl7.org/fhir/2021Mar/package.tgz http://hl7.org/fhir/2021Mar/package.tgz HL7, Inc 4.1.0 fhir.core Thu, 11 Mar 2021 12:00:00 +1100 GMT hl7.fhir.us.phcp#1.0.0 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. This guide contains a library of Fast Health Interoperability Resources (FHIR) profiles, and is compliant with the C-CDA on FHIR specification. ### Content and Organization * [Background](background.html): describes the purpose, audience, general background, and use cases for this guide * [Specification](specification.html): covers the detailed implementation requirements and conformance expectation * [Acknowledgments](acknowledgments.html): identifies the individuals and organizations involved in developing this implementation guide * [Downloads](downloads.html): allows download of this and other specifications as well as other useful files * [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 (built Thu, Feb 11, 2021 17:05+0000+00:00) http://hl7.org/fhir/us/phcp/STU1/package.tgz http://hl7.org/fhir/us/phcp/STU1/package.tgz HL7, Inc 4.0.1 IG Thu, 11 Feb 2021 12:00:00 +1100 GMT hl7.fhir.uv.cpg#1.0.0 Implementation guidance for creating Clinical Practice Guidelines with formal artifacts to facilitate sharing and implementation of the guideline (built Thu, Feb 11, 2021 20:29+0000+00:00) http://hl7.org/fhir/uv/cpg/STU1/package.tgz http://hl7.org/fhir/uv/cpg/STU1/package.tgz HL7, Inc 4.0.1 IG Thu, 11 Feb 2021 12:00:00 +1100 GMT hl7.fhir.us.davinci-atr#1.0.0 Exchange of member attribution list between payers and providers (built Mon, Feb 8, 2021 19:02+0000+00:00) http://hl7.org/fhir/us/davinci-atr/STU1/package.tgz http://hl7.org/fhir/us/davinci-atr/STU1/package.tgz HL7, Inc 4.0.1 IG Mon, 08 Feb 2021 12:00:00 +1100 GMT hl7.fhir.us.core#3.2.0 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. These 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 Wed, Dec 16, 2020 20:52+0000+00:00) http://hl7.org/fhir/us/core/2021Jan/package.tgz http://hl7.org/fhir/us/core/2021Jan/package.tgz HL7, Inc 4.0.1 IG Sat, 30 Jan 2021 12:00:00 +1100 GMT hl7.fhir.us.davinci-dtr#1.0.0 Guidelines for documentation templates and rules for coverage requirements (built Wed, Dec 23, 2020 03:54+0000+00:00) http://hl7.org/fhir/us/davinci-dtr/STU1/package.tgz http://hl7.org/fhir/us/davinci-dtr/STU1/package.tgz HL7, Inc 4.0.1 IG Wed, 23 Dec 2020 12:00:00 +1100 GMT hl7.fhir.us.davinci-pcde#1.0.0 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) http://hl7.org/fhir/us/davinci-pcde/STU1/package.tgz http://hl7.org/fhir/us/davinci-pcde/STU1/package.tgz HL7, Inc 4.0.1 IG Wed, 23 Dec 2020 12:00:00 +1100 GMT hl7.fhir.us.davinci-crd#1.0.0 Guidelines for conveying coverage requirements to clinicians when planning treatment (built Tue, Dec 22, 2020 14:27+0000+00:00) http://hl7.org/fhir/us/davinci-crd/STU1/package.tgz http://hl7.org/fhir/us/davinci-crd/STU1/package.tgz HL7, Inc 4.0.1 IG Tue, 22 Dec 2020 12:00:00 +1100 GMT hl7.fhir.us.davinci-pdex#1.0.0 This specification is currently undergoing ballot and connectathon testing. It is expected to evolve, possibly significantly, as part of that process. Feedback 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. This 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. [Financial Management](https://confluence.hl7.org/display/FM/Financial+Management+Home) is the Sponsoring Work Group for this Implementation Guide. **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 Profiles based on FHIR R4) which can be understood by providers and, if they choose to, committed to their Electronic Medical Records (EMR) System.** The 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. This IG uses the same Member Health History "payload" for member-authorized exchange of information with other Health Plans 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. This IG covers the exchange of: - Claims-based information - Clinical Information (such as Lab Results, Allergies and Conditions) This 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. This IG covers the exchange of a Member's Health History in the following scenarios: - Provider requested Provider-Health Plan Exchange using CDS-Hooks and SMART-on-FHIR - Member-authorized Health Plan to Health Plan exchange - Member-authorized Health Plan to Third-Party Application exchange The latter two scenarios are provided to meet the requirements identified in the CMS Interoperability Notice for Proposed Rule Making issued on February 11, 2019. **There are items in this guide that are subject to update**. This includes: - Value Sets - Vocabularies (X12, NUBC etc.) - Examples **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). See the [Table of Contents](toc.html) for more information. (built Tue, Dec 22, 2020 14:16+0000+00:00) http://hl7.org/fhir/us/davinci-pdex/STU1/package.tgz http://hl7.org/fhir/us/davinci-pdex/STU1/package.tgz HL7, Inc 4.0.1 IG Tue, 22 Dec 2020 12:00:00 +1100 GMT hl7.fhir.us.davinci-drug-formulary#1.0.1 Da Vinci Payer Data Exchange (PDex) US Drug Formulary STU 1.0.1 (built Mon, Dec 21, 2020 16:49+0000+00:00) http://hl7.org/fhir/us/davinci-drug-formulary/STU1.0.1/package.tgz http://hl7.org/fhir/us/davinci-drug-formulary/STU1.0.1/package.tgz HL7, Inc 4.0.1 IG Mon, 21 Dec 2020 12:00:00 +1100 GMT hl7.fhir.us.davinci-pas#1.0.0 Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Sun, Dec 20, 2020 19:17+0000+00:00) http://hl7.org/fhir/us/davinci-pas/STU1/package.tgz http://hl7.org/fhir/us/davinci-pas/STU1/package.tgz HL7, Inc 4.0.1 IG Sun, 20 Dec 2020 12:00:00 +1100 GMT hl7.fhir.us.davinci-pdex-plan-net#1.0.0 Davinci PDEX Plan Net (built Sun, Dec 20, 2020 06:11+0000+00:00) http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1/package.tgz http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1/package.tgz HL7, Inc 4.0.1 IG Sun, 20 Dec 2020 12:00:00 +1100 GMT hl7.fhir.uv.livd#0.3.0 Recommended LOINC mappings for IVD Devices (built Fri, Dec 18, 2020 22:06+0000+00:00) http://hl7.org/fhir/uv/livd/2021Jan/package.tgz http://hl7.org/fhir/uv/livd/2021Jan/package.tgz HL7, Inc 4.0.1 IG Fri, 18 Dec 2020 12:00:00 +1100 GMT hl7.fhir.us.bfdr#0.1.0 Birth and fetal death reporting includes the transmission of data from health care providers to jurisdictional Vital Records Offices and national health statistics agencies. Data associated with the mother of the baby or fetus may be communicated independently from that associated directly with the labor and delivery encounter at the responsible healthcare facility. Note that for the purposes of this guide, "mother" always refers to the woman who delivered the infant. In cases of surrogacy or gestational carrier, the information reported should be for the surrogate or the gestational carrier, that is, the woman who delivered the infant. ### Scope This implementation guide (IG) defines a series of FHIR profiles on the Composition resource to represent electronic birth and fetal death reporting (BFDR). It includes the content of medical/health information on live births and fetal deaths for select state and federal birth and fetal death reporting, as indicated in the 2003 Revision of the U.S. Standard Certificate of Live Birth and the U.S. Standard Report of Fetal Death. Additionally, it includes the content that is exchanged between electronic health record (EHR) systems, jurisdictions, and the Centers for Disease Control and Prevention/ National Center for Health Statistics (CDC/NCHS). This guide is compliant with FHIR Release 4. All 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. ### Relationship to Other Standards This BFDR implementation guide standard complements other vital records standards to support the expansion of information flow to and from NCHS. It is informed by: * [HL7, Version 2.6 Implementation Guide: Vital Records Birth and Fetal Death Reporting, Release 1,STU Release 2.1 - US Realm (April 2020)](https://www.hl7.org/implement/standards/product_brief.cfm?product_id=320) * [HL7, CDA® R2 Implementation Guide: Birth and Fetal Death Reporting, Release 1, STU Release 2 - US Realm (June 2019)](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=387) * [HL7, Vital Records Mortality and Morbidity Reporting (VRDR) FHIR Implementation Guide 1.0.0, STU 1 (October 2020)](http://hl7.org/fhir/us/vrdr/) * [IHE , Quality, Research and Public Health Technical Framework Supplement - Birth and Fetal Death Reporting-Enhanced (BFDR-E) (September 2018)](https://www.ihe.net/uploadedFiles/Documents/QRPH/IHE_QRPH_Suppl_BFDR-E.pdf) * [ONC, United States Core Data for Interoperability (USCDI) (April 2020)](https://www.healthit.gov/isa/united-states-core-data-interoperability-uscdi) ### Audience This guide is for analysts and developers who require guidance on the use of the HL7 FHIR for providing birth and fetal death reporting information. The implementation guide is informative to health care provider organizations, jurisdictional Vital Records Offices, CDC/NCHS, health information exchange organizations, and other vital records fetal death reporting stakeholders. ### Background This FHIR implementation guide builds on previous electronic data standards for transmitting vital records of death, birth, and fetal death. The goal has been to transmit reliable and relevant clinical information to jurisdictional Vital Records Offices and to transfer information from vital records offices to the national statistics agency. Electronic vital records work started with the HL7 Vital Records Domain Analysis Model (VR DAM), published as an Informative Specification in 2011. The VR DAM was updated in 2017 with the HL7 Cross-Paradigm Domain Analysis Model: Vital Records, Release 2, and, in 2018, with Release 3. This is the first FHIR BFDR standard. (built Wed, Dec 16, 2020 19:11+0000+00:00) http://hl7.org/fhir/us/bfdr/2021Jan/package.tgz http://hl7.org/fhir/us/bfdr/2021Jan/package.tgz HL7, Inc 4.0.1 IG Wed, 16 Dec 2020 12:00:00 +1100 GMT hl7.fhir.us.davinci-cdex#0.2.0 This IG provides detailed guidance that helps implementers use FHIR-based interactions and resources relevant to support specific exchanges of clinical information between provider and payers (or other providers). What is unique about this guide is that is provides additional technical guidance on two FHIR transaction approaches for requesting information: - Direct Query - Task Based Approach: The types of clinical data is not limited to FHIR resources, but includes C-CDA documents, pdfs, text files and other types of data. There may be requests for payloads of clinical records of care such as CCD Documents, clinical data sets that may be represented in a FHIR bundles, and clinical data such as a specific FHIR resource. By using the FHIR standard and implementing this guide the quality of information shared can be improved. Payers can be explicit about the data they are requesting, as opposed to general requests which often result in providers sending more information than might be necessary to make sure claims are supported. Benefits resulting from the information exchange interaction include: - Improve care coordination - Support risk adjustment - Ease quality management - Facilitate claims auditing - Confirm medical necessity - Support orders and referrals (built Wed, Dec 16, 2020 19:01+0000+00:00) http://hl7.org/fhir/us/davinci-cdex/2021Jan/package.tgz http://hl7.org/fhir/us/davinci-cdex/2021Jan/package.tgz HL7, Inc 4.0.1 IG Wed, 16 Dec 2020 12:00:00 +1100 GMT hl7.fhir.us.ecr#1.1.0 # Introduction and Purpose With the adoption and maturing of Electronic Health Records (EHRs) there are opportunities to better support public health surveillance as well as 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. With 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 investigation supplemental data, and to connect public health information (e.g., guidelines) and clinical workflow. 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. For 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). # Stakeholders * Regulatory Agencies * Standards Development Organizations * Vendors: EHR, PHR; Health Care IT; Clinical Decision Support Systems, Public Health Surveillance Systems * Providers: Ambulatory and Healthcare Institutions (hospitals, long term care, mental health) * Local, State, Tribal and Federal Public Health Agencies (built Wed, Dec 16, 2020 19:27+0000+00:00) http://hl7.org/fhir/us/ecr/2021Jan/package.tgz http://hl7.org/fhir/us/ecr/2021Jan/package.tgz HL7, Inc 4.0.1 IG Wed, 16 Dec 2020 12:00:00 +1100 GMT hl7.fhir.us.ecr#1.1.0 # Introduction and Purpose With the adoption and maturing of Electronic Health Records (EHRs) there are opportunities to better support public health surveillance as well as 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. With 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 investigation supplemental data, and to connect public health information (e.g., guidelines) and clinical workflow. 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. For 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). # Stakeholders * Regulatory Agencies * Standards Development Organizations * Vendors: EHR, PHR; Health Care IT; Clinical Decision Support Systems, Public Health Surveillance Systems * Providers: Ambulatory and Healthcare Institutions (hospitals, long term care, mental health) * Local, State, Tribal and Federal Public Health Agencies (built Wed, Dec 16, 2020 19:27+0000+00:00) http://hl7.org/fhir/us/ecr/2021Jan/package.tgz http://hl7.org/fhir/us/ecr/2021Jan/package.tgz HL7, Inc 4.0.1 IG Wed, 16 Dec 2020 12:00:00 +1100 GMT hl7.fhir.us.medmorph#0.1.0 MedMorph describes a framework to enable submission of data from healthcare organizations to public health and research organizations. (built Wed, Dec 16, 2020 20:21+0000+00:00) http://hl7.org/fhir/us/medmorph/2021Jan/package.tgz http://hl7.org/fhir/us/medmorph/2021Jan/package.tgz HL7, Inc 4.0.1 IG Wed, 16 Dec 2020 12:00:00 +1100 GMT hl7.fhir.us.sdoh-clinicalcare#0.1.0 Social Determinants of Health (SDOH) are increasingly being recognized as essential factors that influence healthcare outcomes. This HL7 Implementation Guide (IG) defines how to exchange SDOH content defined by the Gravity Project using the Fast Healthcare Ineroperability Resources (FHIR) standard. It defines how to represent coded content used to support the following care activities: screening, clinical assessment/diagnosis, goal setting, and the planning and performing of interventions. This IG addresses the need to gather SDOH information in the context of clinical encounters and describes how to share SDOH information and other relevant information with outside organizations for the purpose of coordinating services and support to address SDOH related needs. In addition, the IG demonstrates how to share clinical data to support secondary purposes such as population health, quality, and research. The guide supports the following use cases: * Document SDOH data in conjunction with the patient encounters * Document and track SDOH related interventions to completion * Gather and aggregate SDOH data for uses beyond the point of care (e.g. public health, population health, quality measurement, risk adjustment, quality improvement, and research) This implementation guide was developed under the auspices of the Gravity FHIR accelerator project, which specifically focuses on using HL7 FHIR to define standards for the exchange of SDOH-related information. Both the project and this implementation guide are focused on the U.S. environment. This implementation guide leverages content from the US Core implementation guide and binds to US-specific terminology. However, the basic constructs and interaction patterns may well be applicable outside the U.S. ### Content and organization The implementation guide is organized into the following sections: * Background: Includes [Gravity Background](http://build.fhir.org/ig/HL7/fhir-sdoh-clinicalcare/gravity_background.html), [SDOH Clinical Care Scope](http://build.fhir.org/ig/HL7/fhir-sdoh-clinicalcare/sdoh_clinical_care_scope.html), [Personas and Patient Stories](http://build.fhir.org/ig/HL7/fhir-sdoh-clinicalcare/personas_and_patient_stories.html) that describe the SDOH environment surrounding the intended use of this implementation guide * Context: Describes the [Survey Instrument Support](http://build.fhir.org/ig/HL7/fhir-sdoh-clinicalcare/survey_instrument_support.html),[ QuestionnaireResponse Mapping Instructions](http://build.fhir.org/ig/HL7/fhir-sdoh-clinicalcare/mapping_instructions.html), [Support for Multiple Domains](http://build.fhir.org/ig/HL7/fhir-sdoh-clinicalcare/support_for_multiple_domains.html), and [Exchange Workflow diagram](http://build.fhir.org/ig/HL7/fhir-sdoh-clinicalcare/exchange_workflow.html) that describes a high-level overview of expected process flow * Specifications: Provides a [Technical Background](http://build.fhir.org/ig/HL7/fhir-sdoh-clinicalcare/technical_background.html), overview of the [FHIR Artifacts](http://build.fhir.org/ig/HL7/fhir-sdoh-clinicalcare/fhir_artifacts_overview.html) defined and used in this IG, description of [Privacy and Security](http://build.fhir.org/ig/HL7/fhir-sdoh-clinicalcare/privacy_and_security.html) issues, and explains [MustSupport and Missing Data](http://build.fhir.org/ig/HL7/fhir-sdoh-clinicalcare/mustsupport_and_missing_data.html) concepts * [Downloads](http://build.fhir.org/ig/HL7/fhir-sdoh-clinicalcare/downloads.html): Provides for the download of various IG related artifacts * [Credits](http://build.fhir.org/ig/HL7/fhir-sdoh-clinicalcare/credits.html): Identifies the individuals and organizations involved in developing this implementation guide * [Artifacts Index](http://build.fhir.org/ig/HL7/fhir-sdoh-clinicalcare/artifacts.html): Introduces and provides links to the FHIR R4 profiles, examples and other FHIR artifacts used in this implementation guide (built Wed, Dec 16, 2020 20:13+0000+00:00) http://hl7.org/fhir/us/sdoh-clinicalcare/2021Jan/package.tgz http://hl7.org/fhir/us/sdoh-clinicalcare/2021Jan/package.tgz HL7, Inc 4.0.1 IG Wed, 16 Dec 2020 12:00:00 +1100 GMT hl7.fhir.us.specialty-rx#0.1.0 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 Wed, Dec 16, 2020 17:56+0000+00:00) http://hl7.org/fhir/us/specialty-rx/2021Jan/package.tgz http://hl7.org/fhir/us/specialty-rx/2021Jan/package.tgz HL7, Inc 4.0.1 IG Wed, 16 Dec 2020 12:00:00 +1100 GMT hl7.fhir.us.vr-common-library#0.1.0 The purpose of this project is to create an HL7 Fast Healthcare Interoperability Resources (FHIR) Library standard to support the needs of multiple Vital Records Implementation Guides. After evaluation and analysis of two separate FHIR IG projects - [Birth Defects Reporting](https://build.fhir.org/ig/HL7/fhir-birthdefectsreporting-ig/) and [Birth and Fetal Death Reporting](http://build.fhir.org/ig/HL7/fhir-bfdr), it was determined that there are many common data elements between the two IGs. The short-term scope of this common profiles library will include data elements common to the above-mentioned FHIR IGs and will define a US Realm specific framework that defines common elements for the implementation guides. The longer-term scope of this profiles library will include analysis and possible inclusion of data elements from other Vital Records projects (such as [Vital Records Mortality and Morbidity Reporting FHIR IG](https://build.fhir.org/ig/HL7/vrdr/)). To avoid defining the same profiles multiple times, we propose to create a US Realm focused profile library for use by Vital Records and other FHIR standards development efforts to define the appropriate FHIR profiles, value sets, etc., once and allow them to be referenced by each of the specific implementation guides. This profile library will provide a standard framework for inclusion in multiple use case specific implementation guides focused on the exchange of Vital Records information to support interoperability among public health systems and reduce provider and implementer burden. (built Wed, Dec 16, 2020 17:44+0000+00:00) http://hl7.org/fhir/us/vr-common-library/2021Jan/package.tgz http://hl7.org/fhir/us/vr-common-library/2021Jan/package.tgz HL7, Inc 4.0.1 IG Wed, 16 Dec 2020 12:00:00 +1100 GMT hl7.fhir.uv.cdisc-mapping#0.1.0 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 Wed, Dec 16, 2020 20:35+0000+00:00) http://hl7.org/fhir/uv/cdisc-mapping/2021Jan/package.tgz http://hl7.org/fhir/uv/cdisc-mapping/2021Jan/package.tgz HL7, Inc 4.0.1 IG Wed, 16 Dec 2020 12:00:00 +1100 GMT hl7.fhir.uv.subscriptions-backport#0.1.0 The Subscription R5 Backport Implementation Guide enables servers running verions of FHIR earlier than R5 to implement a subset of R5 Subscriptions in a standardized way. (built Wed, Dec 16, 2020 17:36+0000+00:00) http://hl7.org/fhir/uv/subscriptions-backport/2021Jan/package.tgz http://hl7.org/fhir/uv/subscriptions-backport/2021Jan/package.tgz HL7, Inc 4.0.1 IG Wed, 16 Dec 2020 12:00:00 +1100 GMT hl7.fhir.uv.bulkdata#1.0.1 http://hl7.org/fhir/uv/bulkdata/STU1.0.1/package.tgz http://hl7.org/fhir/uv/bulkdata/STU1.0.1/package.tgz HL7, Inc 4.0.1 IG Fri, 04 Dec 2020 12:00:00 +1100 GMT hl7.fhir.us.carin-bb#1.0.0 CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) (built Mon, Nov 23, 2020 17:25+0000+00:00) http://hl7.org/fhir/us/carin-bb/STU1/package.tgz http://hl7.org/fhir/us/carin-bb/STU1/package.tgz HL7, Inc 4.0.1 IG Mon, 23 Nov 2020 12:00:00 +1100 GMT hl7.fhir.us.vrdr#1.0.0 The VRDR FHIR IG provides guidance regarding the use of FHIR resources as a conduit for data required in the bidirectional exchange of mortality data between State-run Public Health Agencies (PHA) Vital Records offices and U.S. Centers for Disease Control and Prevention (CDC)/National Center for Health Statistics (NCHS). Bidirectional exchange of mortality data between PHA Vital Records offices and NCHS is essential to effective public health surveillance and emergency response efforts. Automation of the reporting process adds efficiencies that dramatically improves the efficacy of event response, data analysis, and evidence-based measurable prevention of the causes of death. The VRDR FHIR IG will provide guidance for the use of standard FHIR resources as a conduit for data required by vital records death reporting. The use of FHIR as a platform for automation of vital records death reporting is expected to improve existing automation by enabling wide-scale adoption and leveraging the potential of electronic health records and clinical decision support systems. The VRDR FHIR IG will lay a foundation for expansion of automated standards-driven information exchange to include tributary flows of information from entities such as physicians, medical examiners, coroners, funeral directors, and family members to public health agencies and between public health agencies and secondary users of detailed mortality data and aggregate statistics. This FHIR implementation guide is the primary work product of [project #1475](https://bit.ly/34DRIoA) "Vital Records Mortality and Morbidity Reporting FHIR IG" sponsored by the Health Level Seven (HL7) Public Health Work Group (PHWG). The scope of the project is to produce and ballot a Standard for Trail Use (STU) Fast Healthcare Interoperability Resources (FHIR) implementation guide (IG) for use in reporting of death events to the U.S. National Center for Health Statistics (NCHS) by State and Local Public Health Agencies (PHA). The VRDR FHIR IG is based upon FHIR R4. The VRDR FHIR IG was successfully balloted as a standard for trial use (STU) in May 2019. This is a U.S. Realm Specification. This guide and related materials are based on reporting specifications in U.S. jurisdictions. The data content of this IG are based upon the [U.S. Standard Certificate of Death](https://www.cdc.gov/nchs/data/dvs/DEATH11-03final-ACC.pdf). (built Tue, Oct 27, 2020 16:24+0000+00:00) http://hl7.org/fhir/us/vrdr/STU1/package.tgz http://hl7.org/fhir/us/vrdr/STU1/package.tgz HL7, Inc 4.0.1 IG Tue, 27 Oct 2020 12:00:00 +1100 GMT hl7.fhir.us.ccda#1.1.0 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. This 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). The 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. We 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. ## Scope To represent Consolidated CDA Templates for Clinical Notes (C-CDA) 2.1 templates using FHIR profiles. This first stage of the project defines all the C-CDA document-level profiles on the Composition resource and contained sections. Any 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. For further information see the C-CDA specification here: http://www.hl7.org/implement/standards/product_brief.cfm?product_id=408. (built Wed, Oct 21, 2020 22:01+0000+00:00) http://hl7.org/fhir/us/ccda/STU1.1/package.tgz http://hl7.org/fhir/us/ccda/STU1.1/package.tgz HL7, Inc 4.0.1 IG Wed, 21 Oct 2020 12:00:00 +1100 GMT hl7.fhir.us.pacio-cs#0.1.0 To advance interoperable health data exchange between post-acute care (PAC) and other providers, patients, and key stakeholders (built Mon, Oct 19, 2020 22:42+0000+00:00) http://hl7.org/fhir/us/pacio-cs/2021Jan/package.tgz http://hl7.org/fhir/us/pacio-cs/2021Jan/package.tgz HL7, Inc 4.0.1 IG Mon, 19 Oct 2020 12:00:00 +1100 GMT hl7.fhir.us.pacio-fs#0.1.0 To advance interoperable health data exchange between post-acute care (PAC) and other providers, patients, and key stakeholders (built Mon, Oct 19, 2020 22:19+0000+00:00) http://hl7.org/fhir/us/pacio-fs/2021Jan/package.tgz http://hl7.org/fhir/us/pacio-fs/2021Jan/package.tgz HL7, Inc 4.0.1 IG Mon, 19 Oct 2020 12:00:00 +1100 GMT hl7.fhir.uv.saner#0.1.0 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 Mon, Oct 19, 2020 21:05+0000+00:00) http://hl7.org/fhir/uv/saner/2021Jan/package.tgz http://hl7.org/fhir/uv/saner/2021Jan/package.tgz HL7, Inc 4.0.1 IG Mon, 19 Oct 2020 12:00:00 +1100 GMT hl7.fhir.us.davinci-alerts#1.0.0 http://hl7.org/fhir/us/davinci-alerts/STU1/package.tgz http://hl7.org/fhir/us/davinci-alerts/STU1/package.tgz HL7, Inc 4.0.1 IG Thu, 15 Oct 2020 12:00:00 +1100 GMT hl7.fhir.uv.shorthand#1.0.0 Describes FHIR Shorthand (FSH), a domain-specific language (DSL) for defining the content of FHIR Implementation Guides (IG). (built Mon, Oct 12, 2020 15:26+1100+11:00) http://hl7.org/fhir/uv/shorthand/STU1/package.tgz http://hl7.org/fhir/uv/shorthand/STU1/package.tgz HL7, Inc 4.0.1 IG Mon, 12 Oct 2020 12:00:00 +1100 GMT hl7.fhir.uv.cdisc-lab#1.0.0 http://hl7.org/fhir/uv/cdisc-lab/STU1/package.tgz http://hl7.org/fhir/uv/cdisc-lab/STU1/package.tgz HL7, Inc 4.0.1 IG Thu, 27 Aug 2020 12:00:00 +1000 GMT hl7.fhir.us.carin-rtpbc#1.0.0 This is a guide for implementing the Consumer-Focused Real-Time Pharmacy Benefit Check (consumer RTPBC) using FHIR R4. Using RTPBC, a patient can learn the cost and insurance coverage related to medications they've been prescribed. Specifically: how a medication will be covered by their insurance, including out of pocket costs and any coverage restrictions or requirements that might apply, discount pricing available for the medication. Consumer RTPBC leverages the predetermination process supported by the Claim and ClaimResponse FHIR resources. Accompanying resources carry information that identifies the patient and their insurance coverage, prescription information and the preferred pharmacy (Patient, Coverage, MedicationRequest, Practitioner and Organization). (built Tue, Aug 25, 2020 19:54+0000+00:00) http://hl7.org/fhir/us/carin-rtpbc/STU1/package.tgz http://hl7.org/fhir/us/carin-rtpbc/STU1/package.tgz HL7, Inc 4.0.1 IG Tue, 25 Aug 2020 12:00:00 +1000 GMT hl7.fhir.r5.core#4.5.0 FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (built Thu, Aug 20, 2020 17:41+1000+10:00) http://hl7.org/fhir/2020Sep/hl7.fhir.r5.core.tgz http://hl7.org/fhir/2020Sep/hl7.fhir.r5.core.tgz HL7, Inc 4.5.0 fhir.core Thu, 20 Aug 2020 12:00:00 +1000 GMT hl7.fhir.r5.expansions#4.5.0 Expansions for the R5 version of the FHIR standard (built Thu, Aug 20, 2020 17:41+1000+10:00) http://hl7.org/fhir/2020Sep/hl7.fhir.r5.expansions.tgz http://hl7.org/fhir/2020Sep/hl7.fhir.r5.expansions.tgz HL7, Inc 4.5.0 fhir.core Thu, 20 Aug 2020 12:00:00 +1000 GMT hl7.fhir.r5.examples#4.5.0 Example resources in the R5 version of the FHIR standard http://hl7.org/fhir/2020Sep/hl7.fhir.r5.examples.tgz http://hl7.org/fhir/2020Sep/hl7.fhir.r5.examples.tgz HL7, Inc 4.5.0 fhir.core Thu, 20 Aug 2020 12:00:00 +1000 GMT hl7.fhir.core#4.5.0 FHIR Core - Group package for Release 5 Preview #3 http://hl7.org/fhir/2020Sep/package.tgz http://hl7.org/fhir/2020Sep/package.tgz HL7, Inc 4.5.0 fhir.core Thu, 20 Aug 2020 12:00:00 +1000 GMT hl7.fhir.us.davinci-deqm#2.1.0 http://hl7.org/fhir/us/davinci-deqm/2020Sep/package.tgz http://hl7.org/fhir/us/davinci-deqm/2020Sep/package.tgz HL7, Inc 4.0.1 IG Sat, 15 Aug 2020 12:00:00 +1000 GMT hl7.fhir.us.davinci-deqm#2.0.0 http://hl7.org/fhir/us/davinci-deqm/STU2/package.tgz http://hl7.org/fhir/us/davinci-deqm/STU2/package.tgz HL7, Inc 4.0.1 IG Sat, 15 Aug 2020 12:00:00 +1000 GMT hl7.fhir.us.davinci-hrex#0.2.0 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. Da 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. The 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. HRex 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 Sun, Aug 9, 2020 15:38+0000+00:00) http://hl7.org/fhir/us/davinci-hrex/2020Sep/package.tgz http://hl7.org/fhir/us/davinci-hrex/2020Sep/package.tgz HL7, Inc 4.0.1 IG Fri, 14 Aug 2020 12:00:00 +1000 GMT hl7.fhir.uv.v2mappings#0.1.0 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 Wed, Aug 12, 2020 20:10+0000+00:00) http://hl7.org/fhir/uv/v2mappings/2020Sep/package.tgz http://hl7.org/fhir/uv/v2mappings/2020Sep/package.tgz HL7, Inc 4.0.1 IG Wed, 12 Aug 2020 12:00:00 +1000 GMT hl7.fhir.uv.smart-web-messaging#0.1.0 The SMART Web Messaging Implementation Guide enables SMART-launched apps a standard way to communicate with the fixture that launched the app. (built Tue, Aug 11, 2020 16:30+0000+00:00) http://hl7.org/fhir/uv/smart-web-messaging/2020Sep/package.tgz http://hl7.org/fhir/uv/smart-web-messaging/2020Sep/package.tgz HL7, Inc 4.0.1 IG Tue, 11 Aug 2020 12:00:00 +1000 GMT hl7.fhir.us.dental-data-exchange#0.1.0 Note to balloters: This implementation guide as balloted depends on the current build of CCDAonFHIR#2.0.0, in it's final form ready for publication, but due to publication timing, CCDAonFHIR#2.0.0 is not yet released. A technical correction may be published to correct this dependency subsequently if this proves necessary once CCDAonFHIR#2.0.0 is published 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. This 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. This guide defines 5 new Profiles: * Dental Consult Note * Dental Communication * Dental Service Request * Dental Findings * Dental Referral Note All 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. This HL7 FHIR® R4 Implementation Guide: Dental Data Exchange is developed in parallel to the HL7 CDA® R2 Implementation Guide: Dental Data Exchange. (built Mon, Aug 10, 2020 19:19+0000+00:00) http://hl7.org/fhir/us/dental-data-exchange/2020Sep/package.tgz http://hl7.org/fhir/us/dental-data-exchange/2020Sep/package.tgz HL7, Inc 4.0.1 IG Mon, 10 Aug 2020 12:00:00 +1000 GMT hl7.fhir.us.dme-orders#0.2.0 # General This 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. * 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. * This specification is currently undergoing connectathon testing. It is expected to evolve, possibly significantly, as part of that process. This 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. # Change log * **0.2.* :**QA versions for the September 2020 ballot cycle (minor version 0.2.x) include QA feedback * **0.3.0 :** Final version for the September 2020 ballot cycle # Known issues and to-dos * Example of message bundle for message based ordering (built Mon, Aug 10, 2020 18:26+0000+00:00) http://hl7.org/fhir/us/dme-orders/2020Sep/package.tgz http://hl7.org/fhir/us/dme-orders/2020Sep/package.tgz HL7, Inc 4.0.1 IG Mon, 10 Aug 2020 12:00:00 +1000 GMT hl7.fhir.uv.pddi#0.2.0 This implementation guide provides conformance requirements and guidance for the representation, distribution, and evaluation of potential drug-drug interactions. (built Mon, Aug 10, 2020 16:56+0000+00:00) http://hl7.org/fhir/uv/pddi/2020Sep/package.tgz http://hl7.org/fhir/uv/pddi/2020Sep/package.tgz HL7, Inc 4.0.1 IG Mon, 10 Aug 2020 12:00:00 +1000 GMT hl7.fhir.us.vitals#0.1.0 http://hl7.org/fhir/us/vitals/2020Sep/package.tgz http://hl7.org/fhir/us/vitals/2020Sep/package.tgz HL7, Inc 4.0.1 IG Fri, 07 Aug 2020 12:00:00 +1000 GMT hl7.fhir.uv.order-catalog#0.1.0 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) http://hl7.org/fhir/uv/order-catalog/2020Sep/package.tgz http://hl7.org/fhir/uv/order-catalog/2020Sep/package.tgz HL7, Inc 4.0.1 IG Wed, 05 Aug 2020 12:00:00 +1000 GMT hl7.fhir.us.cqfmeasures#2.0.0 The Fast Healthcare Interoperability Resource (FHIR) Quality Measure Implementation Guide (this IG) describes an approach to representing electronic Clinical Quality Measures (eCQMs) 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, Jul 23, 2020 20:24+0000+00:00) http://hl7.org/fhir/us/cqfmeasures/STU2/package.tgz http://hl7.org/fhir/us/cqfmeasures/STU2/package.tgz HL7, Inc 4.0.1 IG Thu, 23 Jul 2020 12:00:00 +1000 GMT hl7.fhir.us.core#3.1.1 http://hl7.org/fhir/us/core/STU3.1.1/package.tgz http://hl7.org/fhir/us/core/STU3.1.1/package.tgz HL7, Inc 4.0.1 IG Tue, 30 Jun 2020 12:00:00 +1000 GMT hl7.fhir.uv.ips#1.0.0 International Patient Summary (IPS) FHIR Implementation Guide (built Tue, May 19, 2020 18:36+0000+00:00) http://hl7.org/fhir/uv/ips/STU1/package.tgz http://hl7.org/fhir/uv/ips/STU1/package.tgz HL7, Inc 4.0.1 IG Tue, 19 May 2020 12:00:00 +1000 GMT hl7.fhir.r5.core#4.4.0 FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (built Tue, May 12, 2020 23:09+1000+10:00) http://hl7.org/fhir/2020May/hl7.fhir.r5.core.tgz http://hl7.org/fhir/2020May/hl7.fhir.r5.core.tgz HL7, Inc 4.4.0 fhir.core Mon, 04 May 2020 12:00:00 +1000 GMT hl7.fhir.r5.expansions#4.4.0 Expansions for the R5 version of the FHIR standard (built Tue, May 12, 2020 23:09+1000+10:00) http://hl7.org/fhir/2020May/hl7.fhir.r5.expansions.tgz http://hl7.org/fhir/2020May/hl7.fhir.r5.expansions.tgz HL7, Inc 4.4.0 fhir.core Mon, 04 May 2020 12:00:00 +1000 GMT hl7.fhir.core#4.4.0 FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification http://hl7.org/fhir/2020May/package.tgz http://hl7.org/fhir/2020May/package.tgz HL7, Inc 4.4.0 fhir.core Mon, 04 May 2020 12:00:00 +1000 GMT hl7.fhir.uv.mhealth-framework#0.1.0 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) http://hl7.org/fhir/uv/mhealth-framework/2020May/package.tgz http://hl7.org/fhir/uv/mhealth-framework/2020May/package.tgz HL7, Inc 4.0.1 IG Thu, 16 Apr 2020 12:00:00 +1000 GMT hl7.fhir.uv.security-label-ds4p#0.1.0 Application of FHIR meta.security to segment FHIR Bundles and Resources per applicable policy. (built Wed, Apr 8, 2020 12:30+0000+00:00) http://hl7.org/fhir/uv/security-label-ds4p/2020May/package.tgz http://hl7.org/fhir/uv/security-label-ds4p/2020May/package.tgz HL7, Inc 4.0.1 IG Tue, 07 Apr 2020 12:00:00 +1000 GMT hl7.fhir.us.dme-orders#0.1.0 # General This is a FHIR R4 Implementation Guide to support the electronic exchange of post-acute orders, along with the exchange of supporting documentation between the ordering provider and the specific supplier. * The initial version of the implementation guide (IG) will focus on orders and documentation for Durable Medical Equipment (DME) and Home Health Services. * This specification is currently undergoing connectathon testing. It is expected to evolve, possibly significantly, as part of that process. This implementation guide is the result of work sponsored by CMS's Center for Program Integrity, whose goal is to advance the ability for providers to supply services that are medically necessary and appropriate to Medicare Beneficiaries. By enabling providers to communicate orders and supporting documentation in real-time to suppliers, beneficiaries can receive appropriate treatment more rapidly and reduce the burden on providers and suppliers to comply with documentation requirements. # Note to balloters **Please comment on the existing material and not on items that are know issues or to-dos (these will be addressed in the STU ballot version planned for the Septemeber Ballot Cycle) There is a section of the IG (Requests to Balloters) that solicits feedback from balloters on items of interest to the authors -- please respond with your recommedations** # Feedback Comments and suggestions are welcome on our Zulip stream... or send a note to rdieterle@enablecare.us # Change log * **0.1.1 (this version):** QA version for the May 2020 ballot cycle Note: prior changes consolided into this Ballot for Comment version # Known issues and to-dos * Complex extensions are defined but not added to DeviceRequest, ServiceRequest and MedicationRequest * Will add examples during ballot reconciliation * Will add specific terminologies and value sets for post-acute orders during ballot reconcilliation (built Wed, Apr 8, 2020 13:17+0000+00:00) http://hl7.org/fhir/us/dme-orders/2020May/package.tgz http://hl7.org/fhir/us/dme-orders/2020May/package.tgz HL7, Inc 4.0.1 IG Thu, 02 Apr 2020 12:00:00 +1100 GMT hl7.fhir.uv.shorthand#0.12.0 Describes FHIR Shorthand (FSH), a domain-specific language (DSL) for defining the content of FHIR Implementation Guides (IG). (built Wed, Apr 1, 2020 17:24+0000+00:00) http://hl7.org/fhir/uv/shorthand/2020May/package.tgz http://hl7.org/fhir/uv/shorthand/2020May/package.tgz HL7, Inc 4.0.1 IG Tue, 31 Mar 2020 12:00:00 +1100 GMT hl7.fhir.us.qicore#4.0.0 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 Tue, Mar 24, 2020 21:02+0000+00:00) http://hl7.org/fhir/us/qicore/STU4/package.tgz http://hl7.org/fhir/us/qicore/STU4/package.tgz HL7, Inc 4.0.1 IG Thu, 19 Mar 2020 12:00:00 +1100 GMT hl7.fhir.us.mcode#1.0.0 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, Mar 18, 2020 15:31+0000+00:00) http://hl7.org/fhir/us/mcode/STU1/package.tgz http://hl7.org/fhir/us/mcode/STU1/package.tgz HL7, Inc 4.0.1 IG Wed, 18 Mar 2020 12:00:00 +1100 GMT hl7.fhir.us.bser#1.0.0 The Bidirectional Services eReferral (BSeR) FHIR implementation guide provides guidance for using the HL7 Fast Healthcare Interoperability Resources (FHIR) standard as an exchange format for clinical and non-clinical service requests. It is a collection of profiled FHIR resources designed for use in information exchanges supporting the placement of a service request by a referral initiating provider and the reporting of service delivery outcomes by a referral recipient provider. The goal of the BSeR project is to streamline and enhance the efficacy of the exchange of health information between health care systems and community services organizations involved in addressing chronic health conditions by establishing information exchange standards for electronic referrals and referral outcome reporting. (built Mon, Mar 2, 2020 22:24+0000+00:00) http://hl7.org/fhir/us/bser/STU1/package.tgz http://hl7.org/fhir/us/bser/STU1/package.tgz HL7, Inc 4.0.1 IG Mon, 02 Mar 2020 12:00:00 +1100 GMT hl7.fhir.us.ecr#1.0.0 # Introduction and Purpose With the adoption and maturing of Electronic Health Records (EHRs) there are opportunities to better support public health surveillance as well as 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. With 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 investigation supplemental data, and to connect public health information (e.g., guidelines) and clinical workflow. 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. For 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). # Stakeholders * Regulatory Agencies * Standards Development Organizations * Vendors: EHR, PHR; Health Care IT; Clinical Decision Support Systems, Public Health Surveillance Systems * Providers: Ambulatory and Healthcare Institutions (hospitals, long term care, mental health) * Local, State, Tribal and Federal Public Health Agencies (built Wed, Jan 29, 2020 20:29+0000+00:00) http://hl7.org/fhir/us/ecr/STU1/package.tgz http://hl7.org/fhir/us/ecr/STU1/package.tgz HL7, Inc 4.0.1 IG Wed, 29 Jan 2020 12:00:00 +1100 GMT hl7.fhir.us.ecr#1.0.0 # Introduction and Purpose With the adoption and maturing of Electronic Health Records (EHRs) there are opportunities to better support public health surveillance as well as 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. With 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 investigation supplemental data, and to connect public health information (e.g., guidelines) and clinical workflow. 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. For 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). # Stakeholders * Regulatory Agencies * Standards Development Organizations * Vendors: EHR, PHR; Health Care IT; Clinical Decision Support Systems, Public Health Surveillance Systems * Providers: Ambulatory and Healthcare Institutions (hospitals, long term care, mental health) * Local, State, Tribal and Federal Public Health Agencies (built Wed, Jan 29, 2020 20:29+0000+00:00) http://hl7.org/fhir/us/ecr/STU1/package.tgz http://hl7.org/fhir/us/ecr/STU1/package.tgz HL7, Inc 4.0.1 IG Wed, 29 Jan 2020 12:00:00 +1100 GMT hl7.fhir.us.davinci-drug-formulary#1.0.0 http://hl7.org/fhir/us/davinci-drug-formulary/STU1/package.tgz http://hl7.org/fhir/us/davinci-drug-formulary/STU1/package.tgz HL7, Inc 4.0.1 IG Tue, 21 Jan 2020 12:00:00 +1100 GMT hl7.fhir.us.odh#1.0.0 http://hl7.org/fhir/us/odh/STU1/package.tgz http://hl7.org/fhir/us/odh/STU1/package.tgz HL7, Inc 4.0.1 IG Wed, 08 Jan 2020 12:00:00 +1100 GMT hl7.fhir.r5.core#4.2.0 FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (built Tue, Dec 31, 2019 21:03+1100+11:00) http://hl7.org/fhir/2020Feb/hl7.fhir.r5.core.tgz http://hl7.org/fhir/2020Feb/hl7.fhir.r5.core.tgz HL7, Inc 4.2.0 fhir.core Tue, 31 Dec 2019 12:00:00 +1100 GMT hl7.fhir.r5.expansions#4.2.0 Expansions for the R5 version of the FHIR standard (built Tue, Dec 31, 2019 21:03+1100+11:00) http://hl7.org/fhir/2020Feb/hl7.fhir.r5.expansions.tgz http://hl7.org/fhir/2020Feb/hl7.fhir.r5.expansions.tgz HL7, Inc 4.2.0 fhir.core Tue, 31 Dec 2019 12:00:00 +1100 GMT hl7.fhir.core#4.2.0 FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification http://hl7.org/fhir/2020Feb/package.tgz http://hl7.org/fhir/2020Feb/package.tgz HL7, Inc 4.2.0 fhir.core Tue, 31 Dec 2019 12:00:00 +1100 GMT hl7.fhir.us.davinci-deqm#1.1.0 http://hl7.org/fhir/us/davinci-deqm/2020Feb/package.tgz http://hl7.org/fhir/us/davinci-deqm/2020Feb/package.tgz HL7, Inc 4.0.1 IG Fri, 27 Dec 2019 12:00:00 +1100 GMT hl7.fhir.us.carin-bb#0.1.0 # CARIN Alliance **_Enabling consumers and their authorized caregivers to access more of their digital health information with less friction._** This implementation guide describes the CARIN Blue Button&reg; Framework and Common Payer Consumer Data Set (CPCDS), providing a set of resources that payers can display to consumers via a FHIR API. See the [Table of Contents](toc.html) for more information. --- --- ### Latest Changes | Number | Description | | :---: | --- | | 60 | Added Balloter Notes to document the errors in QA.html and explain that these errors have been reviewed and were considered acceptable for going to ballot. | | 59 | A new html page was added to the IG to fix the broken Directory of Published version link which wasn't working because this is the first version of the IG to be published. | | 58 | The Request a Change link in the IG footer was fixed in Trifolia to take commenters to the new HL7 Jira site for tracking issues. | | 57 | Examples have been added and referenced from a new Examples Section. Additional examples will be developed and reviewed during the ballot reconciliation period to be included with the published IG. | | 56 | Search Parameters: Added a Search Parameters page to expose the developed SearchParameter Resources defined in this IG. A note to balloters was added to explain that Trifolia on FHIR is not rendering SearchParameter Resources correctly and reviewers need to use the XML or JSON tab to see the defintion. | | 55 | Notes to Balloters: A note to balloters was added to explain that the name of the IG has been changed. The formal HL7 title does not include the FHIR Accelerator Program name, nor does it use of a trademarked phrase. An acknowledgement was added to explain the IG will also be known as (aka) the Carin Blue Button IG. | | 54 | Notes to Balloters: A note to balloters was added to explain that certain Terminology naming issues will be addressed during the ballot process and will be resolved prior to publication in the following way: the Value Sets will be updated to remove reference to CARIN Blue Button, replaced by either industry standard names or, for those specific to claim adjudication, with the new IG name. Industry standard Code System revisions include consolidating the three Type of Bill Codes, removing reference to SNOMED CT, etc. Some value sets renaming has be started. The rest will be completed during ballot reconciliation. | | 53 | Note to Balloters: A note to balloters was added to explain that certain Code System referencing issues will be addressed during the ballot process and will be resolved prior to publication. Based on recent guidance from the HL7 Vocabulary Workgroup a change will be made to reference external licensed Code Systems using URIs instead of OIDs| | 52 | Capability Statements: The names of the Capability Statements were modified to align with the updated actor names. | | 51 | Profiles and Extensions: The MustSupport implementer guidance was added to the CARINBBExplanationOfBenefit Profile. A sentence was added to explain the Explanation of Benefit profiles inherit MustSupport guidance from the base profile. Search parameter guidance was added for the Coverage and Explanation of Benefit profile. | | 50 | Notes to Balloters: The Feedback section was modified to Notes to Balloters and comments were added requesting feedback on additional search parameters needed to support the use cases covered in this IG. An additional comment was added about Value Set and Codes System names noting they will be updated prior to publication and Terminology references. The note explains that they way Licensed Codes Systems and associated Value Sets are identified will be modified to incorporate recent changes in the way FHIR IGs specify external codes systems that HL7 is not licensed to incorporate into publications made available through HL7.org/FHIR | | 49 | Access to Licensed Code Systems: A new section under General Guidance, Access to Licensed Code Systems, was added. It will include guidance on how to access Licensed Industry Standard Code Systems and Available Industry Standard Code Systems. | | 48 | General Guidance: A section, General Guidance, was added to include guidance to support MustSupport for this IG, how to handle missing information. | | 47 | Use Case: A sequence flow diagram was added and the actor names in the descriptions were modified to align with the actor names used in the diagram. | | 46 | CARIN Blue Button Framework Specification: hotlinks were added to make the content it describes directly accessible without having to click through next page. | | 45 | Home Page, CARIN Alliance section: Formatting was resolved and additional verbiage was added to note that Blue Button is a registered mark of the U.S. Department of Health and Human Services. An attribution statement was made in the Acknowledgements to state, Blue Button, the slogan, Download My Data, the Blue Button Logo, and the Blue Button combined logo are registered service marks owned by the U.S. Department of Health and Human Services. | | 44 | Refined mapping page and added worksheet download link. Added initial profile desciptions and must support flags. | | 43 | The IG does not forbid any elements from base R4. Added &reg; symbol to Blue Button references to acknowledge CMS' registered mark. Reorganized the mapping sections. | | 42 | First pass at harmonization of profiles and terminologies. Added the **Authorization, Authentication, and Registration** section. | | 41 | set content to completed for code system [CARINBBClaimType](http://hl7.org/fhir/us/carin/CodeSystem/carin-bb-claim-type) | | 40 | Binding of value set [CARINBBClaimType](http://hl7.org/fhir/us/carin/ValueSet/carin-bb-claim-type) to eob.type in profile [CARINBBExplanationOfBenefit](http://hl7.org/fhir/us/carin/StructureDefinition/carin-bb-explanationofbenefit) | | 39 | Added new code allowedunits to [CARINBBAdjudicationCategory](http://hl7.org/fhir/us/carin/CodeSystem/carin-bb-adjudicationcategory) | | 38 | Added new code clmlastactiondate to [CARINBBClaimInformationCategory](http://hl7.org/fhir/us/carin/CodeSystem/carin-bb-claiminformationcategory) | | 37 | Updated Feedback section with Zulip stream information | | 36 | Added explicit "draft" verbiage | | 35 | Revised narrative content | | 34 | Removed Credits and added USCore Patient based CARINBBPatient profile | | 33 | Removed mapping page content and created new pages for Coverage, Patient, Comprehensive, and Data Index (to match spreadsheet); added content from spreadsheet to the pages | | 32 | Added 4 specific EOB and 1 Coverage profiles. | | 31 | Removed mapping pages for Claim, Claim LIne, Diagnosis, Procedure, Member and Coverage; removed 10 EOB profile stubs and replaced with 1 base profile | | 30 | Added pages to hold mappings for EOB Inpatient Facility, EOB Outpatient Facility, EOB Professional/Non-Clinician, and EOB Pharmacy | | 29 | Updated Provider and Claim Line Amounts mappings. | | 28 | Removed references to flat file format. Combined CPCDS format and mapping sections. Updated sample reverse mapping. | | 27 | Replaced 6 EOB profiles (one per claim type) with 10 EOB profiles (one per claim/subclaim type, flattened). Renamed things with new naming convention. | | 26 | Added sample of reverse mapping narrative for ExplanationOfBenefit. | | 25 | Added FHIR Resources section to narrative and included Example EOB. | | 24 | Replaced EOB profile with one EOB profile for each claim type. Added Business Rules page as a placeholder. | | 23 | Added the Latest Changes section. Added USCoreR4 Dependency. | ### Acknowledgements The Consumer-Directed Payer Data Exchange Implementation Guide is also known as the CARIN Blue Button&reg; Implementation Guide. Blue Button, the slogan, 'Download My Data,' the Blue Button Logo, and the Blue Button combined logo are registered service marks owned by the U.S. Department of Health and Human Services. --- >This implementation guide is currently a work in progress and is in draft status. > >Blue Button&reg; is a registered mark of HHS --- (built Mon, Dec 23, 2019 19:40+0000+00:00) http://hl7.org/fhir/us/carin-bb/2020Feb/package.tgz http://hl7.org/fhir/us/carin-bb/2020Feb/package.tgz HL7, Inc 4.0.1 IG Mon, 23 Dec 2019 12:00:00 +1100 GMT hl7.fhir.us.davinci-atr#0.1.0 Exchange of member attribution list between payers and providers (built Tue, Dec 24, 2019 01:00+0000+00:00) http://hl7.org/fhir/us/davinci-atr/2020Feb/package.tgz http://hl7.org/fhir/us/davinci-atr/2020Feb/package.tgz HL7, Inc 4.0.1 IG Mon, 23 Dec 2019 12:00:00 +1100 GMT hl7.fhir.us.carin-rtpbc#0.1.0 This is a guide for implementing the **consumer-focused real-time pharmacy benefit check** (consumer RTPBC) using FHIR R4. Using RTPBC, a patient can learn the cost and insurance coverage related to medications they've been prescribed. Specifically... * how a medication will be covered by their insurance, including out of pocket costs and any coverage restrictions or requirements that might apply * discount pricing available for the medication. Consumer RTPBC leverages the predetermination process supported by the Claim and ClaimResponse FHIR resources. Accompanying resources carry information that identifies the patient and their insurance coverage, prescription information and the preferred pharmacy (Patient, Coverage, MedicationRequest, Practitioner and Organization). OperationOutcome is used to communicate exceptions. The profile adapts terminology used in US pharmacy benefit processing, to minimize implementation obstacles for stakeholders who operate in that domain. <br/> *This guide is currently in development * <br/> ### Scope of this guide **Consumer RTPBC is intended to be used...** * in the United States (as it reflects unique US pharmacy insurance roles and conventions) * for medications that are covered under the *pharmacy benefit* portion of the patient's health insurance, which typically excludes medications administered during hospital care or as part of medical procedures * for commercially available medication products that are not compounded at the pharmacy. *(Support for compounds could potentially be added later)* ***Relationship to the NCPDP provider-focused RTPBC transactions*** <br/> This initial release of the consumer RTPBC profile seeks to include the coverage and cost information that's the most useful and meaningful to patients. As a result, certain content in the provider-centric NCPDP RTPBC standard is not included here. Additional content could potentially be added in a later effort. ***Related information flows outside of consumer RTPBC*** <br/> The patient application might gather related information before submitting the consumer RTPBC request, such as prescription information or insurance eligibility. *These exchanges are outside the scope of this guide.* <br> ### Feedback This implementation guide is the result of work sponsored by the CARIN Alliance, whose goal is to advance the ability for consumers and their authorized caregivers to easily get, use, and share their digital health information when, where, and how they want to achieve their goals. Comments and suggestions are welcome on our Zulip stream... https://chat.fhir.org/#narrow/stream/208660-CARIN-Benefit.20Check.20IG * or send a note to fm@frankmckinney.com <br/> ### Change log **0.1.10 (This version):** Added proposed coupon representation in Coverage resource (when request is processed by a discount pricing source). Added currency, state and country value set values in ClaimResponse, Patient and pharmacy Organization profiles. **0.1.09:** Added message definitions for the request and response. Added an Error Handling section in the Guidance menu, and placeholder 'error code' CodeSystem and ValueSet resources (to be refined/replaced after stakeholder discussion). **0.1.08:** Added discussion of submission/response using FHIR messaging to the Submission Method page (renamed from Submit Operation). Added examples of submission / response using messaging. Added an extension (isAlternative) to characterize ClaimResponse.addItem composites as independent alternative fulfillment options (based on feedback from the FM WG). Added a Security page under Guidance, to be further fleshed out through stakeholder discussion. **0.1.07:** Moved content illustration content to Examples section. (Changed name of Other menu item to Examples). Adjusted Submit Operation to remove the MessageHeader resource from the submitted Bundle, based on discussion with Financial Mgmt WG. Likewise adjusted the Bundle examples and illustrations. Clarified the high-level resource map illustration to match current approach. **0.1.06:** Added the Coverage resource into the request content illustration (inadvertently left it out earlier). **0.1.05:** Added MedicationRequest.reported as a Must Support element to indicate whether the prescription information is being reported by the patient or other source (versus being the actual original prescription resource). Added content illustrations to provide business-level discussion material. **0.1.04:** Addressed broken page links, made small profile adjustments in ClaimResponse. **0.1.03:** Added submit operation and parameter details. Added bundled version of request and response. Corrected version using Claim w/contained resources (for discussion). Added separate Patient, Coverage, MedicationRequest, Organization, MessageHeader example resources. **0.1.02 :** Loosened element cardinality restrictions in the Claim profile based on input from reviewers. General narrative cleanup. **0.1.01:** Adjusted background and use case material to also reflect RTPBC communication between the patient's application and discount medication pricing sources--which augments information retrieved from the patient's insurer. In process of reorganizing content to a more intuitive arrangement. **0.1.00:** Initial resources and narrative content. <br/> ### Known issues and to-dos * The example, rtpbc-claim-with-contained-03, omits the MedicationRequest; it is being lost when importing the resource to Trifolia. Trying to figure out... <br/> (built Fri, Dec 20, 2019 01:48+0000+00:00) http://hl7.org/fhir/us/carin-rtpbc/2020Feb/package.tgz http://hl7.org/fhir/us/carin-rtpbc/2020Feb/package.tgz HL7, Inc 4.0.1 IG Sun, 22 Dec 2019 12:00:00 +1100 GMT hl7.fhir.us.cqfmeasures#1.1.0 Measure content in support of the Clinical Reasoning Track at the Baltimore 2018 FHIR Connectathon (built Tue, Dec 24, 2019 00:29+0000+00:00) http://hl7.org/fhir/us/cqfmeasures/2020Feb/package.tgz http://hl7.org/fhir/us/cqfmeasures/2020Feb/package.tgz HL7, Inc 4.0.1 IG Sun, 22 Dec 2019 12:00:00 +1100 GMT hl7.fhir.us.davinci-alerts#0.2.0 http://hl7.org/fhir/us/davinci-alerts/2020Feb/package.tgz http://hl7.org/fhir/us/davinci-alerts/2020Feb/package.tgz HL7, Inc 4.0.1 IG Sun, 22 Dec 2019 12:00:00 +1100 GMT hl7.fhir.uv.genomics-reporting#1.0.0 Guidelines for reporting of clinical genomics results using HL7 FHIR (built Wed, Nov 20, 2019 11:44-0500-05:00) http://hl7.org/fhir/uv/genomics-reporting/STU1/package.tgz http://hl7.org/fhir/uv/genomics-reporting/STU1/package.tgz HL7, Inc 4.0.1 IG Wed, 20 Nov 2019 12:00:00 +1100 GMT hl7.fhir.us.core#3.1.0 http://hl7.org/fhir/us/core/STU3.1/package.tgz http://hl7.org/fhir/us/core/STU3.1/package.tgz HL7, Inc 4.0.1 IG Thu, 31 Oct 2019 12:00:00 +1100 GMT hl7.fhir.us.davinci-deqm#1.0.0 http://hl7.org/fhir/us/davinci-deqm/STU1/package.tgz http://hl7.org/fhir/us/davinci-deqm/STU1/package.tgz HL7, Inc 3.0.1 IG Thu, 31 Oct 2019 12:00:00 +1100 GMT hl7.fhir.r4.core#4.0.1 Definitions (API, structures and terminologies) for the R4 version of the FHIR standard http://hl7.org/fhir/R4/hl7.fhir.r4.core.tgz http://hl7.org/fhir/R4/hl7.fhir.r4.core.tgz HL7, Inc 4.0.1 fhir.core Wed, 30 Oct 2019 12:00:00 +1100 GMT hl7.fhir.r4.corexml#4.0.1 Definitions (API, structures and terminologies) for the R4 version of the FHIR standard http://hl7.org/fhir/R4/hl7.fhir.r4.corexml.tgz http://hl7.org/fhir/R4/hl7.fhir.r4.corexml.tgz HL7, Inc 4.0.1 fhir.core Wed, 30 Oct 2019 12:00:00 +1100 GMT hl7.fhir.r4.examples#4.0.1 Example resources in the R4 version of the FHIR standard http://hl7.org/fhir/R4/hl7.fhir.r4.examples.tgz http://hl7.org/fhir/R4/hl7.fhir.r4.examples.tgz HL7, Inc 4.0.1 fhir.core Wed, 30 Oct 2019 12:00:00 +1100 GMT hl7.fhir.r4.expansions#4.0.1 Expansions for the R4 version of the FHIR standard http://hl7.org/fhir/R4/hl7.fhir.r4.expansions.tgz http://hl7.org/fhir/R4/hl7.fhir.r4.expansions.tgz HL7, Inc 4.0.1 fhir.core Wed, 30 Oct 2019 12:00:00 +1100 GMT hl7.fhir.r4.elements#4.0.1 Element Definitions for types defined in the R4 version of the FHIR standard http://hl7.org/fhir/R4/hl7.fhir.r4.elements.tgz http://hl7.org/fhir/R4/hl7.fhir.r4.elements.tgz HL7, Inc 4.0.1 fhir.core Wed, 30 Oct 2019 12:00:00 +1100 GMT hl7.fhir.core#4.0.1 Group Wrapper that includes all the R4 packages http://hl7.org/fhir/R4/package.tgz http://hl7.org/fhir/R4/package.tgz HL7, Inc 4.0.1 fhir.core Wed, 30 Oct 2019 12:00:00 +1100 GMT hl7.fhir.us.cqfmeasures#1.0.0 Measure content in support of the Clinical Reasoning Track at the Baltimore 2018 FHIR Connectathon (built Wed, Nov 20, 2019 11:59-0500-05:00) http://hl7.org/fhir/us/cqfmeasures/STU1/package.tgz http://hl7.org/fhir/us/cqfmeasures/STU1/package.tgz HL7, Inc 3.0.2 IG Wed, 30 Oct 2019 12:00:00 +1100 GMT hl7.fhir.r3.core#3.0.2 Definitions (API, structures and terminologies) for the R3 version of the FHIR standard http://hl7.org/fhir/STU3/hl7.fhir.r3.core.tgz http://hl7.org/fhir/STU3/hl7.fhir.r3.core.tgz HL7, Inc 3.0.2 fhir.core Thu, 24 Oct 2019 12:00:00 +1100 GMT hl7.fhir.r3.corexml#3.0.2 Definitions (API, structures and terminologies) for the R3 version of the FHIR standard http://hl7.org/fhir/STU3/hl7.fhir.r3.corexml.tgz http://hl7.org/fhir/STU3/hl7.fhir.r3.corexml.tgz HL7, Inc 3.0.2 fhir.core Thu, 24 Oct 2019 12:00:00 +1100 GMT hl7.fhir.r3.examples#3.0.2 Example resources in the R3 version of the FHIR standard http://hl7.org/fhir/STU3/hl7.fhir.r3.examples.tgz http://hl7.org/fhir/STU3/hl7.fhir.r3.examples.tgz HL7, Inc 3.0.2 fhir.core Thu, 24 Oct 2019 12:00:00 +1100 GMT hl7.fhir.r3.expansions#3.0.2 Expansions for the R3 version of the FHIR standard http://hl7.org/fhir/STU3/hl7.fhir.r3.expansions.tgz http://hl7.org/fhir/STU3/hl7.fhir.r3.expansions.tgz HL7, Inc 3.0.2 fhir.core Thu, 24 Oct 2019 12:00:00 +1100 GMT hl7.fhir.r3.elements#3.0.2 Element Definitions for types defined in the R3 version of the FHIR standard http://hl7.org/fhir/STU3/hl7.fhir.r3.elements.tgz http://hl7.org/fhir/STU3/hl7.fhir.r3.elements.tgz HL7, Inc 3.0.2 fhir.core Thu, 24 Oct 2019 12:00:00 +1100 GMT hl7.fhir.core#3.0.2 Group Wrapper that includes all the R3 packages http://hl7.org/fhir/STU3/package.tgz http://hl7.org/fhir/STU3/package.tgz HL7, Inc 3.0.2 fhir.core Thu, 24 Oct 2019 12:00:00 +1100 GMT hl7.fhir.us.davinci-pdex-plan-net#0.1.0 http://hl7.org/fhir/us/davinci-pdex-plan-net/2020Feb/package.tgz http://hl7.org/fhir/us/davinci-pdex-plan-net/2020Feb/package.tgz HL7, Inc 4.0.0 IG Thu, 24 Oct 2019 12:00:00 +1100 GMT hl7.fhir.us.hai#2.0.0 http://hl7.org/fhir/us/hai/STU2/package.tgz http://hl7.org/fhir/us/hai/STU2/package.tgz HL7, Inc 4.0.0 IG Fri, 11 Oct 2019 12:00:00 +1100 GMT hl7.fhir.us.breast-radiology#0.1.0 http://hl7.org/fhir/us/breast-radiology/2019Sep/package.tgz http://hl7.org/fhir/us/breast-radiology/2019Sep/package.tgz HL7, Inc 4.0.0 IG Mon, 30 Sep 2019 12:00:00 +1000 GMT hl7.fhir.us.eltss#1.0.0 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 Thu, Sep 12, 2019 12:55-0400-04:00) http://hl7.org/fhir/us/eltss/STU1/package.tgz http://hl7.org/fhir/us/eltss/STU1/package.tgz HL7, Inc 4.0.0 IG Thu, 12 Sep 2019 12:00:00 +1000 GMT hl7.fhir.us.core#3.0.1 http://hl7.org/fhir/us/core/2019Sep/package.tgz http://hl7.org/fhir/us/core/2019Sep/package.tgz HL7, Inc 4.0.0 IG Sun, 01 Sep 2019 12:00:00 +1000 GMT hl7.fhir.uv.bulkdata#1.0.0 http://hl7.org/fhir/uv/bulkdata/STU1/package.tgz http://hl7.org/fhir/uv/bulkdata/STU1/package.tgz HL7, Inc 4.0.0 IG Thu, 22 Aug 2019 12:00:00 +1000 GMT hl7.fhir.us.davinci-pcde#0.1.0 Guidelines for conveying coverage information from one payer to another when a patient changes insurance (built Fri, Aug 2, 2019 13:52-0400-04:00) http://hl7.org/fhir/us/davinci-pcde/2019Sep/package.tgz http://hl7.org/fhir/us/davinci-pcde/2019Sep/package.tgz HL7, Inc 4.0.0 IG Fri, 09 Aug 2019 12:00:00 +1000 GMT hl7.fhir.us.davinci-dtr#0.2.0 Guidelines for documentation templates and rules for coverage requirements (built Tue, Aug 6, 2019 12:57-0400-04:00) http://hl7.org/fhir/us/davinci-dtr/2019Sep/package.tgz http://hl7.org/fhir/us/davinci-dtr/2019Sep/package.tgz HL7, Inc 4.0.0 IG Tue, 06 Aug 2019 12:00:00 +1000 GMT hl7.fhir.us.qicore#3.3.0 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 Tue, Aug 6, 2019 11:43-0400-04:00) http://hl7.org/fhir/us/qicore/2019Sep/package.tgz http://hl7.org/fhir/us/qicore/2019Sep/package.tgz HL7, Inc 4.0.0 IG Tue, 06 Aug 2019 12:00:00 +1000 GMT hl7.fhir.uv.ips#0.3.0 http://hl7.org/fhir/uv/ips/2019Sep/package.tgz http://hl7.org/fhir/uv/ips/2019Sep/package.tgz HL7, Inc 4.0.0 IG Tue, 06 Aug 2019 12:00:00 +1000 GMT hl7.fhir.uv.livd#0.2.0 Recommended LOINC mappings for IVD Devices (built Tue, Aug 6, 2019 14:35-0400-04:00) http://hl7.org/fhir/uv/livd/2019Sep/package.tgz http://hl7.org/fhir/uv/livd/2019Sep/package.tgz HL7, Inc 4.0.0 IG Tue, 06 Aug 2019 12:00:00 +1000 GMT hl7.fhir.us.davinci-pas#0.1.0 Guidelines for conveying coverage requirements to clinicians when planning treatment (built Mon, Aug 5, 2019 11:50-0400-04:00) http://hl7.org/fhir/us/davinci-pas/2019Sep/package.tgz http://hl7.org/fhir/us/davinci-pas/2019Sep/package.tgz HL7, Inc 4.0.0 IG Mon, 05 Aug 2019 12:00:00 +1000 GMT hl7.fhir.uv.cpg#0.1.0 Implementation guidance for creating Clinical Practice Guidelines with formal artifacts to facilitate sharing and implementation of the guideline (built Mon, Aug 5, 2019 12:02-0400-04:00) http://hl7.org/fhir/uv/cpg/2019Sep/package.tgz http://hl7.org/fhir/uv/cpg/2019Sep/package.tgz HL7, Inc 4.0.0 IG Sun, 04 Aug 2019 12:00:00 +1000 GMT hl7.fhir.us.hai-ltcf#0.1.0 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. As reports are modified and new report types are defined, CDC and Health Level Seven (HL7) will develop and publish additional constraints. Throughout 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. Note 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 Thu, Aug 1, 2019 08:55-0400-04:00) http://hl7.org/fhir/us/hai-ltcf/2019Sep/package.tgz http://hl7.org/fhir/us/hai-ltcf/2019Sep/package.tgz HL7, Inc 4.0.0 IG Thu, 01 Aug 2019 12:00:00 +1000 GMT hl7.fhir.us.immds#0.2.0 http://hl7.org/fhir/uv/immds/2019Sep/package.tgz http://hl7.org/fhir/uv/immds/2019Sep/package.tgz HL7, Inc 4.0.0 IG Mon, 29 Jul 2019 12:00:00 +1000 GMT hl7.fhir.uv.immds#0.2.0 http://hl7.org/fhir/uv/immds/2019Sep/package.tgz http://hl7.org/fhir/uv/immds/2019Sep/package.tgz HL7, Inc 4.0.0 IG Mon, 29 Jul 2019 12:00:00 +1000 GMT hl7.fhir.us.meds#1.2.0 http://hl7.org/fhir/us/meds/STU2/package.tgz http://hl7.org/fhir/us/meds/STU2/package.tgz HL7, Inc 3.0.1 IG Thu, 25 Jul 2019 12:00:00 +1000 GMT hl7.fhir.uv.cdisc-lab#0.1.0 http://hl7.org/fhir/uv/cdisc-lab/2019Sep/package.tgz http://hl7.org/fhir/uv/cdisc-lab/2019Sep/package.tgz HL7, Inc 4.0.1 IG Fri, 12 Jul 2019 12:00:00 +1000 GMT hl7.fhir.us.davinci-cdex#0.1.0 The CDex implementation guide defines combinations of exchange methods (push, pull, etc. ), specific payloads (Documents, Bundles, and Individual Resources), search criteria, conformance, provenance, and other relevant requirements to support the exchange of clinical information between provider and other providers and/or payers. The goal is to identify, document and constrain specific exchange patterns so that providers and payers can reliably exchange information for patient care (including coordination of care), risk adjustment, quality reporting, identifying that requested services are necessary and appropriate (e.g. should be covered by the payer) and other uses that may be documented as part of this effort. Clinical data payloads will include C-CDA, C-CDA on FHIR, compositions, bundles, and discrete resources conforming to the US Core specification. Ultimately this IG is expected to support multiple versions of FHIR (DSTU2/Argonaught, STU3, and R4), but the current version of this IG only supports for FHIR R4. The implementation guide is organized into the following major sections: * **[Introduction](Introduction.html)**: describes the HL7 FHIR standard, and explains the content covered in this implementation guide (IG) and how it is organized to help payers understand how to access and use the specification. It also identifies other supporting specifications that are utilized to address the use cases covered in this IG. * **[Use Cases, Personas and Patient Story](Use_Cases,_Personas_and_Patient_Story.html)**: describes specific information exchange scenarios that are covered by the CDex IG and demonstrates steps and information exchange mechanisms employed to accomplish the data exchange required for each use case. Each use case includes one or more variants to demonstrate different exchange interactions that may be used to accomplish the information sharing objective of the use case. Each use case variant defines the technical roles (actors) played by systems involved in the information exchange, explains the steps involved with any preconditions or post conditions defined, and provides a sequence diagram illustration to show the flow of information in the exchange. * **[CDex Profiles and Extensions](CDex_Profiles_and_Extensions.html)**: introduces and provides links to the supported profiles, search parameters and other FHIR artifacts used in this implementation guide as well as in the [Health Record Exchange IG](http://hl7.org/fhir/us/davinci-hrex/). It provides the technical conformance details for profiles that are defined within and used only by the CDex IG. * **[Information Exchange Interactions and Specifications](Information_Exchange_Interactions_and_Specifications.html)**: describes how each information exchange interaction is implemented in FHIR. Readers will be directed to reference documentation in the HRex IG for information about interactions fully defined in that guide. * **[Credits](Credits.html)**: identifies the individuals and organizations involved in developing this implementation guide (built Thu, Jun 20, 2019 16:38-0400-04:00) http://hl7.org/fhir/us/davinci-cdex/2019Jun/package.tgz http://hl7.org/fhir/us/davinci-cdex/2019Jun/package.tgz HL7, Inc 4.0.0 IG Thu, 20 Jun 2019 12:00:00 +1000 GMT hl7.fhir.us.davinci-hrex#0.1.0 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. Da 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. The 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 were appropriate. In addition, exchanges from payer systems to providers, other payers, and third-party applications are supported by the HRex profiles and operations. HRex 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 Thu, Jun 20, 2019 08:10-0400-04:00) http://hl7.org/fhir/us/davinci-hrex/2019Jun/package.tgz http://hl7.org/fhir/us/davinci-hrex/2019Jun/package.tgz HL7, Inc 4.0.0 IG Thu, 20 Jun 2019 12:00:00 +1000 GMT hl7.fhir.us.davinci-pdex#0.1.0 This specification is currently undergoing ballot and connectathon testing. It is expected to evolve, possibly significantly, as part of that process. Feedback is welcome and may be submitted through the FHIR gForge tracker indicating US Da Vinci PDex as the specification. If balloting on this IG, please submit your comments via the tracker and just reference them in your ballot submission implementation guide. [Financial Management](https://confluence.hl7.org/display/FM/Financial+Management+Home) is the Sponsoring Work Group for this Implementation Guide. **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 Profiles based on FHIR R4) which can be understood by providers and, if they choose to, committed to their Electronic Medical Records (EMR) System.** This IG uses the same Member Health History "payload" for member-authorized exchange of information with other Health Plans and with Third-Party Applications. It describes the interaction patters that, when followed, allow the various parties involved in managing healthcare and payer data to more easily integrate and exchange data securely and effectively. This IG covers the exchange of: - Claims-based information - Clinical Information (such as Lab Results, Allergies and Conditions) This 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. This IG covers the exchange of a Member's Health History in the following scenarios: - Provider requested Provider-Health Plan Exchange using CDS-Hooks and SMART-on-FHIR - Member-authorized Health Plan to Health Plan exchange - Member-authorized Health Plan to Third-Party Application exchange The latter two scenarios are provided to meet the requirements identified in the CMS Interoperability Notice for Proposed Rule Making issued on February 11, 2019. **There are items in this guide that are subject to update**. This includes: - Value Sets - Vocabularies (X12, NUBC etc.) - Examples **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). See the [Table of Contents](toc.html) for more information. #### Latest Changes - (283) rebuild to test broken CI process - (280) fix more links - (275) fix links - (274) Change Business Version to 0.1.0, Change navigation links - (271) Change Business Version to 1.0.0 - (270) reformat section 2-1 - (269) Fix corrupted section 2-1 - (266) Add remaining previous/next links to narrative - (255) Adding Previous / Next Page Links to narrative thru section 3 - (254) Add CDS Hooks Justification, revisions per review comments. - (245) Add section 4-8 sub-content links - (243) Add FM as sponsoring workgroup to description (built Thu, Jun 20, 2019 13:45-0400-04:00) http://hl7.org/fhir/us/davinci-pdex/2019Jun/package.tgz http://hl7.org/fhir/us/davinci-pdex/2019Jun/package.tgz HL7, Inc 4.0.0 IG Thu, 20 Jun 2019 12:00:00 +1000 GMT hl7.fhir.us.davinci-drug-formulary#0.1.0 http://hl7.org/fhir/us/davinci-drug-formulary/Jun2019/package.tgz http://hl7.org/fhir/us/davinci-drug-formulary/Jun2019/package.tgz HL7, Inc 4.0.1 IG Tue, 18 Jun 2019 12:00:00 +1000 GMT hl7.fhir.us.core#3.0.0 http://hl7.org/fhir/us/core/STU3/package.tgz http://hl7.org/fhir/us/core/STU3/package.tgz HL7, Inc 4.0.0 IG Sat, 15 Jun 2019 12:00:00 +1000 GMT hl7.fhir.us.mcode#0.9.1 http://hl7.org/fhir/us/mcode/2019Sep/package.tgz http://hl7.org/fhir/us/mcode/2019Sep/package.tgz HL7, Inc 4.0.0 IG Mon, 10 Jun 2019 12:00:00 +1000 GMT hl7.fhir.us.cqfmeasures#0.1.0 Measure content in support of the Clinical Reasoning Track at the Baltimore 2018 FHIR Connectathon (built Wed, Mar 27, 2019 07:31+1100+11:00) http://hl7.org/fhir/us/cqfmeasures/2019May/package.tgz http://hl7.org/fhir/us/cqfmeasures/2019May/package.tgz HL7, Inc 3.0.1 IG Wed, 01 May 2019 12:00:00 +1000 GMT hl7.fhir.us.davinci-dtr#0.1.0 Guidelines for documentation templates and rules for coverage requirements (built Wed, Mar 27, 2019 07:35+1100+11:00) http://hl7.org/fhir/us/davinci-dtr/2019May/package.tgz http://hl7.org/fhir/us/davinci-dtr/2019May/package.tgz HL7, Inc 3.0.1 IG Wed, 01 May 2019 12:00:00 +1000 GMT hl7.fhir.us.qicore#3.2.0 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 Sun, Apr 14, 2019 21:07+1000+10:00) http://hl7.org/fhir/us/qicore/STU32/package.tgz http://hl7.org/fhir/us/qicore/STU32/package.tgz HL7, Inc 3.0.1 IG Sun, 14 Apr 2019 12:00:00 +1000 GMT hl7.fhir.uv.sdc#2.7.0 The SDC specification provides an infrastructure to standardize the capture and expanded use of patient-level data collected within an EHR.<br/>This includes two components:<br/>* Support more sophisticated questionnaire/form use-cases such as those needed for research, oncology, pathology and other clinical domains.<br/>*Support pre-population and auto-population of EHR data into forms/questionnaires for uses outside direct clinical care (patient safety, adverse event reporting, public health reporting, etc.). (built Wed, Mar 27, 2019 07:27+1100+11:00) http://hl7.org/fhir/uv/sdc/2019May/package.tgz http://hl7.org/fhir/uv/sdc/2019May/package.tgz HL7, Inc 4.0.0 IG Fri, 29 Mar 2019 12:00:00 +1100 GMT hl7.fhir.us.bulkdata#0.1.0 http://hl7.org/fhir/us/bulkdata/2019May/package.tgz http://hl7.org/fhir/us/bulkdata/2019May/package.tgz HL7, Inc 4.0.0 IG Wed, 27 Mar 2019 12:00:00 +1100 GMT hl7.fhir.us.davinci-crd#0.3.0 Guidelines for conveying coverage requirements to clinicians when planning treatment (built Wed, Mar 27, 2019 08:37+1100+11:00) http://hl7.org/fhir/us/davinci-crd/2019May/package.tgz http://hl7.org/fhir/us/davinci-crd/2019May/package.tgz HL7, Inc 4.0.0 IG Wed, 27 Mar 2019 12:00:00 +1100 GMT hl7.fhir.us.davinci-deqm#0.2.0 http://hl7.org/fhir/us/davinci-deqm/2019May/package.tgz http://hl7.org/fhir/us/davinci-deqm/2019May/package.tgz HL7, Inc 3.0.1 IG Wed, 27 Mar 2019 12:00:00 +1100 GMT hl7.fhir.us.eltss#0.1.0 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 Wed, Mar 27, 2019 07:36+1100+11:00) http://hl7.org/fhir/us/eltss/2019May/package.tgz http://hl7.org/fhir/us/eltss/2019May/package.tgz HL7, Inc 4.0.0 IG Wed, 27 Mar 2019 12:00:00 +1100 GMT hl7.fhir.us.hai#1.1.0 This implementation guide (IG) is to 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. As reports are modified and new report types are defined, CDC and Health Level Seven (HL7) will develop and publish additional constraints. Throughout 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. Note 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, Mar 27, 2019 07:21+1100+11:00) http://hl7.org/fhir/us/hai/2019May/package.tgz http://hl7.org/fhir/us/hai/2019May/package.tgz HL7, Inc 3.0.1 IG Wed, 27 Mar 2019 12:00:00 +1100 GMT hl7.fhir.us.patient-reported-outcomes#0.2.0 http://hl7.org/fhir/us/patient-reported-outcomes/2019May/package.tgz http://hl7.org/fhir/us/patient-reported-outcomes/2019May/package.tgz HL7, Inc 4.0.0 IG Wed, 27 Mar 2019 12:00:00 +1100 GMT hl7.fhir.us.phcp#0.2.0 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. This guide contains a library of Fast Health Interoperability Resources (FHIR) profiles, and is compliant with the C-CDA on FHIR specification (built Wed, Mar 27, 2019 07:23+1100+11:00) http://hl7.org/fhir/us/phcp/2019May/package.tgz http://hl7.org/fhir/us/phcp/2019May/package.tgz HL7, Inc 3.1.0 IG Wed, 27 Mar 2019 12:00:00 +1100 GMT hl7.fhir.us.womens-health-registries#0.2.0 http://hl7.org/fhir/us/womens-health-registries/2019May/package.tgz http://hl7.org/fhir/us/womens-health-registries/2019May/package.tgz HL7, Inc 4.0.0 IG Wed, 27 Mar 2019 12:00:00 +1100 GMT hl7.fhir.uv.phd#0.3.0 ImplementationGuide for Personal Health Devices (PHD), used in remote patient monitoring (e.g., weight scales, blood pressure cuffs, glucose monitors, pulse-oximeters, etc.). (built Wed, Mar 27, 2019 07:25+1100+11:00) http://hl7.org/fhir/uv/phd/2019May/package.tgz http://hl7.org/fhir/uv/phd/2019May/package.tgz HL7, Inc 4.0.0 IG Wed, 27 Mar 2019 12:00:00 +1100 GMT hl7.fhir.us.breast-radiology#0.2.0 Breast Radiology Reporting Implementation Guide (built Tue, Apr 7, 2020 16:39+0000+00:00) http://hl7.org/fhir/us/breast-radiology/2020May/package.tgz http://hl7.org/fhir/us/breast-radiology/2020May/package.tgz HL7, Inc 4.0.1 IG Mon, 25 Mar 2019 12:00:00 +1100 GMT hl7.fhir.us.bser#0.2.0 The BSeR FHIR implementation guide provides guidance for using the HL7 Fast Healthcare Interoperability Resources (FHIR) standard as an exchange format for Bidirectional Services eReferral (BSeR). It is a collection of FHIR resource profiles design for use in information exchanges supporting service provider referral and service outcome reporting. A key concept adopted in the design of the BSeR FHIR Profiles is the concept of parsimony. Program area referral and feedback transactions contain common transaction data and program specific data. A critical design requirement is to limit the exchange of clinical information to program areas to only that data that pertain to the program. Transaction participant data such as Patient, Referring Provider, and Servicing Provider are common to both referral and feedback transactions. The data content of each transaction type is partitioned into common and program specific data items. Some program specific data items pertain to multiple program areas; others are specific to a single subject area. (built Wed, Mar 27, 2019 07:29+1100+11:00) http://hl7.org/fhir/us/bser/2019May/package.tgz http://hl7.org/fhir/us/bser/2019May/package.tgz HL7, Inc 3.0.1 IG Thu, 21 Mar 2019 12:00:00 +1100 GMT hl7.fhir.us.vrdr#0.1.0 The purpose of the VRDR FHIR IG is to provide guidance regarding the use of FHIR resources as a conduit for data required in the bidirectional exchange of mortality data between State-run Public Health Agencies (PHA) Vital Records offices and U.S. National Center for Health Statistics (NCHS). (built Wed, Mar 27, 2019 07:24+1100+11:00) http://hl7.org/fhir/us/vrdr/2019May/package.tgz http://hl7.org/fhir/us/vrdr/2019May/package.tgz HL7, Inc 3.0.1 IG Thu, 21 Mar 2019 12:00:00 +1100 GMT hl7.fhir.us.hai#1.0.0 http://hl7.org/fhir/us/hai/STU1/package.tgz http://hl7.org/fhir/us/hai/STU1/package.tgz HL7, Inc 3.0.1 IG Fri, 08 Mar 2019 12:00:00 +1100 GMT hl7.fhir.us.core#2.1.0 http://hl7.org/fhir/us/core/2019Jan/package.tgz http://hl7.org/fhir/us/core/2019Jan/package.tgz HL7, Inc 4.0.0 IG Tue, 04 Dec 2018 12:00:00 +1100 GMT hl7.fhir.us.core#2.0.0 http://hl7.org/fhir/us/core/STU2/package.tgz http://hl7.org/fhir/us/core/STU2/package.tgz HL7, Inc 3.0.1 IG Tue, 04 Dec 2018 12:00:00 +1100 GMT hl7.fhir.uv.genomics-reporting#0.3.0 http://hl7.org/fhir/uv/genomics-reporting/2019Jan/package.tgz http://hl7.org/fhir/uv/genomics-reporting/2019Jan/package.tgz HL7, Inc 4.0.0 IG Tue, 04 Dec 2018 12:00:00 +1100 GMT hl7.fhir.uv.phd#0.2.0 http://hl7.org/fhir/uv/phd/2019Jan/package.tgz http://hl7.org/fhir/uv/phd/2019Jan/package.tgz HL7, Inc 4.0.0 IG Tue, 04 Dec 2018 12:00:00 +1100 GMT hl7.fhir.uv.smart-app-launch#1.0.0 http://hl7.org/fhir/smart-app-launch/1.0.0/package.tgz http://hl7.org/fhir/smart-app-launch/1.0.0/package.tgz HL7, Inc 3.0.1 IG Tue, 13 Nov 2018 12:00:00 +1100 GMT hl7.fhir.us.davinci-crd#0.1.0 Guidelines for conveying coverage requirements to clinicians when planning treatment http://hl7.org/fhir/us/davinci-crd/2018Sep/package.tgz http://hl7.org/fhir/us/davinci-crd/2018Sep/package.tgz HL7, Inc 3.5.0 IG Sat, 01 Sep 2018 12:00:00 +1000 GMT hl7.fhir.us.davinci-deqm#0.1.0 http://hl7.org/fhir/us/davinci-deqm/2018Sep/package.tgz http://hl7.org/fhir/us/davinci-deqm/2018Sep/package.tgz HL7, Inc 3.0.1|3.5.0 IG Sat, 01 Sep 2018 12:00:00 +1000 GMT hl7.fhir.us.odh#0.1.0 http://hl7.org/fhir/us/odh/2018Sep/package.tgz http://hl7.org/fhir/us/odh/2018Sep/package.tgz HL7, Inc 3.0.1 IG Sat, 01 Sep 2018 12:00:00 +1000 GMT hl7.fhir.us.patient-reported-outcomes#0.1.0 http://hl7.org/fhir/us/patient-reported-outcomes/2018Sep/package.tgz http://hl7.org/fhir/us/patient-reported-outcomes/2018Sep/package.tgz HL7, Inc 3.5.0 IG Sat, 01 Sep 2018 12:00:00 +1000 GMT hl7.fhir.us.womens-health-registries#0.1.0 http://hl7.org/fhir/us/womens-health-registries/2018Sep/package.tgz http://hl7.org/fhir/us/womens-health-registries/2018Sep/package.tgz HL7, Inc 3.5.0 IG Sat, 01 Sep 2018 12:00:00 +1000 GMT hl7.fhir.uv.livd#0.1.0 Recommended LOINC mappings for IVD Devices http://hl7.org/fhir/uv/livd/2018Sep/package.tgz http://hl7.org/fhir/uv/livd/2018Sep/package.tgz HL7, Inc 3.5.0 IG Sat, 01 Sep 2018 12:00:00 +1000 GMT hl7.fhir.uv.pddi#0.1.0 http://hl7.org/fhir/uv/pddi/2018Sep/package.tgz http://hl7.org/fhir/uv/pddi/2018Sep/package.tgz HL7, Inc 3.5.0 IG Sat, 01 Sep 2018 12:00:00 +1000 GMT hl7.fhir.uv.pocd#0.2.0 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.). http://hl7.org/fhir/uv/pocd/2018Sep/package.tgz http://hl7.org/fhir/uv/pocd/2018Sep/package.tgz HL7, Inc 3.5.0 IG Sat, 01 Sep 2018 12:00:00 +1000 GMT hl7.fhir.uv.vhdir#0.2.0 http://hl7.org/fhir/uv/vhdir/2018Sep/package.tgz http://hl7.org/fhir/uv/vhdir/2018Sep/package.tgz HL7, Inc 3.5.0 IG Sat, 01 Sep 2018 12:00:00 +1000 GMT hl7.fhir.us.breastcancer#0.2.0 http://hl7.org/fhir/us/breastcancer/2018Sep/package.tgz http://hl7.org/fhir/us/breastcancer/2018Sep/package.tgz HL7, Inc 3.0.1 IG Fri, 31 Aug 2018 12:00:00 +1000 GMT hl7.fhir.uv.sdc#2.5.0 The SDC specification provides an infrastructure to standardize the capture and expanded use of patient-level data collected within an EHR.<br/>This includes two components:<br/>* Support more sophisticated questionnaire/form use-cases such as those needed for research, oncology, pathology and other clinical domains.<br/>*Support pre-population and auto-population of EHR data into forms/questionnaires for uses outside direct clinical care (patient safety, adverse event reporting, public health reporting, etc.). http://hl7.org/fhir/uv/sdc/2018Sep/package.tgz http://hl7.org/fhir/uv/sdc/2018Sep/package.tgz HL7, Inc 3.5.0 IG Fri, 31 Aug 2018 12:00:00 +1000 GMT hl7.fhir.core#3.5.0 FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification http://hl7.org/fhir/2018Sep/package.tgz http://hl7.org/fhir/2018Sep/package.tgz HL7, Inc 3.5.0 fhir.core Tue, 21 Aug 2018 12:00:00 +1000 GMT hl7.fhir.us.ecr#0.2.0 http://hl7.org/fhir/us/ecr/2018Sep/package.tgz http://hl7.org/fhir/us/ecr/2018Sep/package.tgz HL7, Inc 3.0.2 IG Tue, 21 Aug 2018 12:00:00 +1000 GMT hl7.fhir.us.ecr#0.2.0 http://hl7.org/fhir/us/ecr/2018Sep/package.tgz http://hl7.org/fhir/us/ecr/2018Sep/package.tgz HL7, Inc 3.0.2 IG Tue, 21 Aug 2018 12:00:00 +1000 GMT hl7.fhir.us.qicore#3.1.0 http://hl7.org/fhir/us/qicore/STU3/package.tgz http://hl7.org/fhir/us/qicore/STU3/package.tgz HL7, Inc 3.0.1 IG Tue, 21 Aug 2018 12:00:00 +1000 GMT hl7.fhir.uv.ips#0.2.0 http://hl7.org/fhir/uv/ips/2018Sep/package.tgz http://hl7.org/fhir/uv/ips/2018Sep/package.tgz HL7, Inc 3.5.0 IG Tue, 21 Aug 2018 12:00:00 +1000 GMT hl7.fhir.us.bser#0.1.0 The BSeR FHIR implementation guide provides guidance for using the HL7 Fast Healthcare Interoperability Resources (FHIR) standard as an exchange format for Bidirectional Services eReferral (BSeR). It is a collection of FHIR resource profiles design for use in information exchanges supporting service provider referral and service outcome reporting. A key concept adopted in the design of the BSeR FHIR Profiles is the concept of parsimony. Program area referral and feedback transactions contain common transaction data and program specific data. A critical design requirement is to limit the exchange of clinical information to program areas to only that data that pertain to the program. Transaction participant data such as Patient, Referring Provider, and Servicing Provider are common to both referral and feedback transactions. The data content of each transaction type is partitioned into common and program specific data items. Some program specific data items pertain to multiple program areas; others are specific to a single subject area. http://hl7.org/fhir/us/bser/2018Sep/package.tgz http://hl7.org/fhir/us/bser/2018Sep/package.tgz HL7, Inc 3.0.1 IG Fri, 17 Aug 2018 12:00:00 +1000 GMT hl7.fhir.us.ccda#1.0.0 http://hl7.org/fhir/us/ccda/STU1/package.tgz http://hl7.org/fhir/us/ccda/STU1/package.tgz HL7, Inc 3.0.1 IG Sat, 07 Apr 2018 12:00:00 +1000 GMT hl7.fhir.us.breastcancer#0.1.0 http://hl7.org/fhir/us/breastcancer/2018May/package.tgz http://hl7.org/fhir/us/breastcancer/2018May/package.tgz HL7, Inc 3.0.1 IG Wed, 04 Apr 2018 12:00:00 +1000 GMT hl7.fhir.us.hai#0.1.0 http://hl7.org/fhir/us/hai/2018May/package.tgz http://hl7.org/fhir/us/hai/2018May/package.tgz HL7, Inc 3.3.0 IG Wed, 04 Apr 2018 12:00:00 +1000 GMT hl7.fhir.us.meds#1.1.0 http://hl7.org/fhir/us/meds/2018May/package.tgz http://hl7.org/fhir/us/meds/2018May/package.tgz HL7, Inc 3.0.1 IG Wed, 04 Apr 2018 12:00:00 +1000 GMT hl7.fhir.uv.genomics-reporting#0.1.0 Guidelines for reporting of clinical genomics results using HL7 FHIR http://hl7.org/fhir/uv/genomics-reporting/2018May/package.tgz http://hl7.org/fhir/uv/genomics-reporting/2018May/package.tgz HL7, Inc 3.3.0 IG Wed, 04 Apr 2018 12:00:00 +1000 GMT hl7.fhir.uv.ips#0.1.0 http://hl7.org/fhir/uv/ips/2018May/package.tgz http://hl7.org/fhir/uv/ips/2018May/package.tgz HL7, Inc 3.0.1 IG Wed, 04 Apr 2018 12:00:00 +1000 GMT hl7.fhir.core#3.2.0 FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification http://hl7.org/fhir/2018Jan/package.tgz http://hl7.org/fhir/2018Jan/package.tgz HL7, Inc 3.2.0 fhir.core Mon, 02 Apr 2018 12:00:00 +1000 GMT hl7.fhir.us.cdmh#0.1.0 http://hl7.org/fhir/us/cdmh/2019May/package.tgz http://hl7.org/fhir/us/cdmh/2019May/package.tgz HL7, Inc 4.0.0 IG Mon, 02 Apr 2018 12:00:00 +1000 GMT hl7.fhir.us.immds#0.1.0 http://hl7.org/fhir/uv/immds/2018Jan/package.tgz http://hl7.org/fhir/uv/immds/2018Jan/package.tgz HL7, Inc 3.0.1 IG Mon, 01 Jan 2018 12:00:00 +1100 GMT hl7.fhir.uv.immds#0.1.0 http://hl7.org/fhir/uv/immds/2018Jan/package.tgz http://hl7.org/fhir/uv/immds/2018Jan/package.tgz HL7, Inc 3.0.1 IG Mon, 01 Jan 2018 12:00:00 +1100 GMT hl7.fhir.uv.phd#0.1.0 http://hl7.org/fhir/uv/phd/2018Jan/package.tgz http://hl7.org/fhir/uv/phd/2018Jan/package.tgz HL7, Inc 3.0.0 IG Mon, 01 Jan 2018 12:00:00 +1100 GMT hl7.fhir.uv.pocd#0.1.0 http://hl7.org/fhir/uv/pocd/2018Jan/package.tgz http://hl7.org/fhir/uv/pocd/2018Jan/package.tgz HL7, Inc 3.0.0 IG Mon, 01 Jan 2018 12:00:00 +1100 GMT hl7.fhir.uv.vhdir#0.1.0 http://hl7.org/fhir/uv/vhdir/2018Jan/package.tgz http://hl7.org/fhir/uv/vhdir/2018Jan/package.tgz HL7, Inc 3.2.0 IG Mon, 01 Jan 2018 12:00:00 +1100 GMT hl7.fhir.us.core#1.1.0 http://hl7.org/fhir/us/core/2018Jan/package.tgz http://hl7.org/fhir/us/core/2018Jan/package.tgz HL7, Inc 3.0.1 IG Wed, 20 Dec 2017 12:00:00 +1100 GMT hl7.fhir.us.ecr#0.1.0 http://hl7.org/fhir/uv/ecr/2018Jan/package.tgz http://hl7.org/fhir/uv/ecr/2018Jan/package.tgz HL7, Inc 3.0.2 IG Wed, 20 Dec 2017 12:00:00 +1100 GMT hl7.fhir.us.ecr#0.1.0 http://hl7.org/fhir/uv/ecr/2018Jan/package.tgz http://hl7.org/fhir/uv/ecr/2018Jan/package.tgz HL7, Inc 3.0.2 IG Wed, 20 Dec 2017 12:00:00 +1100 GMT hl7.fhir.us.qicore#2.1.0 http://hl7.org/fhir/us/qicore/2018Jan/package.tgz http://hl7.org/fhir/us/qicore/2018Jan/package.tgz HL7, Inc 3.0.1 IG Wed, 20 Dec 2017 12:00:00 +1100 GMT hl7.fhir.us.qicore#2.0.0 http://hl7.org/fhir/us/qicore/STU2/package.tgz http://hl7.org/fhir/us/qicore/STU2/package.tgz HL7, Inc 3.0.1 IG Tue, 12 Dec 2017 12:00:00 +1100 GMT hl7.fhir.us.core#1.0.1 http://hl7.org/fhir/us/core/1.0.1/package.tgz http://hl7.org/fhir/us/core/1.0.1/package.tgz HL7, Inc 3.0.1 IG Thu, 02 Nov 2017 12:00:00 +1100 GMT hl7.fhir.us.phcp#0.1.0 http://hl7.org/fhir/us/phcp/2017Sep/package.tgz http://hl7.org/fhir/us/phcp/2017Sep/package.tgz HL7, Inc 3.1.0 IG Sun, 30 Jul 2017 12:00:00 +1000 GMT hl7.fhir.uv.smart-app-launch#0.8.0 http://hl7.org/fhir/smart-app-launch/0.8.0/package.tgz http://hl7.org/fhir/smart-app-launch/0.8.0/package.tgz HL7, Inc 3.0.1 IG Sat, 29 Jul 2017 12:00:00 +1000 GMT hl7.fhir.us.meds#1.0.0 http://hl7.org/fhir/us/meds/STU1/package.tgz http://hl7.org/fhir/us/meds/STU1/package.tgz HL7, Inc 3.0.1 IG Wed, 14 Jun 2017 12:00:00 +1000 GMT hl7.fhir.us.daf#2.0.0 http://hl7.org/fhir/us/daf-research/STU2/package.tgz http://hl7.org/fhir/us/daf-research/STU2/package.tgz HL7, Inc 3.0.1 IG Fri, 21 Apr 2017 12:00:00 +1000 GMT hl7.fhir.uv.sdc#2.0.0 The SDC specification provides an infrastructure to standardize the capture and expanded use of patient-level data collected within an EHR.<br/>This includes two components:<br/>* Support more sophisticated questionnaire/form use-cases such as those needed for research, oncology, pathology and other clinical domains.<br/>*Support pre-population and auto-population of EHR data into forms/questionnaires for uses outside direct clinical care (patient safety, adverse event reporting, public health reporting, etc.). http://hl7.org/fhir/us/sdc/STU2/package.tgz http://hl7.org/fhir/us/sdc/STU2/package.tgz HL7, Inc 3.0.1 IG Fri, 21 Apr 2017 12:00:00 +1000 GMT hl7.fhir.us.core#1.0.0 http://hl7.org/fhir/us/core/STU1/package.tgz http://hl7.org/fhir/us/core/STU1/package.tgz HL7, Inc 3.0.1 IG Tue, 21 Mar 2017 12:00:00 +1100 GMT hl7.fhir.core#1.8.0 FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification http://hl7.org/fhir/2017Jan/package.tgz http://hl7.org/fhir/2017Jan/package.tgz HL7, Inc 1.8.0 fhir.core Tue, 06 Dec 2016 12:00:00 +1100 GMT hl7.fhir.us.ccda#1.8.0 http://hl7.org/fhir/us/ccda/2017Jan/package.tgz http://hl7.org/fhir/us/ccda/2017Jan/package.tgz HL7, Inc 1.8.0 IG Tue, 06 Dec 2016 12:00:00 +1100 GMT hl7.fhir.us.core#0.0.0 http://hl7.org/fhir/us/core/2017Jan/package.tgz http://hl7.org/fhir/us/core/2017Jan/package.tgz HL7, Inc 1.8.0 IG Tue, 06 Dec 2016 12:00:00 +1100 GMT hl7.fhir.us.meds#0.0.1 http://hl7.org/fhir/us/meds/2017Jan/package.tgz http://hl7.org/fhir/us/meds/2017Jan/package.tgz HL7, Inc 1.8.0 IG Tue, 06 Dec 2016 12:00:00 +1100 GMT hl7.fhir.us.daf#1.8.0 http://hl7.org/fhir/us/daf-research/2017Jan/package.tgz http://hl7.org/fhir/us/daf-research/2017Jan/package.tgz HL7, Inc 1.8.0 IG Mon, 05 Dec 2016 12:00:00 +1100 GMT hl7.fhir.us.ccda#1.6.0 http://hl7.org/fhir/us/ccda/2016Sep/package.tgz http://hl7.org/fhir/us/ccda/2016Sep/package.tgz HL7, Inc 1.6.0 IG Thu, 11 Aug 2016 12:00:00 +1000 GMT hl7.fhir.us.daf#1.6.0 http://hl7.org/fhir/us/daf/2016Sep/package.tgz http://hl7.org/fhir/us/daf/2016Sep/package.tgz HL7, Inc 1.6.0 IG Thu, 11 Aug 2016 12:00:00 +1000 GMT hl7.fhir.us.qicore#1.6.0 http://hl7.org/fhir/us/qicore/2016Sep/package.tgz http://hl7.org/fhir/us/qicore/2016Sep/package.tgz HL7, Inc 1.6.0 IG Thu, 11 Aug 2016 12:00:00 +1000 GMT hl7.fhir.r2b.core#1.4.0 Definitions (API, structures and terminologies) for the R2b version of the FHIR standard http://hl7.org/fhir/2016May/hl7.fhir.r2b.core.tgz http://hl7.org/fhir/2016May/hl7.fhir.r2b.core.tgz HL7, Inc 1.4.0 fhir.core Wed, 30 Mar 2016 12:00:00 +1100 GMT hl7.fhir.r2b.corexml#1.4.0 Definitions (API, structures and terminologies) for the R2b version of the FHIR standard http://hl7.org/fhir/2016May/hl7.fhir.r2b.corexml.tgz http://hl7.org/fhir/2016May/hl7.fhir.r2b.corexml.tgz HL7, Inc 1.4.0 fhir.core Wed, 30 Mar 2016 12:00:00 +1100 GMT hl7.fhir.r2b.examples#1.4.0 Example resources in the R2b version of the FHIR standard http://hl7.org/fhir/2016May/hl7.fhir.r2b.examples.tgz http://hl7.org/fhir/2016May/hl7.fhir.r2b.examples.tgz HL7, Inc 1.4.0 fhir.core Wed, 30 Mar 2016 12:00:00 +1100 GMT hl7.fhir.r2b.expansions#1.4.0 Expansions for the R2b version of the FHIR standard http://hl7.org/fhir/2016May/hl7.fhir.r2b.expansions.tgz http://hl7.org/fhir/2016May/hl7.fhir.r2b.expansions.tgz HL7, Inc 1.4.0 fhir.core Wed, 30 Mar 2016 12:00:00 +1100 GMT hl7.fhir.core#1.4.0 Group Wrapper that includes all the R2B packages http://hl7.org/fhir/2016May/package.tgz http://hl7.org/fhir/2016May/package.tgz HL7, Inc 1.4.0 fhir.core Wed, 30 Mar 2016 12:00:00 +1100 GMT hl7.fhir.r2.core#1.0.2 Definitions (API, structures and terminologies) for the R2 version of the FHIR standard http://hl7.org/fhir/DSTU2/hl7.fhir.r2.core.tgz http://hl7.org/fhir/DSTU2/hl7.fhir.r2.core.tgz HL7, Inc 1.0.2 fhir.core Sat, 24 Oct 2015 12:00:00 +1100 GMT hl7.fhir.r2.corexml#1.0.2 Definitions (API, structures and terminologies) for the R2 version of the FHIR standard http://hl7.org/fhir/DSTU2/hl7.fhir.r2.corexml.tgz http://hl7.org/fhir/DSTU2/hl7.fhir.r2.corexml.tgz HL7, Inc 1.0.2 fhir.core Sat, 24 Oct 2015 12:00:00 +1100 GMT hl7.fhir.r2.examples#1.0.2 Example resources in the R2 version of the FHIR standard http://hl7.org/fhir/DSTU2/hl7.fhir.r2.examples.tgz http://hl7.org/fhir/DSTU2/hl7.fhir.r2.examples.tgz HL7, Inc 1.0.2 fhir.core Sat, 24 Oct 2015 12:00:00 +1100 GMT hl7.fhir.r2.expansions#1.0.2 Expansions for the R2 version of the FHIR standard http://hl7.org/fhir/DSTU2/hl7.fhir.r2.expansions.tgz http://hl7.org/fhir/DSTU2/hl7.fhir.r2.expansions.tgz HL7, Inc 1.0.2 fhir.core Sat, 24 Oct 2015 12:00:00 +1100 GMT hl7.fhir.r2.elements#1.0.2 Element Definitions for types defined in the R2 version of the FHIR standard http://hl7.org/fhir/DSTU2/hl7.fhir.r2.elements.tgz http://hl7.org/fhir/DSTU2/hl7.fhir.r2.elements.tgz HL7, Inc 1.0.2 fhir.core Sat, 24 Oct 2015 12:00:00 +1100 GMT hl7.fhir.core#1.0.2 Group Wrapper that includes all the R2 packages http://hl7.org/fhir/DSTU2/package.tgz http://hl7.org/fhir/DSTU2/package.tgz HL7, Inc 1.0.2 fhir.core Sat, 24 Oct 2015 12:00:00 +1100 GMT hl7.fhir.uv.extensions.r3#0.1.0 Ballot for release 5.3 http://hl7.org/fhir/extensions/0.1.0/hl7.fhir.uv.extensions.r3.tgz http://hl7.org/fhir/extensions/0.1.0/hl7.fhir.uv.extensions.r3.tgz HL7, Inc 3.0.2 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions.r4#0.1.0 Ballot for release 5.3 http://hl7.org/fhir/extensions/0.1.0/hl7.fhir.uv.extensions.r4.tgz http://hl7.org/fhir/extensions/0.1.0/hl7.fhir.uv.extensions.r4.tgz HL7, Inc 4.0.1 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions.r5#0.1.0 Ballot for release 5.3 http://hl7.org/fhir/extensions/0.1.0/hl7.fhir.uv.extensions.r5.tgz http://hl7.org/fhir/extensions/0.1.0/hl7.fhir.uv.extensions.r5.tgz HL7, Inc 5.0.0 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions#0.1.0 Ballot for release 5.3 http://hl7.org/fhir/extensions/0.1.0/package.tgz http://hl7.org/fhir/extensions/0.1.0/package.tgz HL7, Inc 5.0.0 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions.r3#1.0.0 Ballot for release 5.3 http://hl7.org/fhir/extensions/1.0.0/hl7.fhir.uv.extensions.r3.tgz http://hl7.org/fhir/extensions/1.0.0/hl7.fhir.uv.extensions.r3.tgz HL7, Inc 3.0.2 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions.r4#1.0.0 Ballot for release 5.3 http://hl7.org/fhir/extensions/1.0.0/hl7.fhir.uv.extensions.r4.tgz http://hl7.org/fhir/extensions/1.0.0/hl7.fhir.uv.extensions.r4.tgz HL7, Inc 4.0.1 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions.r5#1.0.0 Ballot for release 5.3 http://hl7.org/fhir/extensions/1.0.0/hl7.fhir.uv.extensions.r5.tgz http://hl7.org/fhir/extensions/1.0.0/hl7.fhir.uv.extensions.r5.tgz HL7, Inc 5.0.0 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions#1.0.0 Ballot for release 5.3 http://hl7.org/fhir/extensions/1.0.0/package.tgz http://hl7.org/fhir/extensions/1.0.0/package.tgz HL7, Inc 5.0.0 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions.r3#5.1.0-ballot Ballot for release 5.3 http://hl7.org/fhir/extensions/5.1.0-ballot/hl7.fhir.uv.extensions.r3.fixed.tgz http://hl7.org/fhir/extensions/5.1.0-ballot/hl7.fhir.uv.extensions.r3.fixed.tgz HL7, Inc 3.0.2 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions.r4#5.1.0-ballot Ballot for release 5.3 http://hl7.org/fhir/extensions/5.1.0-ballot/hl7.fhir.uv.extensions.r4.fixed.tgz http://hl7.org/fhir/extensions/5.1.0-ballot/hl7.fhir.uv.extensions.r4.fixed.tgz HL7, Inc 4.0.1 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions.r5#5.1.0-ballot Ballot for release 5.3 http://hl7.org/fhir/extensions/5.1.0-ballot/hl7.fhir.uv.extensions.r5.fixed.tgz http://hl7.org/fhir/extensions/5.1.0-ballot/hl7.fhir.uv.extensions.r5.fixed.tgz HL7, Inc 5.0.0 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions#5.1.0-ballot Ballot for release 5.3 http://hl7.org/fhir/extensions/5.1.0-ballot/package.tgz http://hl7.org/fhir/extensions/5.1.0-ballot/package.tgz HL7, Inc 5.0.0 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions.r3#5.1.0-snapshot1 Ballot for release 5.3 http://hl7.org/fhir/extensions/5.1.0-snapshot1/hl7.fhir.uv.extensions.r3.fixed.tgz http://hl7.org/fhir/extensions/5.1.0-snapshot1/hl7.fhir.uv.extensions.r3.fixed.tgz HL7, Inc 3.0.2 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions.r4#5.1.0-snapshot1 Ballot for release 5.3 http://hl7.org/fhir/extensions/5.1.0-snapshot1/hl7.fhir.uv.extensions.r4.fixed.tgz http://hl7.org/fhir/extensions/5.1.0-snapshot1/hl7.fhir.uv.extensions.r4.fixed.tgz HL7, Inc 4.0.1 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions.r5#5.1.0-snapshot1 Ballot for release 5.3 http://hl7.org/fhir/extensions/5.1.0-snapshot1/hl7.fhir.uv.extensions.r5.fixed.tgz http://hl7.org/fhir/extensions/5.1.0-snapshot1/hl7.fhir.uv.extensions.r5.fixed.tgz HL7, Inc 5.0.0 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions#5.1.0-snapshot1 Ballot for release 5.3 http://hl7.org/fhir/extensions/5.1.0-snapshot1/package.tgz http://hl7.org/fhir/extensions/5.1.0-snapshot1/package.tgz HL7, Inc 5.0.0 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions.r3#5.1.0 Ballot for release 5.3 http://hl7.org/fhir/extensions/5.1.0/hl7.fhir.uv.extensions.r3.tgz http://hl7.org/fhir/extensions/5.1.0/hl7.fhir.uv.extensions.r3.tgz HL7, Inc 3.0.2 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions.r4#5.1.0 Ballot for release 5.3 http://hl7.org/fhir/extensions/5.1.0/hl7.fhir.uv.extensions.r4.tgz http://hl7.org/fhir/extensions/5.1.0/hl7.fhir.uv.extensions.r4.tgz HL7, Inc 4.0.1 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions.r5#5.1.0 Ballot for release 5.3 http://hl7.org/fhir/extensions/5.1.0/hl7.fhir.uv.extensions.r5.tgz http://hl7.org/fhir/extensions/5.1.0/hl7.fhir.uv.extensions.r5.tgz HL7, Inc 5.0.0 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions#5.1.0 Ballot for release 5.3 http://hl7.org/fhir/extensions/5.1.0/package.tgz http://hl7.org/fhir/extensions/5.1.0/package.tgz HL7, Inc 5.0.0 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions.r3#5.2.0-ballot Ballot for release 5.3 http://hl7.org/fhir/extensions/5.2.0-ballot/hl7.fhir.uv.extensions.r3.tgz http://hl7.org/fhir/extensions/5.2.0-ballot/hl7.fhir.uv.extensions.r3.tgz HL7, Inc 3.0.2 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions.r4#5.2.0-ballot Ballot for release 5.3 http://hl7.org/fhir/extensions/5.2.0-ballot/hl7.fhir.uv.extensions.r4.tgz http://hl7.org/fhir/extensions/5.2.0-ballot/hl7.fhir.uv.extensions.r4.tgz HL7, Inc 4.0.1 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions.r5#5.2.0-ballot Ballot for release 5.3 http://hl7.org/fhir/extensions/5.2.0-ballot/hl7.fhir.uv.extensions.r5.tgz http://hl7.org/fhir/extensions/5.2.0-ballot/hl7.fhir.uv.extensions.r5.tgz HL7, Inc 5.0.0 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions#5.2.0-ballot Ballot for release 5.3 http://hl7.org/fhir/extensions/5.2.0-ballot/package.tgz http://hl7.org/fhir/extensions/5.2.0-ballot/package.tgz HL7, Inc 5.0.0 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions.r3#5.2.0 Ballot for release 5.3 http://hl7.org/fhir/extensions/5.2.0/hl7.fhir.uv.extensions.r3.tgz http://hl7.org/fhir/extensions/5.2.0/hl7.fhir.uv.extensions.r3.tgz HL7, Inc 3.0.2 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions.r4#5.2.0 Ballot for release 5.3 http://hl7.org/fhir/extensions/5.2.0/hl7.fhir.uv.extensions.r4.tgz http://hl7.org/fhir/extensions/5.2.0/hl7.fhir.uv.extensions.r4.tgz HL7, Inc 4.0.1 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions.r5#5.2.0 Ballot for release 5.3 http://hl7.org/fhir/extensions/5.2.0/hl7.fhir.uv.extensions.r5.tgz http://hl7.org/fhir/extensions/5.2.0/hl7.fhir.uv.extensions.r5.tgz HL7, Inc 5.0.0 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.extensions#5.2.0 Ballot for release 5.3 http://hl7.org/fhir/extensions/5.2.0/package.tgz http://hl7.org/fhir/extensions/5.2.0/package.tgz HL7, Inc 5.0.0 IG Fri, 01 Aug 2025 01:17:55 +1000 Publication run at 01/08/2025 by grahamegrieve using Version 2.0.13-SNAPSHOT (Git# 009b654f089c). Built 2025-08-01T09:16:11.307+10:00 (4 hours old) source id Unknown (todo) hl7.fhir.uv.v2mappings.r4b#1.0.0 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) http://hl7.org/fhir/uv/v2mappings/package.r4b.tgz http://hl7.org/fhir/uv/v2mappings/package.r4b.tgz HL7, Inc 4.3.0 IG Mon, 27 Oct 2025 03:20:36 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.v2mappings.r4#1.0.0 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) http://hl7.org/fhir/uv/v2mappings/package.r4.tgz http://hl7.org/fhir/uv/v2mappings/package.r4.tgz HL7, Inc 4.0.1 IG Mon, 27 Oct 2025 03:20:36 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.ips.r4b#2.0.0 Package hl7.fhir.uv.ips.r4b#2.0.0 http://hl7.org/fhir/uv/ips/package.r4b.tgz http://hl7.org/fhir/uv/ips/package.r4b.tgz HL7, Inc 4.3.0 IG Mon, 27 Oct 2025 03:20:34 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.ips.r4#2.0.0 Package hl7.fhir.uv.ips.r4#2.0.0 http://hl7.org/fhir/uv/ips/package.r4.tgz http://hl7.org/fhir/uv/ips/package.r4.tgz HL7, Inc 4.0.1 IG Mon, 27 Oct 2025 03:20:34 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pct.r4b#2.0.0 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) http://hl7.org/fhir/us/davinci-pct/package.r4b.tgz http://hl7.org/fhir/us/davinci-pct/package.r4b.tgz HL7, Inc 4.3.0 IG Mon, 27 Oct 2025 03:20:28 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pct.r4#2.0.0 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) http://hl7.org/fhir/us/davinci-pct/package.r4.tgz http://hl7.org/fhir/us/davinci-pct/package.r4.tgz HL7, Inc 4.0.1 IG Mon, 27 Oct 2025 03:20:28 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.cql.r4b#1.0.0 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) http://hl7.org/fhir/us/cql/package.r4b.tgz http://hl7.org/fhir/us/cql/package.r4b.tgz HL7, Inc 4.3.0 IG Mon, 27 Oct 2025 03:20:24 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.cql.r4#1.0.0 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) http://hl7.org/fhir/us/cql/package.r4.tgz http://hl7.org/fhir/us/cql/package.r4.tgz HL7, Inc 4.0.1 IG Mon, 27 Oct 2025 03:20:24 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.cancer-reporting.r4b#2.0.0 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) http://hl7.org/fhir/us/cancer-reporting/package.r4b.tgz http://hl7.org/fhir/us/cancer-reporting/package.r4b.tgz HL7, Inc 4.3.0 IG Mon, 27 Oct 2025 03:20:23 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.cancer-reporting.r4#2.0.0 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) http://hl7.org/fhir/us/cancer-reporting/package.r4.tgz http://hl7.org/fhir/us/cancer-reporting/package.r4.tgz HL7, Inc 4.0.1 IG Mon, 27 Oct 2025 03:20:23 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.tx-ecosystem#1.9.0-SNAPSHOT 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, Sep 29, 2025 17:20+1000+10:00) http://hl7.org/fhir/uv/tx-ecosystem/package.tgz http://hl7.org/fhir/uv/tx-ecosystem/package.tgz HL7, Inc 5.0.0 IG Mon, 29 Sep 2025 17:21:46 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.cgm.r4#1.0.0 Communicate Continuous Glucose Monitoring (CGM) data using FHIR (built Wed, Sep 24, 2025 19:39+0000+00:00) http://hl7.org/fhir/uv/cgm/package.r4.tgz http://hl7.org/fhir/uv/cgm/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 25 Sep 2025 06:07:47 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.cgm.r4b#1.0.0 Communicate Continuous Glucose Monitoring (CGM) data using FHIR (built Wed, Sep 24, 2025 19:39+0000+00:00) http://hl7.org/fhir/uv/cgm/package.r4b.tgz http://hl7.org/fhir/uv/cgm/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 25 Sep 2025 06:07:47 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.cqm.r4#1.0.0 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) http://hl7.org/fhir/uv/cqm/package.r4.tgz http://hl7.org/fhir/uv/cqm/package.r4.tgz HL7, Inc 4.0.1 IG Sun, 14 Sep 2025 16:01:02 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.cqm.r4b#1.0.0 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) http://hl7.org/fhir/uv/cqm/package.r4b.tgz http://hl7.org/fhir/uv/cqm/package.r4b.tgz HL7, Inc 4.3.0 IG Sun, 14 Sep 2025 16:01:02 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.xver-r5.r4b#0.0.1-snapshot-2 The cross-version extensions available in FHIR R4B from FHIR R5 (built Sat, Sep 13, 2025 17:27-0400-04:00) http://hl7.org/fhir/uv/xver-r5.r4b/0.0.1-snapshot-2/package.tgz http://hl7.org/fhir/uv/xver-r5.r4b/0.0.1-snapshot-2/package.tgz HL7, Inc 4.3.0 IG Sun, 14 Sep 2025 15:35:52 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.xver-r4b.r5#0.0.1-snapshot-2 The cross-version extensions available in FHIR R5 from FHIR R4B (built Sat, Sep 13, 2025 16:46-0400-04:00) http://hl7.org/fhir/uv/xver-r4b.r5/0.0.1-snapshot-2/package.tgz http://hl7.org/fhir/uv/xver-r4b.r5/0.0.1-snapshot-2/package.tgz HL7, Inc 5.0.0 IG Sun, 14 Sep 2025 15:35:43 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.xver-r4b.r4.r4#0.0.1-snapshot-2 The cross-version extensions available in FHIR R4 from FHIR R4B (built Sat, Sep 13, 2025 16:38-0400-04:00) http://hl7.org/fhir/uv/xver-r4b.r4/0.0.1-snapshot-2/package.r4.tgz http://hl7.org/fhir/uv/xver-r4b.r4/0.0.1-snapshot-2/package.r4.tgz HL7, Inc 4.0.1 IG Sun, 14 Sep 2025 15:35:40 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.xver-r4b.r4.r4b#0.0.1-snapshot-2 The cross-version extensions available in FHIR R4 from FHIR R4B (built Sat, Sep 13, 2025 16:38-0400-04:00) http://hl7.org/fhir/uv/xver-r4b.r4/0.0.1-snapshot-2/package.r4b.tgz http://hl7.org/fhir/uv/xver-r4b.r4/0.0.1-snapshot-2/package.r4b.tgz HL7, Inc 4.3.0 IG Sun, 14 Sep 2025 15:35:40 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.xver-r4b.r4#0.0.1-snapshot-2 The cross-version extensions available in FHIR R4 from FHIR R4B (built Sat, Sep 13, 2025 16:38-0400-04:00) http://hl7.org/fhir/uv/xver-r4b.r4/0.0.1-snapshot-2/package.tgz http://hl7.org/fhir/uv/xver-r4b.r4/0.0.1-snapshot-2/package.tgz HL7, Inc 4.0.1 IG Sun, 14 Sep 2025 15:35:39 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.xver-r4.r4b.r4#0.0.1-snapshot-2 The cross-version extensions available in FHIR R4B from FHIR R4 (built Sat, Sep 13, 2025 16:11-0400-04:00) http://hl7.org/fhir/uv/xver-r4.r4b/0.0.1-snapshot-2/package.r4.tgz http://hl7.org/fhir/uv/xver-r4.r4b/0.0.1-snapshot-2/package.r4.tgz HL7, Inc 4.0.0 IG Sun, 14 Sep 2025 15:35:34 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.xver-r4.r4b.r4b#0.0.1-snapshot-2 The cross-version extensions available in FHIR R4B from FHIR R4 (built Sat, Sep 13, 2025 16:11-0400-04:00) http://hl7.org/fhir/uv/xver-r4.r4b/0.0.1-snapshot-2/package.r4b.tgz http://hl7.org/fhir/uv/xver-r4.r4b/0.0.1-snapshot-2/package.r4b.tgz HL7, Inc 4.3.0 IG Sun, 14 Sep 2025 15:35:34 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.xver-r4.r4b#0.0.1-snapshot-2 The cross-version extensions available in FHIR R4B from FHIR R4 (built Sat, Sep 13, 2025 16:11-0400-04:00) http://hl7.org/fhir/uv/xver-r4.r4b/0.0.1-snapshot-2/package.tgz http://hl7.org/fhir/uv/xver-r4.r4b/0.0.1-snapshot-2/package.tgz HL7, Inc 4.3.0 IG Sun, 14 Sep 2025 15:35:30 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.xver-r3.r4b.r4#0.0.1-snapshot-2 The cross-version extensions available in FHIR R4B from FHIR R3 (built Sat, Sep 13, 2025 15:45-0400-04:00) http://hl7.org/fhir/uv/xver-r3.r4b/0.0.1-snapshot-2/package.r4.tgz http://hl7.org/fhir/uv/xver-r3.r4b/0.0.1-snapshot-2/package.r4.tgz HL7, Inc 4.0.0 IG Sun, 14 Sep 2025 15:35:25 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.xver-r3.r4b.r4b#0.0.1-snapshot-2 The cross-version extensions available in FHIR R4B from FHIR R3 (built Sat, Sep 13, 2025 15:45-0400-04:00) http://hl7.org/fhir/uv/xver-r3.r4b/0.0.1-snapshot-2/package.r4b.tgz http://hl7.org/fhir/uv/xver-r3.r4b/0.0.1-snapshot-2/package.r4b.tgz HL7, Inc 4.3.0 IG Sun, 14 Sep 2025 15:35:25 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.xver-r3.r4b#0.0.1-snapshot-2 The cross-version extensions available in FHIR R4B from FHIR R3 (built Sat, Sep 13, 2025 15:45-0400-04:00) http://hl7.org/fhir/uv/xver-r3.r4b/0.0.1-snapshot-2/package.tgz http://hl7.org/fhir/uv/xver-r3.r4b/0.0.1-snapshot-2/package.tgz HL7, Inc 4.3.0 IG Sun, 14 Sep 2025 15:35:21 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2 The cross-version extensions available in FHIR R4 from FHIR R5 (built Sat, Sep 13, 2025 16:55-0400-04:00) http://hl7.org/fhir/uv/xver-r5.r4/0.0.1-snapshot-2/package.r4.tgz http://hl7.org/fhir/uv/xver-r5.r4/0.0.1-snapshot-2/package.r4.tgz HL7, Inc 4.0.1 IG Sun, 14 Sep 2025 08:19:01 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.xver-r5.r4.r4b#0.0.1-snapshot-2 The cross-version extensions available in FHIR R4 from FHIR R5 (built Sat, Sep 13, 2025 16:55-0400-04:00) http://hl7.org/fhir/uv/xver-r5.r4/0.0.1-snapshot-2/package.r4b.tgz http://hl7.org/fhir/uv/xver-r5.r4/0.0.1-snapshot-2/package.r4b.tgz HL7, Inc 4.3.0 IG Sun, 14 Sep 2025 08:19:01 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.xver-r5.r4#0.0.1-snapshot-2 The cross-version extensions available in FHIR R4 from FHIR R5 (built Sat, Sep 13, 2025 16:55-0400-04:00) http://hl7.org/fhir/uv/xver-r5.r4/0.0.1-snapshot-2/package.tgz http://hl7.org/fhir/uv/xver-r5.r4/0.0.1-snapshot-2/package.tgz HL7, Inc 4.0.1 IG Sun, 14 Sep 2025 08:18:53 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.xver-r4.r5#0.0.1-snapshot-2 The cross-version extensions available in FHIR R5 from FHIR R4 (built Sat, Sep 13, 2025 16:22-0400-04:00) http://hl7.org/fhir/uv/xver-r4.r5/0.0.1-snapshot-2/package.tgz http://hl7.org/fhir/uv/xver-r4.r5/0.0.1-snapshot-2/package.tgz HL7, Inc 5.0.0 IG Sun, 14 Sep 2025 08:18:40 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.xver-r3.r5#0.0.1-snapshot-2 The cross-version extensions available in FHIR R5 from FHIR R3 (built Sat, Sep 13, 2025 15:57-0400-04:00) http://hl7.org/fhir/uv/xver-r3.r5/0.0.1-snapshot-2/package.tgz http://hl7.org/fhir/uv/xver-r3.r5/0.0.1-snapshot-2/package.tgz HL7, Inc 5.0.0 IG Sun, 14 Sep 2025 08:18:28 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.xver-r3.r4.r4#0.0.1-snapshot-2 The cross-version extensions available in FHIR R4 from FHIR R3 (built Sat, Sep 13, 2025 15:32-0400-04:00) http://hl7.org/fhir/uv/xver-r3.r4/0.0.1-snapshot-2/package.r4.tgz http://hl7.org/fhir/uv/xver-r3.r4/0.0.1-snapshot-2/package.r4.tgz HL7, Inc 4.0.1 IG Sun, 14 Sep 2025 08:18:22 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.xver-r3.r4.r4b#0.0.1-snapshot-2 The cross-version extensions available in FHIR R4 from FHIR R3 (built Sat, Sep 13, 2025 15:32-0400-04:00) http://hl7.org/fhir/uv/xver-r3.r4/0.0.1-snapshot-2/package.r4b.tgz http://hl7.org/fhir/uv/xver-r3.r4/0.0.1-snapshot-2/package.r4b.tgz HL7, Inc 4.3.0 IG Sun, 14 Sep 2025 08:18:22 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.xver-r3.r4#0.0.1-snapshot-2 The cross-version extensions available in FHIR R4 from FHIR R3 (built Sat, Sep 13, 2025 15:32-0400-04:00) http://hl7.org/fhir/uv/xver-r3.r4/0.0.1-snapshot-2/package.tgz http://hl7.org/fhir/uv/xver-r3.r4/0.0.1-snapshot-2/package.tgz HL7, Inc 4.0.1 IG Sun, 14 Sep 2025 08:18:19 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.xver-r2.r5#0.0.1-snapshot-2 The cross-version extensions available in FHIR R5 from FHIR R2 (built Sat, Sep 13, 2025 15:20-0400-04:00) http://hl7.org/fhir/uv/xver-r2.r5/0.0.1-snapshot-2/package.tgz http://hl7.org/fhir/uv/xver-r2.r5/0.0.1-snapshot-2/package.tgz HL7, Inc 5.0.0 IG Sun, 14 Sep 2025 08:18:08 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.xver-r2.r4.r4#0.0.1-snapshot-2 The cross-version extensions available in FHIR R4 from FHIR R2 (built Sat, Sep 13, 2025 15:01-0400-04:00) http://hl7.org/fhir/uv/xver-r2.r4/0.0.1-snapshot-2/package.r4.tgz http://hl7.org/fhir/uv/xver-r2.r4/0.0.1-snapshot-2/package.r4.tgz HL7, Inc 4.0.1 IG Sun, 14 Sep 2025 08:18:03 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.xver-r2.r4.r4b#0.0.1-snapshot-2 The cross-version extensions available in FHIR R4 from FHIR R2 (built Sat, Sep 13, 2025 15:01-0400-04:00) http://hl7.org/fhir/uv/xver-r2.r4/0.0.1-snapshot-2/package.r4b.tgz http://hl7.org/fhir/uv/xver-r2.r4/0.0.1-snapshot-2/package.r4b.tgz HL7, Inc 4.3.0 IG Sun, 14 Sep 2025 08:18:03 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.xver-r2.r4#0.0.1-snapshot-2 The cross-version extensions available in FHIR R4 from FHIR R2 (built Sat, Sep 13, 2025 15:01-0400-04:00) http://hl7.org/fhir/uv/xver-r2.r4/0.0.1-snapshot-2/package.tgz http://hl7.org/fhir/uv/xver-r2.r4/0.0.1-snapshot-2/package.tgz HL7, Inc 4.0.1 IG Sun, 14 Sep 2025 08:18:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.xver-r2.r4b.r4#0.0.1-snapshot-2 The cross-version extensions available in FHIR R4B from FHIR R2 (built Sat, Sep 13, 2025 15:10-0400-04:00) http://hl7.org/fhir/uv/xver-r2.r4b/0.0.1-snapshot-2/package.r4.tgz http://hl7.org/fhir/uv/xver-r2.r4b/0.0.1-snapshot-2/package.r4.tgz HL7, Inc 4.0.0 IG Sun, 14 Sep 2025 05:17:15 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.xver-r2.r4b.r4b#0.0.1-snapshot-2 The cross-version extensions available in FHIR R4B from FHIR R2 (built Sat, Sep 13, 2025 15:10-0400-04:00) http://hl7.org/fhir/uv/xver-r2.r4b/0.0.1-snapshot-2/package.r4b.tgz http://hl7.org/fhir/uv/xver-r2.r4b/0.0.1-snapshot-2/package.r4b.tgz HL7, Inc 4.3.0 IG Sun, 14 Sep 2025 05:17:12 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.xver-r2.r4b#0.0.1-snapshot-2 The cross-version extensions available in FHIR R4B from FHIR R2 (built Sat, Sep 13, 2025 15:10-0400-04:00) http://hl7.org/fhir/uv/xver-r2.r4b/0.0.1-snapshot-2/package.tgz http://hl7.org/fhir/uv/xver-r2.r4b/0.0.1-snapshot-2/package.tgz HL7, Inc 4.3.0 IG Sun, 14 Sep 2025 05:17:10 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.rtls.r4#1.0.0-ballot2 Description of IG (built Thu, Aug 7, 2025 17:38+0000+00:00) http://hl7.org/fhir/uv/rtls/2025Sep/package.r4.tgz http://hl7.org/fhir/uv/rtls/2025Sep/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 28 Aug 2025 06:21:56 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.rtls.r4b#1.0.0-ballot2 Description of IG (built Thu, Aug 7, 2025 17:38+0000+00:00) http://hl7.org/fhir/uv/rtls/2025Sep/package.r4b.tgz http://hl7.org/fhir/uv/rtls/2025Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 28 Aug 2025 06:21:56 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.phd.r4#2.0.0-ballot2 Package hl7.fhir.uv.phd.r4#2.0.0-ballot2 http://hl7.org/fhir/uv/phd/2025Sep/package.r4.tgz http://hl7.org/fhir/uv/phd/2025Sep/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 28 Aug 2025 06:21:55 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.phd.r4b#2.0.0-ballot2 Package hl7.fhir.uv.phd.r4b#2.0.0-ballot2 http://hl7.org/fhir/uv/phd/2025Sep/package.r4b.tgz http://hl7.org/fhir/uv/phd/2025Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 28 Aug 2025 06:21:55 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-crd.r4#2.2.0-ballot Guidelines for conveying coverage requirements to clinicians when planning treatment (built Wed, Aug 6, 2025 17:27+0000+00:00) http://hl7.org/fhir/us/davinci-crd/2025Sep/package.r4.tgz http://hl7.org/fhir/us/davinci-crd/2025Sep/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 28 Aug 2025 06:21:54 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-crd.r4b#2.2.0-ballot Guidelines for conveying coverage requirements to clinicians when planning treatment (built Wed, Aug 6, 2025 17:27+0000+00:00) http://hl7.org/fhir/us/davinci-crd/2025Sep/package.r4b.tgz http://hl7.org/fhir/us/davinci-crd/2025Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 28 Aug 2025 06:21:54 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.tools.r3#0.2.0 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 Fri, Apr 26, 2024 06:44+1000+10:00) http://hl7.org/fhir/tools/0.2.0/hl7.fhir.uv.tools.r3.tgz http://hl7.org/fhir/tools/0.2.0/hl7.fhir.uv.tools.r3.tgz HL7, Inc 3.0.2 IG Tue, 05 Aug 2025 20:13:28 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.tools#0.2.0 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 Fri, Apr 26, 2024 06:44+1000+10:00) http://hl7.org/fhir/tools/0.2.0/package.tgz http://hl7.org/fhir/tools/0.2.0/package.tgz HL7, Inc 5.0.0 IG Tue, 05 Aug 2025 20:13:27 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.tools.r5#0.2.0 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 Fri, Apr 26, 2024 06:44+1000+10:00) http://hl7.org/fhir/tools/0.2.0/hl7.fhir.uv.tools.r5.tgz http://hl7.org/fhir/tools/0.2.0/hl7.fhir.uv.tools.r5.tgz HL7, Inc 5.0.0 IG Tue, 05 Aug 2025 20:13:27 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.tools.r4#0.2.0 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 Fri, Apr 26, 2024 06:44+1000+10:00) http://hl7.org/fhir/tools/0.2.0/hl7.fhir.uv.tools.r4.tgz http://hl7.org/fhir/tools/0.2.0/hl7.fhir.uv.tools.r4.tgz HL7, Inc 4.0.1 IG Tue, 05 Aug 2025 20:13:27 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.tools.r5#0.5.0 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 Thu, Apr 17, 2025 05:34+1000+10:00) http://hl7.org/fhir/tools/0.5.0/hl7.fhir.uv.tools.r5.tgz http://hl7.org/fhir/tools/0.5.0/hl7.fhir.uv.tools.r5.tgz HL7, Inc 5.0.0 IG Tue, 05 Aug 2025 20:13:24 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.tools.r4#0.5.0 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 Thu, Apr 17, 2025 05:34+1000+10:00) http://hl7.org/fhir/tools/0.5.0/hl7.fhir.uv.tools.r4.tgz http://hl7.org/fhir/tools/0.5.0/hl7.fhir.uv.tools.r4.tgz HL7, Inc 4.0.1 IG Tue, 05 Aug 2025 20:13:24 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.tools.r3#0.5.0 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 Thu, Apr 17, 2025 05:34+1000+10:00) http://hl7.org/fhir/tools/0.5.0/hl7.fhir.uv.tools.r3.tgz http://hl7.org/fhir/tools/0.5.0/hl7.fhir.uv.tools.r3.tgz HL7, Inc 3.0.2 IG Tue, 05 Aug 2025 20:13:24 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.tools#0.5.0 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 Thu, Apr 17, 2025 05:34+1000+10:00) http://hl7.org/fhir/tools/0.5.0/package.tgz http://hl7.org/fhir/tools/0.5.0/package.tgz HL7, Inc 5.0.0 IG Tue, 05 Aug 2025 20:13:23 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.tools#0.1.0 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, Dec 19, 2023 11:34+1100+11:00) http://hl7.org/fhir/tools/0.1.0/package.tgz http://hl7.org/fhir/tools/0.1.0/package.tgz HL7, Inc 5.0.0 IG Tue, 05 Aug 2025 20:13:22 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.tools.r5#0.1.0 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, Dec 19, 2023 11:34+1100+11:00) http://hl7.org/fhir/tools/0.1.0/hl7.fhir.uv.tools.r5.tgz http://hl7.org/fhir/tools/0.1.0/hl7.fhir.uv.tools.r5.tgz HL7, Inc 5.0.0 IG Tue, 05 Aug 2025 20:13:22 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.tools.r4#0.1.0 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, Dec 19, 2023 11:34+1100+11:00) http://hl7.org/fhir/tools/0.1.0/hl7.fhir.uv.tools.r4.tgz http://hl7.org/fhir/tools/0.1.0/hl7.fhir.uv.tools.r4.tgz HL7, Inc 4.0.1 IG Tue, 05 Aug 2025 20:13:22 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.tools.r3#0.1.0 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, Dec 19, 2023 11:34+1100+11:00) http://hl7.org/fhir/tools/0.1.0/hl7.fhir.uv.tools.r3.tgz http://hl7.org/fhir/tools/0.1.0/hl7.fhir.uv.tools.r3.tgz HL7, Inc 3.0.2 IG Tue, 05 Aug 2025 20:13:22 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.tools.r5#0.4.0 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, Mar 10, 2025 15:06+1100+11:00) http://hl7.org/fhir/tools/0.4.0/hl7.fhir.uv.tools.r5.tgz http://hl7.org/fhir/tools/0.4.0/hl7.fhir.uv.tools.r5.tgz HL7, Inc 5.0.0 IG Tue, 05 Aug 2025 20:13:21 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.tools.r4#0.4.0 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, Mar 10, 2025 15:06+1100+11:00) http://hl7.org/fhir/tools/0.4.0/hl7.fhir.uv.tools.r4.tgz http://hl7.org/fhir/tools/0.4.0/hl7.fhir.uv.tools.r4.tgz HL7, Inc 4.0.1 IG Tue, 05 Aug 2025 20:13:21 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.tools.r3#0.4.0 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, Mar 10, 2025 15:06+1100+11:00) http://hl7.org/fhir/tools/0.4.0/hl7.fhir.uv.tools.r3.tgz http://hl7.org/fhir/tools/0.4.0/hl7.fhir.uv.tools.r3.tgz HL7, Inc 3.0.2 IG Tue, 05 Aug 2025 20:13:21 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.tools.r4#0.4.1 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 11, 2025 14:21+1100+11:00) http://hl7.org/fhir/tools/0.4.1/hl7.fhir.uv.tools.r4.tgz http://hl7.org/fhir/tools/0.4.1/hl7.fhir.uv.tools.r4.tgz HL7, Inc 4.0.1 IG Tue, 05 Aug 2025 20:13:20 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.tools.r3#0.4.1 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 11, 2025 14:21+1100+11:00) http://hl7.org/fhir/tools/0.4.1/hl7.fhir.uv.tools.r3.tgz http://hl7.org/fhir/tools/0.4.1/hl7.fhir.uv.tools.r3.tgz HL7, Inc 3.0.2 IG Tue, 05 Aug 2025 20:13:20 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.tools#0.4.0 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, Mar 10, 2025 15:06+1100+11:00) http://hl7.org/fhir/tools/0.4.0/package.tgz http://hl7.org/fhir/tools/0.4.0/package.tgz HL7, Inc 5.0.0 IG Tue, 05 Aug 2025 20:13:20 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.tools.r5#0.4.1 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 11, 2025 14:21+1100+11:00) http://hl7.org/fhir/tools/0.4.1/hl7.fhir.uv.tools.r5.tgz http://hl7.org/fhir/tools/0.4.1/hl7.fhir.uv.tools.r5.tgz HL7, Inc 5.0.0 IG Tue, 05 Aug 2025 20:13:19 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.tools#0.4.1 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 11, 2025 14:21+1100+11:00) http://hl7.org/fhir/tools/0.4.1/package.tgz http://hl7.org/fhir/tools/0.4.1/package.tgz HL7, Inc 5.0.0 IG Tue, 05 Aug 2025 20:13:18 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.tools.r5#0.3.0 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 Sun, Oct 27, 2024 07:27+1100+11:00) http://hl7.org/fhir/tools/0.3.0/hl7.fhir.uv.tools.r5.tgz http://hl7.org/fhir/tools/0.3.0/hl7.fhir.uv.tools.r5.tgz HL7, Inc 5.0.0 IG Tue, 05 Aug 2025 20:13:14 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.tools.r4#0.3.0 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 Sun, Oct 27, 2024 07:27+1100+11:00) http://hl7.org/fhir/tools/0.3.0/hl7.fhir.uv.tools.r4.tgz http://hl7.org/fhir/tools/0.3.0/hl7.fhir.uv.tools.r4.tgz HL7, Inc 4.0.1 IG Tue, 05 Aug 2025 20:13:14 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.tools.r3#0.3.0 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 Sun, Oct 27, 2024 07:27+1100+11:00) http://hl7.org/fhir/tools/0.3.0/hl7.fhir.uv.tools.r3.tgz http://hl7.org/fhir/tools/0.3.0/hl7.fhir.uv.tools.r3.tgz HL7, Inc 3.0.2 IG Tue, 05 Aug 2025 20:13:14 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.tools#0.3.0 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 Sun, Oct 27, 2024 07:27+1100+11:00) http://hl7.org/fhir/tools/0.3.0/package.tgz http://hl7.org/fhir/tools/0.3.0/package.tgz HL7, Inc 5.0.0 IG Tue, 05 Aug 2025 20:13:13 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.bulkdata.r4#3.0.0-ballot 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) http://hl7.org/fhir/uv/bulkdata/2025Sep/package.r4.tgz http://hl7.org/fhir/uv/bulkdata/2025Sep/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 05 Aug 2025 19:52:08 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.bulkdata.r4b#3.0.0-ballot 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) http://hl7.org/fhir/uv/bulkdata/2025Sep/package.r4b.tgz http://hl7.org/fhir/uv/bulkdata/2025Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 05 Aug 2025 19:52:08 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.resp-net.r4#2.0.0-ballot 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) http://hl7.org/fhir/us/resp-net/2025Sep/package.r4.tgz http://hl7.org/fhir/us/resp-net/2025Sep/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 05 Aug 2025 19:52:07 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.resp-net.r4b#2.0.0-ballot 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) http://hl7.org/fhir/us/resp-net/2025Sep/package.r4b.tgz http://hl7.org/fhir/us/resp-net/2025Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 05 Aug 2025 19:52:07 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.pacio-adi.r4#2.0.0-ballot PACIO Advance Directive Interoperability Implementation Guide (built Mon, Aug 4, 2025 21:33+0000+00:00) http://hl7.org/fhir/us/pacio-adi/2025Sep/package.r4.tgz http://hl7.org/fhir/us/pacio-adi/2025Sep/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 05 Aug 2025 19:52:06 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.pacio-adi.r4b#2.0.0-ballot PACIO Advance Directive Interoperability Implementation Guide (built Mon, Aug 4, 2025 21:33+0000+00:00) http://hl7.org/fhir/us/pacio-adi/2025Sep/package.r4b.tgz http://hl7.org/fhir/us/pacio-adi/2025Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 05 Aug 2025 19:52:06 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-dtr.r4#2.2.0-ballot 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) http://hl7.org/fhir/us/davinci-dtr/2025Sep/package.r4.tgz http://hl7.org/fhir/us/davinci-dtr/2025Sep/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 05 Aug 2025 19:52:04 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-dtr.r4b#2.2.0-ballot 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) http://hl7.org/fhir/us/davinci-dtr/2025Sep/package.r4b.tgz http://hl7.org/fhir/us/davinci-dtr/2025Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 05 Aug 2025 19:52:04 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.extensions.r5#5.3.0-ballot-tc 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) http://hl7.org/fhir/extensions/5.3.0-ballot-tc/hl7.fhir.uv.extensions.r5.tgz http://hl7.org/fhir/extensions/5.3.0-ballot-tc/hl7.fhir.uv.extensions.r5.tgz HL7, Inc 5.0.0 IG Sat, 02 Aug 2025 21:25:07 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.extensions.r4#5.3.0-ballot-tc 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) http://hl7.org/fhir/extensions/5.3.0-ballot-tc/hl7.fhir.uv.extensions.r4.tgz http://hl7.org/fhir/extensions/5.3.0-ballot-tc/hl7.fhir.uv.extensions.r4.tgz HL7, Inc 4.0.1 IG Sat, 02 Aug 2025 21:25:07 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.extensions#5.3.0-ballot-tc 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) http://hl7.org/fhir/extensions/5.3.0-ballot-tc/package.tgz http://hl7.org/fhir/extensions/5.3.0-ballot-tc/package.tgz HL7, Inc 5.0.0 IG Sat, 02 Aug 2025 21:25:07 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.crmi.r4#2.0.0-ballot 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) http://hl7.org/fhir/uv/crmi/2025Sep/package.r4.tgz http://hl7.org/fhir/uv/crmi/2025Sep/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 02 Aug 2025 21:10:10 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.crmi.r4b#2.0.0-ballot 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) http://hl7.org/fhir/uv/crmi/2025Sep/package.r4b.tgz http://hl7.org/fhir/uv/crmi/2025Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 02 Aug 2025 21:10:10 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.qicore.r4#8.0.0-ballot 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) http://hl7.org/fhir/us/qicore/2025Sep/package.r4.tgz http://hl7.org/fhir/us/qicore/2025Sep/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 02 Aug 2025 21:10:08 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.qicore.r4b#8.0.0-ballot 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) http://hl7.org/fhir/us/qicore/2025Sep/package.r4b.tgz http://hl7.org/fhir/us/qicore/2025Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 02 Aug 2025 21:10:08 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.cdc-opioid-cpg.r4#1.0.0-ballot 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) http://hl7.org/fhir/us/cdc-opioid-cpg/2025Sep/package.r4.tgz http://hl7.org/fhir/us/cdc-opioid-cpg/2025Sep/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 02 Aug 2025 21:10:07 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.cdc-opioid-cpg.r4b#1.0.0-ballot 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) http://hl7.org/fhir/us/cdc-opioid-cpg/2025Sep/package.r4b.tgz http://hl7.org/fhir/us/cdc-opioid-cpg/2025Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 02 Aug 2025 21:10:07 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.health-care-surveys-reporting.r4#2.0.0-ballot 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 Thu, Jul 31, 2025 23:11+0000+00:00) http://hl7.org/fhir/us/health-care-surveys-reporting/2025Sep/package.r4.tgz http://hl7.org/fhir/us/health-care-surveys-reporting/2025Sep/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 01 Aug 2025 09:29:18 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.health-care-surveys-reporting.r4b#2.0.0-ballot 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 Thu, Jul 31, 2025 23:11+0000+00:00) http://hl7.org/fhir/us/health-care-surveys-reporting/2025Sep/package.r4b.tgz http://hl7.org/fhir/us/health-care-surveys-reporting/2025Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 01 Aug 2025 09:29:18 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.ph-library.r4#2.0.0-ballot 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) http://hl7.org/fhir/us/ph-library/2025Sep/package.r4.tgz http://hl7.org/fhir/us/ph-library/2025Sep/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 01 Aug 2025 09:09:01 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.ph-library.r4b#2.0.0-ballot 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) http://hl7.org/fhir/us/ph-library/2025Sep/package.r4b.tgz http://hl7.org/fhir/us/ph-library/2025Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 01 Aug 2025 09:09:01 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.medication-rems.r4#2.0.0-ballot FHIR implementation options and guidance for medication REMS participants (built Thu, Jul 31, 2025 17:49+0000+00:00) http://hl7.org/fhir/us/medication-rems/2025Sep/package.r4.tgz http://hl7.org/fhir/us/medication-rems/2025Sep/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 01 Aug 2025 09:09:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.medication-rems.r4b#2.0.0-ballot FHIR implementation options and guidance for medication REMS participants (built Thu, Jul 31, 2025 17:49+0000+00:00) http://hl7.org/fhir/us/medication-rems/2025Sep/package.r4b.tgz http://hl7.org/fhir/us/medication-rems/2025Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 01 Aug 2025 09:09:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pas.r4#2.2.0-ballot Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Wed, Jul 30, 2025 00:50+0000+00:00) http://hl7.org/fhir/us/davinci-pas/2025Sep/package.r4.tgz http://hl7.org/fhir/us/davinci-pas/2025Sep/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 01 Aug 2025 09:08:59 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pas.r4b#2.2.0-ballot Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Wed, Jul 30, 2025 00:50+0000+00:00) http://hl7.org/fhir/us/davinci-pas/2025Sep/package.r4b.tgz http://hl7.org/fhir/us/davinci-pas/2025Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 01 Aug 2025 09:08:59 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.pacio-pfe.r4#2.0.0 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) http://hl7.org/fhir/us/pacio-pfe/package.r4.tgz http://hl7.org/fhir/us/pacio-pfe/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 26 Jul 2025 06:11:40 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.pacio-pfe.r4b#2.0.0 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) http://hl7.org/fhir/us/pacio-pfe/package.r4b.tgz http://hl7.org/fhir/us/pacio-pfe/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 26 Jul 2025 06:11:40 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.smart-health-cards-and-links.r4#1.0.0 FHIR Implementation Guide for SMART Health Cards and Links (built Tue, Jul 22, 2025 13:19+0000+00:00) http://hl7.org/fhir/uv/smart-health-cards-and-links/STU1/package.r4.tgz http://hl7.org/fhir/uv/smart-health-cards-and-links/STU1/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 26 Jul 2025 06:11:40 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.smart-health-cards-and-links.r4b#1.0.0 FHIR Implementation Guide for SMART Health Cards and Links (built Tue, Jul 22, 2025 13:19+0000+00:00) http://hl7.org/fhir/uv/smart-health-cards-and-links/STU1/package.r4b.tgz http://hl7.org/fhir/uv/smart-health-cards-and-links/STU1/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 26 Jul 2025 06:11:40 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.patient-corrections.r4#1.0.0 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) http://hl7.org/fhir/uv/patient-corrections/package.r4.tgz http://hl7.org/fhir/uv/patient-corrections/package.r4.tgz HL7, Inc 4.0.1 IG Sun, 20 Jul 2025 21:09:09 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.patient-corrections.r4b#1.0.0 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) http://hl7.org/fhir/uv/patient-corrections/package.r4b.tgz http://hl7.org/fhir/uv/patient-corrections/package.r4b.tgz HL7, Inc 4.3.0 IG Sun, 20 Jul 2025 21:09:09 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.qicore.r4#7.0.1 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 Thu, Jul 17, 2025 17:50+0000+00:00) http://hl7.org/fhir/us/qicore/package.r4.tgz http://hl7.org/fhir/us/qicore/package.r4.tgz HL7, Inc 4.0.1 IG Sun, 20 Jul 2025 21:09:08 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.qicore.r4b#7.0.1 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 Thu, Jul 17, 2025 17:50+0000+00:00) http://hl7.org/fhir/us/qicore/package.r4b.tgz http://hl7.org/fhir/us/qicore/package.r4b.tgz HL7, Inc 4.3.0 IG Sun, 20 Jul 2025 21:09:08 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.cql.r4#2.0.0 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) http://hl7.org/fhir/uv/cql/package.r4.tgz http://hl7.org/fhir/uv/cql/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 10 Jul 2025 17:17:26 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.cql.r4b#2.0.0 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) http://hl7.org/fhir/uv/cql/package.r4b.tgz http://hl7.org/fhir/uv/cql/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 10 Jul 2025 17:17:26 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.nhsn-dqm.r4#1.0.0 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) http://hl7.org/fhir/us/nhsn-dqm/STU1/package.r4.tgz http://hl7.org/fhir/us/nhsn-dqm/STU1/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 10 Jul 2025 17:17:19 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.nhsn-dqm.r4b#1.0.0 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) http://hl7.org/fhir/us/nhsn-dqm/STU1/package.r4b.tgz http://hl7.org/fhir/us/nhsn-dqm/STU1/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 10 Jul 2025 17:17:19 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-ra.r4#2.1.0 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) http://hl7.org/fhir/us/davinci-ra/package.r4.tgz http://hl7.org/fhir/us/davinci-ra/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 08 Jul 2025 04:55:22 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-ra.r4b#2.1.0 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) http://hl7.org/fhir/us/davinci-ra/package.r4b.tgz http://hl7.org/fhir/us/davinci-ra/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 08 Jul 2025 04:55:22 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.fhir-clinical-document.r4#1.0.0 Package hl7.fhir.uv.fhir-clinical-document.r4#1.0.0 http://hl7.org/fhir/uv/fhir-clinical-document/STU1/package.r4.tgz http://hl7.org/fhir/uv/fhir-clinical-document/STU1/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 27 Jun 2025 07:58:29 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.fhir-clinical-document.r4b#1.0.0 Package hl7.fhir.uv.fhir-clinical-document.r4b#1.0.0 http://hl7.org/fhir/uv/fhir-clinical-document/STU1/package.r4b.tgz http://hl7.org/fhir/uv/fhir-clinical-document/STU1/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 27 Jun 2025 07:58:29 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.resp-net.r4#1.0.0 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 Thu, Jun 19, 2025 21:49+0000+00:00) http://hl7.org/fhir/us/resp-net/STU1/package.r4.tgz http://hl7.org/fhir/us/resp-net/STU1/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 27 Jun 2025 07:58:28 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.resp-net.r4b#1.0.0 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 Thu, Jun 19, 2025 21:49+0000+00:00) http://hl7.org/fhir/us/resp-net/STU1/package.r4b.tgz http://hl7.org/fhir/us/resp-net/STU1/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 27 Jun 2025 07:58:28 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.qicore.r4#7.0.0 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 Wed, Jun 18, 2025 22:12+0000+00:00) http://hl7.org/fhir/us/qicore/STU7/package.r4.tgz http://hl7.org/fhir/us/qicore/STU7/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 27 Jun 2025 07:58:26 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.qicore.r4b#7.0.0 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 Wed, Jun 18, 2025 22:12+0000+00:00) http://hl7.org/fhir/us/qicore/STU7/package.r4b.tgz http://hl7.org/fhir/us/qicore/STU7/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 27 Jun 2025 07:58:26 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pdex.r4#2.1.0 This specification has undergone ballot and connectathon testing. It is expected to continue to evolve, possibly significantly, as part of that process. Feedback 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. This 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. [Financial Management](https://confluence.hl7.org/display/FM/Financial+Management+Home) is the Sponsoring Work Group for this Implementation Guide. **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.** The 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). This 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. This IG covers the exchange of: - Claims-based information (without financials) - Clinical Information (such as Lab Results, Allergies and Conditions) - Prior Authorization information This 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. This IG covers the exchange of a Member's Health History in the following scenarios: - Provider requested exchange using SMART-on-FHIR Bulk exchange - Health Plan Exchange using SMART-on-FHIR - Member-authorized Health Plan to Health Plan exchange - Member-authorized Health Plan to Third-Party Application exchange The latter two scenarios are provided to meet the requirements identified in the CMS Interoperability and Patient Access Final Rule. **There are items in this guide that are subject to update**. This includes: - Value Sets - Vocabularies (X12, NUBC etc.) - Examples **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). See the [Table of Contents](toc.html) for more information. (built Wed, Jun 18, 2025 03:12+0000+00:00) http://hl7.org/fhir/us/davinci-pdex/package.r4.tgz http://hl7.org/fhir/us/davinci-pdex/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 27 Jun 2025 07:58:20 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pdex.r4b#2.1.0 This specification has undergone ballot and connectathon testing. It is expected to continue to evolve, possibly significantly, as part of that process. Feedback 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. This 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. [Financial Management](https://confluence.hl7.org/display/FM/Financial+Management+Home) is the Sponsoring Work Group for this Implementation Guide. **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.** The 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). This 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. This IG covers the exchange of: - Claims-based information (without financials) - Clinical Information (such as Lab Results, Allergies and Conditions) - Prior Authorization information This 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. This IG covers the exchange of a Member's Health History in the following scenarios: - Provider requested exchange using SMART-on-FHIR Bulk exchange - Health Plan Exchange using SMART-on-FHIR - Member-authorized Health Plan to Health Plan exchange - Member-authorized Health Plan to Third-Party Application exchange The latter two scenarios are provided to meet the requirements identified in the CMS Interoperability and Patient Access Final Rule. **There are items in this guide that are subject to update**. This includes: - Value Sets - Vocabularies (X12, NUBC etc.) - Examples **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). See the [Table of Contents](toc.html) for more information. (built Wed, Jun 18, 2025 03:12+0000+00:00) http://hl7.org/fhir/us/davinci-pdex/package.r4b.tgz http://hl7.org/fhir/us/davinci-pdex/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 27 Jun 2025 07:58:20 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.core.r4#8.0.0 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. These 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) http://hl7.org/fhir/us/core/package.r4.tgz http://hl7.org/fhir/us/core/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 11 Jun 2025 14:47:01 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.core.r4b#8.0.0 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. These 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) http://hl7.org/fhir/us/core/package.r4b.tgz http://hl7.org/fhir/us/core/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 11 Jun 2025 14:47:01 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.smp.r4#1.0.0 Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Fri, May 16, 2025 20:17+0000+00:00) http://hl7.org/fhir/us/smp/STU1/package.r4.tgz http://hl7.org/fhir/us/smp/STU1/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 29 May 2025 05:27:16 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.smp.r4b#1.0.0 Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Fri, May 16, 2025 20:17+0000+00:00) http://hl7.org/fhir/us/smp/STU1/package.r4b.tgz http://hl7.org/fhir/us/smp/STU1/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 29 May 2025 05:27:16 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.sdoh-clinicalcare.r4#2.3.0 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) http://hl7.org/fhir/us/sdoh-clinicalcare/package.r4.tgz http://hl7.org/fhir/us/sdoh-clinicalcare/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 29 May 2025 05:27:16 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.sdoh-clinicalcare.r4b#2.3.0 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) http://hl7.org/fhir/us/sdoh-clinicalcare/package.r4b.tgz http://hl7.org/fhir/us/sdoh-clinicalcare/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 29 May 2025 05:27:16 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.mdi.r4#2.0.0 Package hl7.fhir.us.mdi.r4#2.0.0 http://hl7.org/fhir/us/mdi/package.r4.tgz http://hl7.org/fhir/us/mdi/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 29 May 2025 05:27:12 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.mdi.r4b#2.0.0 Package hl7.fhir.us.mdi.r4b#2.0.0 http://hl7.org/fhir/us/mdi/package.r4b.tgz http://hl7.org/fhir/us/mdi/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 29 May 2025 05:27:12 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-deqm.r4#5.0.0 Package hl7.fhir.us.davinci-deqm.r4#5.0.0 http://hl7.org/fhir/us/davinci-deqm/package.r4.tgz http://hl7.org/fhir/us/davinci-deqm/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 29 May 2025 05:27:08 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-deqm.r4b#5.0.0 Package hl7.fhir.us.davinci-deqm.r4b#5.0.0 http://hl7.org/fhir/us/davinci-deqm/package.r4b.tgz http://hl7.org/fhir/us/davinci-deqm/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 29 May 2025 05:27:08 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-atr.r4#2.1.0 Exchange of member attribution list between payers and providers (built Fri, May 16, 2025 17:34+0000+00:00) http://hl7.org/fhir/us/davinci-atr/package.r4.tgz http://hl7.org/fhir/us/davinci-atr/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 29 May 2025 05:27:02 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-atr.r4b#2.1.0 Exchange of member attribution list between payers and providers (built Fri, May 16, 2025 17:34+0000+00:00) http://hl7.org/fhir/us/davinci-atr/package.r4b.tgz http://hl7.org/fhir/us/davinci-atr/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 29 May 2025 05:27:02 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.ndh.r4#1.0.0 Package hl7.fhir.us.ndh.r4#1.0.0 http://hl7.org/fhir/us/ndh/package.r4.tgz http://hl7.org/fhir/us/ndh/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 16 Apr 2025 07:29:30 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.ndh.r4b#1.0.0 Package hl7.fhir.us.ndh.r4b#1.0.0 http://hl7.org/fhir/us/ndh/package.r4b.tgz http://hl7.org/fhir/us/ndh/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 16 Apr 2025 07:29:30 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.extensions#5.1.0-ballot1 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Tue, Dec 19, 2023 08:38+1100+11:00) http://hl7.org/fhir/extensions/5.1.0-ballot/package.tgz http://hl7.org/fhir/extensions/5.1.0-ballot/package.tgz HL7, Inc 5.0.0 IG Wed, 09 Apr 2025 09:15:02 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pr.r4#1.0.0 Package hl7.fhir.us.davinci-pr.r4#1.0.0 http://hl7.org/fhir/us/davinci-pr/package.r4.tgz http://hl7.org/fhir/us/davinci-pr/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 09 Apr 2025 05:27:42 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pr.r4b#1.0.0 Package hl7.fhir.us.davinci-pr.r4b#1.0.0 http://hl7.org/fhir/us/davinci-pr/package.r4b.tgz http://hl7.org/fhir/us/davinci-pr/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 09 Apr 2025 05:27:42 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-alerts.r4#1.1.0 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) http://hl7.org/fhir/us/davinci-alerts/package.r4.tgz http://hl7.org/fhir/us/davinci-alerts/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 09 Apr 2025 05:27:41 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-alerts.r4b#1.1.0 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) http://hl7.org/fhir/us/davinci-alerts/STU1.1/package.r4b.tgz http://hl7.org/fhir/us/davinci-alerts/STU1.1/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 09 Apr 2025 05:27:41 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.cow.r4#1.0.0-ballot An Implementation Guide providing the foundational guidance for order-based workflow FHIR interoperability (built Mon, Apr 7, 2025 15:35+0000+00:00) http://hl7.org/fhir/uv/cow/2025May/package.r4.tgz http://hl7.org/fhir/uv/cow/2025May/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 08 Apr 2025 10:42:07 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.cow.r4b#1.0.0-ballot An Implementation Guide providing the foundational guidance for order-based workflow FHIR interoperability (built Mon, Apr 7, 2025 15:35+0000+00:00) http://hl7.org/fhir/uv/cow/2025May/package.r4b.tgz http://hl7.org/fhir/uv/cow/2025May/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 08 Apr 2025 10:42:07 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.phr.r4#1.0.0-ballot2 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) http://hl7.org/fhir/uv/phr/2025May/package.r4.tgz http://hl7.org/fhir/uv/phr/2025May/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 04 Apr 2025 11:59:36 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.phr.r4b#1.0.0-ballot2 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) http://hl7.org/fhir/uv/phr/2025May/package.r4b.tgz http://hl7.org/fhir/uv/phr/2025May/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 04 Apr 2025 11:59:36 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.cql.r4#1.0.0-ballot This implementation guide contains common CQL assets for use with FHIR in US-realm environments, including the USCore-ModelInfo and USCommon libraries. (built Tue, Apr 1, 2025 14:00+0000+00:00) http://hl7.org/fhir/us/cql/2025May/package.r4.tgz http://hl7.org/fhir/us/cql/2025May/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 02 Apr 2025 13:05:46 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.cql.r4b#1.0.0-ballot This implementation guide contains common CQL assets for use with FHIR in US-realm environments, including the USCore-ModelInfo and USCommon libraries. (built Tue, Apr 1, 2025 14:00+0000+00:00) http://hl7.org/fhir/us/cql/2025May/package.r4b.tgz http://hl7.org/fhir/us/cql/2025May/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 02 Apr 2025 13:05:46 +1100 Added from file system scan on 28/10/2025 hl7.fhir.r6.corexml#6.0.0-ballot3 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) http://hl7.org/fhir/6.0.0-ballot3/hl7.fhir.r6.corexml.tgz http://hl7.org/fhir/6.0.0-ballot3/hl7.fhir.r6.corexml.tgz HL7, Inc 6.0.0-ballot3 IG Tue, 01 Apr 2025 12:28:44 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.cgm.r4#1.0.0-ballot Communicate Continuous Glucose Monitoring (CGM) data using FHIR (built Mon, Mar 31, 2025 13:42+0000+00:00) http://hl7.org/fhir/uv/cgm/2025May/package.r4.tgz http://hl7.org/fhir/uv/cgm/2025May/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 01 Apr 2025 09:17:23 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.cgm.r4b#1.0.0-ballot Communicate Continuous Glucose Monitoring (CGM) data using FHIR (built Mon, Mar 31, 2025 13:42+0000+00:00) http://hl7.org/fhir/uv/cgm/2025May/package.r4b.tgz http://hl7.org/fhir/uv/cgm/2025May/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 01 Apr 2025 09:17:23 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.pco.r4#1.0.0-ballot Person-Centered Outcomes (PCO) FHIR Implementation Guide (built Fri, Mar 28, 2025 21:02+0000+00:00) http://hl7.org/fhir/us/pco/2025May/package.r4.tgz http://hl7.org/fhir/us/pco/2025May/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 01 Apr 2025 09:17:22 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.pco.r4b#1.0.0-ballot Person-Centered Outcomes (PCO) FHIR Implementation Guide (built Fri, Mar 28, 2025 21:02+0000+00:00) http://hl7.org/fhir/us/pco/2025May/package.r4b.tgz http://hl7.org/fhir/us/pco/2025May/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 01 Apr 2025 09:17:22 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.cancer-reporting.r4#2.0.0-ballot 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 Mon, Mar 31, 2025 19:51+0000+00:00) http://hl7.org/fhir/us/cancer-reporting/2025May/package.r4.tgz http://hl7.org/fhir/us/cancer-reporting/2025May/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 01 Apr 2025 09:17:22 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.cancer-reporting.r4b#2.0.0-ballot 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 Mon, Mar 31, 2025 19:51+0000+00:00) http://hl7.org/fhir/us/cancer-reporting/2025May/package.r4b.tgz http://hl7.org/fhir/us/cancer-reporting/2025May/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 01 Apr 2025 09:17:22 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.pacio-toc.r4#1.0.0-ballot 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) http://hl7.org/fhir/us/pacio-toc/2025May/package.r4.tgz http://hl7.org/fhir/us/pacio-toc/2025May/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 29 Mar 2025 06:53:32 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.pacio-toc.r4b#1.0.0-ballot 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) http://hl7.org/fhir/us/pacio-toc/2025May/package.r4b.tgz http://hl7.org/fhir/us/pacio-toc/2025May/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 29 Mar 2025 06:53:32 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.safr.r4#1.0.0-ballot US Situational Awareness Framework for Reporting (US SAFR) (built Fri, Mar 28, 2025 19:37+0000+00:00) http://hl7.org/fhir/us/safr/2025May/package.r4.tgz http://hl7.org/fhir/us/safr/2025May/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 29 Mar 2025 06:53:32 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.safr.r4b#1.0.0-ballot US Situational Awareness Framework for Reporting (US SAFR) (built Fri, Mar 28, 2025 19:37+0000+00:00) http://hl7.org/fhir/us/safr/2025May/package.r4b.tgz http://hl7.org/fhir/us/safr/2025May/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 29 Mar 2025 06:53:32 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.mdi.r4#2.0.0-snapshot2 Package hl7.fhir.us.mdi.r4#2.0.0-snapshot2 http://hl7.org/fhir/us/mdi/2.0.0-snapshot2/package.r4.tgz http://hl7.org/fhir/us/mdi/2.0.0-snapshot2/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 28 Mar 2025 22:19:36 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.mdi.r4b#2.0.0-snapshot2 Package hl7.fhir.us.mdi.r4b#2.0.0-snapshot2 http://hl7.org/fhir/us/mdi/2.0.0-snapshot2/package.r4b.tgz http://hl7.org/fhir/us/mdi/2.0.0-snapshot2/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 28 Mar 2025 22:19:36 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.ipa.r4#1.1.0 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) http://hl7.org/fhir/uv/ipa/package.r4.tgz http://hl7.org/fhir/uv/ipa/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 20 Mar 2025 14:01:34 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.ipa.r4b#1.1.0 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) http://hl7.org/fhir/uv/ipa/STU1.1/package.r4b.tgz http://hl7.org/fhir/uv/ipa/STU1.1/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 20 Mar 2025 14:01:34 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-drug-formulary.r4#2.1.0 DaVinci Payer Data Exchange (PDex) US Drug Formulary" (built Wed, Feb 26, 2025 18:01+0000+00:00) http://hl7.org/fhir/us/davinci-drug-formulary/package.r4.tgz http://hl7.org/fhir/us/davinci-drug-formulary/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 27 Feb 2025 16:18:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-drug-formulary.r4b#2.1.0 DaVinci Payer Data Exchange (PDex) US Drug Formulary" (built Wed, Feb 26, 2025 18:01+0000+00:00) http://hl7.org/fhir/us/davinci-drug-formulary/package.r4b.tgz http://hl7.org/fhir/us/davinci-drug-formulary/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 27 Feb 2025 16:18:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pdex-plan-net.r4#1.2.0 Da Vinci PDex Plan Net (built Tue, Feb 25, 2025 20:09+0000+00:00) http://hl7.org/fhir/us/davinci-pdex-plan-net/package.r4.tgz http://hl7.org/fhir/us/davinci-pdex-plan-net/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 26 Feb 2025 16:51:07 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pdex-plan-net.r4b#1.2.0 Da Vinci PDex Plan Net (built Tue, Feb 25, 2025 20:09+0000+00:00) http://hl7.org/fhir/us/davinci-pdex-plan-net/package.r4b.tgz http://hl7.org/fhir/us/davinci-pdex-plan-net/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 26 Feb 2025 16:51:07 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-ra.r4#2.0.0 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, Feb 19, 2025 15:09+0000+00:00) http://hl7.org/fhir/us/davinci-ra/STU2/package.r4.tgz http://hl7.org/fhir/us/davinci-ra/STU2/package.r4.tgz HL7, Inc 4.0.1 IG Mon, 24 Feb 2025 04:25:39 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-ra.r4b#2.0.0 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, Feb 19, 2025 15:09+0000+00:00) http://hl7.org/fhir/us/davinci-ra/STU2/package.r4b.tgz http://hl7.org/fhir/us/davinci-ra/STU2/package.r4b.tgz HL7, Inc 4.3.0 IG Mon, 24 Feb 2025 04:25:39 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.vhdir.r4#1.0.0 This is a Healthedata1 sandbox for creation of resources and examples (built Tue, Feb 18, 2025 15:41+0000+00:00) http://hl7.org/fhir/uv/vhdir/package.r4.tgz http://hl7.org/fhir/uv/vhdir/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 19 Feb 2025 14:09:05 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.vhdir.r4b#1.0.0 This is a Healthedata1 sandbox for creation of resources and examples (built Tue, Feb 18, 2025 15:41+0000+00:00) http://hl7.org/fhir/uv/vhdir/package.r4b.tgz http://hl7.org/fhir/uv/vhdir/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 19 Feb 2025 14:09:05 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.mcode.r4#4.0.0 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) http://hl7.org/fhir/us/mcode/package.r4.tgz http://hl7.org/fhir/us/mcode/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 19 Feb 2025 14:09:02 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.mcode.r4b#4.0.0 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) http://hl7.org/fhir/us/mcode/package.r4b.tgz http://hl7.org/fhir/us/mcode/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 19 Feb 2025 14:09:02 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.codex-radiation-therapy.r4#2.0.0 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) http://hl7.org/fhir/us/codex-radiation-therapy/package.r4.tgz http://hl7.org/fhir/us/codex-radiation-therapy/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 19 Feb 2025 14:08:50 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.codex-radiation-therapy.r4b#2.0.0 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) http://hl7.org/fhir/us/codex-radiation-therapy/package.r4b.tgz http://hl7.org/fhir/us/codex-radiation-therapy/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 19 Feb 2025 14:08:50 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.carin-bb.r4#2.1.0 CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) (built Tue, Feb 18, 2025 18:08+0000+00:00) http://hl7.org/fhir/us/carin-bb/package.r4.tgz http://hl7.org/fhir/us/carin-bb/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 19 Feb 2025 14:08:44 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.carin-bb.r4b#2.1.0 CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) (built Tue, Feb 18, 2025 18:08+0000+00:00) http://hl7.org/fhir/us/carin-bb/package.r4b.tgz http://hl7.org/fhir/us/carin-bb/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 19 Feb 2025 14:08:44 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.mcode.r4#3.0.0 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) http://hl7.org/fhir/us/mcode/STU3/package.r4.tgz http://hl7.org/fhir/us/mcode/STU3/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 19 Feb 2025 12:22:18 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.mcode.r4b#3.0.0 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) http://hl7.org/fhir/us/mcode/STU3/package.r4b.tgz http://hl7.org/fhir/us/mcode/STU3/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 19 Feb 2025 12:22:18 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.mcode.r4#2.1.0 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 Tue, Mar 21, 2023 04:49+1100+11:00) http://hl7.org/fhir/us/mcode/STU2.1/package.r4.tgz http://hl7.org/fhir/us/mcode/STU2.1/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 19 Feb 2025 12:22:13 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.mcode.r4b#2.1.0 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 Tue, Mar 21, 2023 04:49+1100+11:00) http://hl7.org/fhir/us/mcode/STU2.1/package.r4b.tgz http://hl7.org/fhir/us/mcode/STU2.1/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 19 Feb 2025 12:22:13 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.mcode.r4#4.0.0-ballot 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, Apr 10, 2024 13:47+0000+00:00) http://hl7.org/fhir/us/mcode/2024May/package.r4.tgz http://hl7.org/fhir/us/mcode/2024May/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 19 Feb 2025 12:22:07 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.mcode.r4b#4.0.0-ballot 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, Apr 10, 2024 13:47+0000+00:00) http://hl7.org/fhir/us/mcode/2024May/package.r4b.tgz http://hl7.org/fhir/us/mcode/2024May/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 19 Feb 2025 12:22:07 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.mcode.r4#3.0.0-ballot 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 Tue, Mar 28, 2023 19:23+0000+00:00) http://hl7.org/fhir/us/mcode/2023May/package.r4.tgz http://hl7.org/fhir/us/mcode/2023May/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 19 Feb 2025 12:22:04 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.mcode.r4b#3.0.0-ballot 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 Tue, Mar 28, 2023 19:23+0000+00:00) http://hl7.org/fhir/us/mcode/2023May/package.r4b.tgz http://hl7.org/fhir/us/mcode/2023May/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 19 Feb 2025 12:22:04 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-cdex.r4#2.1.0 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) http://hl7.org/fhir/us/davinci-cdex/STU2.1/package.r4.tgz http://hl7.org/fhir/us/davinci-cdex/STU2.1/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 11 Feb 2025 04:01:08 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-cdex.r4b#2.1.0 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) http://hl7.org/fhir/us/davinci-cdex/STU2.1/package.r4b.tgz http://hl7.org/fhir/us/davinci-cdex/STU2.1/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 11 Feb 2025 04:01:08 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-cdex.r4#2.0.0 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 Wed, Mar 22, 2023 00:14+1100+11:00) http://hl7.org/fhir/us/davinci-cdex/STU2/package.r4.tgz http://hl7.org/fhir/us/davinci-cdex/STU2/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 11 Feb 2025 04:01:05 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-cdex.r4b#2.0.0 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 Wed, Mar 22, 2023 00:14+1100+11:00) http://hl7.org/fhir/us/davinci-cdex/STU2/package.r4b.tgz http://hl7.org/fhir/us/davinci-cdex/STU2/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 11 Feb 2025 04:01:05 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-cdex.r4#2.1.0-snapshot 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) http://hl7.org/fhir/us/davinci-cdex/STU2.1-snapshot/package.r4.tgz http://hl7.org/fhir/us/davinci-cdex/STU2.1-snapshot/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 11 Feb 2025 04:01:02 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-cdex.r4b#2.1.0-snapshot 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) http://hl7.org/fhir/us/davinci-cdex/STU2.1-snapshot/package.r4b.tgz http://hl7.org/fhir/us/davinci-cdex/STU2.1-snapshot/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 11 Feb 2025 04:01:02 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.extensions.r3#5.1.0-cibuild 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) http://hl7.org/fhir/extensions/5.1.0-snapshot1/hl7.fhir.uv.extensions.r3.fixed.tgz http://hl7.org/fhir/extensions/5.1.0-snapshot1/hl7.fhir.uv.extensions.r3.fixed.tgz HL7, Inc 3.0.2 IG Mon, 10 Feb 2025 22:56:33 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.extensions.r5#5.1.0-cibuild 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) http://hl7.org/fhir/extensions/5.1.0-snapshot1/hl7.fhir.uv.extensions.r5.fixed.tgz http://hl7.org/fhir/extensions/5.1.0-snapshot1/hl7.fhir.uv.extensions.r5.fixed.tgz HL7, Inc 5.0.0 IG Mon, 10 Feb 2025 22:56:31 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.extensions.r4#5.1.0-cibuild 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) http://hl7.org/fhir/extensions/5.1.0-snapshot1/hl7.fhir.uv.extensions.r4.fixed.tgz http://hl7.org/fhir/extensions/5.1.0-snapshot1/hl7.fhir.uv.extensions.r4.fixed.tgz HL7, Inc 4.0.1 IG Mon, 10 Feb 2025 22:56:31 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.extensions.r3#5.1.0-ballot1 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Tue, Dec 19, 2023 08:38+1100+11:00) http://hl7.org/fhir/extensions/5.1.0-ballot/hl7.fhir.uv.extensions.r3.fixed.tgz http://hl7.org/fhir/extensions/5.1.0-ballot/hl7.fhir.uv.extensions.r3.fixed.tgz HL7, Inc 3.0.2 IG Mon, 10 Feb 2025 22:55:33 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.extensions.r4#5.1.0-ballot1 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Tue, Dec 19, 2023 08:38+1100+11:00) http://hl7.org/fhir/extensions/5.1.0-ballot/hl7.fhir.uv.extensions.r4.fixed.tgz http://hl7.org/fhir/extensions/5.1.0-ballot/hl7.fhir.uv.extensions.r4.fixed.tgz HL7, Inc 4.0.1 IG Mon, 10 Feb 2025 22:55:32 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.extensions.r5#5.1.0-ballot1 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Tue, Dec 19, 2023 08:38+1100+11:00) http://hl7.org/fhir/extensions/5.1.0-ballot/hl7.fhir.uv.extensions.r5.fixed.tgz http://hl7.org/fhir/extensions/5.1.0-ballot/hl7.fhir.uv.extensions.r5.fixed.tgz HL7, Inc 5.0.0 IG Mon, 10 Feb 2025 22:55:31 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-dtr.r4#2.1.0 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 Sat, Dec 21, 2024 16:14+0000+00:00) http://hl7.org/fhir/us/davinci-dtr/package.r4.tgz http://hl7.org/fhir/us/davinci-dtr/package.r4.tgz HL7, Inc 4.0.1 IG Sun, 22 Dec 2024 03:41:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-dtr.r4b#2.1.0 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 Sat, Dec 21, 2024 16:14+0000+00:00) http://hl7.org/fhir/us/davinci-dtr/package.r4b.tgz http://hl7.org/fhir/us/davinci-dtr/package.r4b.tgz HL7, Inc 4.3.0 IG Sun, 22 Dec 2024 03:41:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-dtr.r4#2.1.0-preview 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, Sep 27, 2024 06:27-0400-04:00) http://hl7.org/fhir/us/davinci-dtr/2.1.0-preview/package.r4.tgz http://hl7.org/fhir/us/davinci-dtr/2.1.0-preview/package.r4.tgz HL7, Inc 4.0.1 IG Sun, 22 Dec 2024 03:41:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-dtr.r4b#2.1.0-preview 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, Sep 27, 2024 06:27-0400-04:00) http://hl7.org/fhir/us/davinci-dtr/2.1.0-preview/package.r4b.tgz http://hl7.org/fhir/us/davinci-dtr/2.1.0-preview/package.r4b.tgz HL7, Inc 4.3.0 IG Sun, 22 Dec 2024 03:41:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-dtr#3.0.1 Guidelines for documentation templates and rules for coverage requirements (built Tue, Aug 6, 2019 12:58-0400-04:00) http://hl7.org/fhir/us/davinci-dtr/2019Sep/STU3/package.tgz http://hl7.org/fhir/us/davinci-dtr/2019Sep/STU3/package.tgz HL7, Inc 3.0.1 IG Sun, 22 Dec 2024 03:40:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-dtr.r4#2.0.1 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 Thu, Jan 11, 2024 19:19+0000+00:00) http://hl7.org/fhir/us/davinci-dtr/STU2/package.r4.tgz http://hl7.org/fhir/us/davinci-dtr/STU2/package.r4.tgz HL7, Inc 4.0.1 IG Sun, 22 Dec 2024 03:39:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-dtr.r4b#2.0.1 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 Thu, Jan 11, 2024 19:19+0000+00:00) http://hl7.org/fhir/us/davinci-dtr/STU2/package.r4b.tgz http://hl7.org/fhir/us/davinci-dtr/STU2/package.r4b.tgz HL7, Inc 4.3.0 IG Sun, 22 Dec 2024 03:39:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pas.r4#2.1.0 Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Fri, Dec 20, 2024 21:41+0000+00:00) http://hl7.org/fhir/us/davinci-pas/package.r4.tgz http://hl7.org/fhir/us/davinci-pas/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 21 Dec 2024 09:31:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pas.r4b#2.1.0 Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Fri, Dec 20, 2024 21:41+0000+00:00) http://hl7.org/fhir/us/davinci-pas/package.r4b.tgz http://hl7.org/fhir/us/davinci-pas/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 21 Dec 2024 09:31:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pas.r4#2.1.0-preview Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Thu, Sep 26, 2024 18:54-0400-04:00) http://hl7.org/fhir/us/davinci-pas/2.1.0-preview/package.r4.tgz http://hl7.org/fhir/us/davinci-pas/2.1.0-preview/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 21 Dec 2024 09:30:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pas.r4b#2.1.0-preview Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Thu, Sep 26, 2024 18:54-0400-04:00) http://hl7.org/fhir/us/davinci-pas/2.1.0-preview/package.r4b.tgz http://hl7.org/fhir/us/davinci-pas/2.1.0-preview/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 21 Dec 2024 09:30:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pas.r4#2.0.1 Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Fri, Dec 1, 2023 20:54+0000+00:00) http://hl7.org/fhir/us/davinci-pas/STU2/package.r4.tgz http://hl7.org/fhir/us/davinci-pas/STU2/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 21 Dec 2024 09:26:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pas.r4b#2.0.1 Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Fri, Dec 1, 2023 20:54+0000+00:00) http://hl7.org/fhir/us/davinci-pas/STU2/package.r4b.tgz http://hl7.org/fhir/us/davinci-pas/STU2/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 21 Dec 2024 09:26:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.ccda.r4#2.0.0-ballot 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. This 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). The 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. We 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. ### Scope To represent Consolidated CDA Templates for Clinical Notes (C-CDA) 2.1 templates using FHIR profiles. This first stage of the project defines all the C-CDA document-level profiles on the Composition resource and contained sections. Any 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. For 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) http://hl7.org/fhir/us/ccda/2025Jan/package.r4.tgz http://hl7.org/fhir/us/ccda/2025Jan/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 18 Dec 2024 09:12:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.ccda.r4b#2.0.0-ballot 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. This 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). The 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. We 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. ### Scope To represent Consolidated CDA Templates for Clinical Notes (C-CDA) 2.1 templates using FHIR profiles. This first stage of the project defines all the C-CDA document-level profiles on the Composition resource and contained sections. Any 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. For 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) http://hl7.org/fhir/us/ccda/2025Jan/package.r4b.tgz http://hl7.org/fhir/us/ccda/2025Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 18 Dec 2024 09:12:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.udap-security.r4#2.0.0-ballot 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) http://hl7.org/fhir/us/udap-security/2025Jan/package.r4.tgz http://hl7.org/fhir/us/udap-security/2025Jan/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 18 Dec 2024 02:11:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.udap-security.r4b#2.0.0-ballot 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) http://hl7.org/fhir/us/udap-security/2025Jan/package.r4b.tgz http://hl7.org/fhir/us/udap-security/2025Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 18 Dec 2024 02:11:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.sdc.r4#4.0.0-ballot 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) http://hl7.org/fhir/uv/sdc/2025Jan/package.r4.tgz http://hl7.org/fhir/uv/sdc/2025Jan/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 17 Dec 2024 13:19:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.sdc.r4b#4.0.0-ballot 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) http://hl7.org/fhir/uv/sdc/2025Jan/package.r4b.tgz http://hl7.org/fhir/uv/sdc/2025Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 17 Dec 2024 13:19:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.cqm.r4#1.0.0-ballot 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, Dec 16, 2024 21:47+0000+00:00) http://hl7.org/fhir/uv/cqm/2025Jan/package.r4.tgz http://hl7.org/fhir/uv/cqm/2025Jan/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 17 Dec 2024 09:06:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.cqm.r4b#1.0.0-ballot 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, Dec 16, 2024 21:47+0000+00:00) http://hl7.org/fhir/uv/cqm/2025Jan/package.r4b.tgz http://hl7.org/fhir/uv/cqm/2025Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 17 Dec 2024 09:06:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.cql.r4#2.0.0-ballot 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 Mon, Dec 16, 2024 21:01+0000+00:00) http://hl7.org/fhir/uv/cql/2025Jan/package.r4.tgz http://hl7.org/fhir/uv/cql/2025Jan/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 17 Dec 2024 08:13:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.cql.r4b#2.0.0-ballot 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 Mon, Dec 16, 2024 21:01+0000+00:00) http://hl7.org/fhir/uv/cql/2025Jan/package.r4b.tgz http://hl7.org/fhir/uv/cql/2025Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 17 Dec 2024 08:13:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pr.r4#1.0.0-ballot Package hl7.fhir.us.davinci-pr.r4#1.0.0-ballot http://hl7.org/fhir/us/davinci-pr/2025Jan/package.r4.tgz http://hl7.org/fhir/us/davinci-pr/2025Jan/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 17 Dec 2024 05:53:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pr.r4b#1.0.0-ballot Package hl7.fhir.us.davinci-pr.r4b#1.0.0-ballot http://hl7.org/fhir/us/davinci-pr/2025Jan/package.r4b.tgz http://hl7.org/fhir/us/davinci-pr/2025Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 17 Dec 2024 05:53:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.core.r4#8.0.0-ballot 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. These 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 Fri, Dec 13, 2024 16:53+0000+00:00) http://hl7.org/fhir/us/core/2025Jan/package.r4.tgz http://hl7.org/fhir/us/core/2025Jan/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 14 Dec 2024 05:34:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.core.r4b#8.0.0-ballot 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. These 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 Fri, Dec 13, 2024 16:53+0000+00:00) http://hl7.org/fhir/us/core/2025Jan/package.r4b.tgz http://hl7.org/fhir/us/core/2025Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 14 Dec 2024 05:34:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.genomics-reporting.r4#3.0.0 Guidelines for reporting of clinical genomics results using HL7 FHIR. (built Thu, Dec 12, 2024 21:07+0000+00:00) http://hl7.org/fhir/uv/genomics-reporting/package.r4.tgz http://hl7.org/fhir/uv/genomics-reporting/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 13 Dec 2024 08:57:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.genomics-reporting.r4b#3.0.0 Guidelines for reporting of clinical genomics results using HL7 FHIR. (built Thu, Dec 12, 2024 21:07+0000+00:00) http://hl7.org/fhir/uv/genomics-reporting/package.r4b.tgz http://hl7.org/fhir/uv/genomics-reporting/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 13 Dec 2024 08:57:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.genomics-reporting.r4#3.0.0-ballot Guidelines for reporting of clinical genomics results using HL7 FHIR. (built Mon, Dec 18, 2023 22:39+0000+00:00) http://hl7.org/fhir/uv/genomics-reporting/2024Jan/package.r4.tgz http://hl7.org/fhir/uv/genomics-reporting/2024Jan/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 13 Dec 2024 08:54:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.genomics-reporting.r4b#3.0.0-ballot Guidelines for reporting of clinical genomics results using HL7 FHIR. (built Mon, Dec 18, 2023 22:39+0000+00:00) http://hl7.org/fhir/uv/genomics-reporting/2024Jan/package.r4b.tgz http://hl7.org/fhir/uv/genomics-reporting/2024Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 13 Dec 2024 08:54:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.mdi.r4#2.0.0-ballot2 Package hl7.fhir.us.mdi.r4#2.0.0-ballot2 http://hl7.org/fhir/us/mdi/2025Jan/package.r4.tgz http://hl7.org/fhir/us/mdi/2025Jan/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 13 Dec 2024 04:38:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.mdi.r4b#2.0.0-ballot2 Package hl7.fhir.us.mdi.r4b#2.0.0-ballot2 http://hl7.org/fhir/us/mdi/2025Jan/package.r4b.tgz http://hl7.org/fhir/us/mdi/2025Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 13 Dec 2024 04:38:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.cardx-htn-mng.r4#1.0.0-ballot Package hl7.fhir.uv.cardx-htn-mng.r4#1.0.0-ballot http://hl7.org/fhir/uv/cardx-htn-mng/2024May/package.r4.tgz http://hl7.org/fhir/uv/cardx-htn-mng/2024May/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 13 Dec 2024 01:53:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.cardx-htn-mng.r4b#1.0.0-ballot Package hl7.fhir.uv.cardx-htn-mng.r4b#1.0.0-ballot http://hl7.org/fhir/uv/cardx-htn-mng/2024May/package.r4b.tgz http://hl7.org/fhir/uv/cardx-htn-mng/2024May/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 13 Dec 2024 01:53:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.cardx-htn-mng.r4#1.0.0 Package hl7.fhir.uv.cardx-htn-mng.r4#1.0.0 http://hl7.org/fhir/uv/cardx-htn-mng/package.r4.tgz http://hl7.org/fhir/uv/cardx-htn-mng/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 13 Dec 2024 01:53:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.cardx-htn-mng.r4b#1.0.0 Package hl7.fhir.uv.cardx-htn-mng.r4b#1.0.0 http://hl7.org/fhir/uv/cardx-htn-mng/package.r4b.tgz http://hl7.org/fhir/uv/cardx-htn-mng/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 13 Dec 2024 01:53:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-crd.r4#2.1.0 Guidelines for conveying coverage requirements to clinicians when planning treatment (built Wed, Dec 11, 2024 19:17+0000+00:00) http://hl7.org/fhir/us/davinci-crd/package.r4.tgz http://hl7.org/fhir/us/davinci-crd/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 12 Dec 2024 07:10:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-crd.r4b#2.1.0 Guidelines for conveying coverage requirements to clinicians when planning treatment (built Wed, Dec 11, 2024 19:17+0000+00:00) http://hl7.org/fhir/us/davinci-crd/package.r4b.tgz http://hl7.org/fhir/us/davinci-crd/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 12 Dec 2024 07:10:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-crd.stu3#0.1.0 Guidelines for conveying coverage requirements to clinicians when planning treatment http://hl7.org/fhir/us/davinci-crd/2018Sep/STU3/package.tgz http://hl7.org/fhir/us/davinci-crd/2018Sep/STU3/package.tgz HL7, Inc 3.0.1 IG Thu, 12 Dec 2024 07:09:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-crd.r4#2.1.0-preview Guidelines for conveying coverage requirements to clinicians when planning treatment (built Thu, Sep 26, 2024 14:58-0400-04:00) http://hl7.org/fhir/us/davinci-crd/STU2.1-preview/package.r4.tgz http://hl7.org/fhir/us/davinci-crd/STU2.1-preview/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 12 Dec 2024 07:07:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-crd.r4b#2.1.0-preview Guidelines for conveying coverage requirements to clinicians when planning treatment (built Thu, Sep 26, 2024 14:58-0400-04:00) http://hl7.org/fhir/us/davinci-crd/STU2.1-preview/package.r4b.tgz http://hl7.org/fhir/us/davinci-crd/STU2.1-preview/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 12 Dec 2024 07:07:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-crd.r4#2.0.1 Guidelines for conveying coverage requirements to clinicians when planning treatment (built Mon, Jan 8, 2024 18:55+0000+00:00) http://hl7.org/fhir/us/davinci-crd/STU2/package.r4.tgz http://hl7.org/fhir/us/davinci-crd/STU2/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 12 Dec 2024 07:07:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-crd.r4b#2.0.1 Guidelines for conveying coverage requirements to clinicians when planning treatment (built Mon, Jan 8, 2024 18:55+0000+00:00) http://hl7.org/fhir/us/davinci-crd/STU2/package.r4b.tgz http://hl7.org/fhir/us/davinci-crd/STU2/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 12 Dec 2024 07:07:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-alerts.r4#1.1.0-preview 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 Wed, Dec 11, 2024 19:02+1100+11:00) http://hl7.org/fhir/us/davinci-alerts/STU1.1-snapshot/package.r4.tgz http://hl7.org/fhir/us/davinci-alerts/STU1.1-snapshot/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 11 Dec 2024 19:57:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-alerts.r4b#1.1.0-preview 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 Wed, Dec 11, 2024 19:02+1100+11:00) http://hl7.org/fhir/us/davinci-alerts/STU1.1-snapshot/package.r4b.tgz http://hl7.org/fhir/us/davinci-alerts/STU1.1-snapshot/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 11 Dec 2024 19:57:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-hrex.r4#1.1.0 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) http://hl7.org/fhir/us/davinci-hrex/package.r4.tgz http://hl7.org/fhir/us/davinci-hrex/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 11 Dec 2024 04:42:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-hrex.r4b#1.1.0 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) http://hl7.org/fhir/us/davinci-hrex/package.r4b.tgz http://hl7.org/fhir/us/davinci-hrex/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 11 Dec 2024 04:42:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-hrex.r4#1.1.0-ballot 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, Aug 13, 2024 16:31+0000+00:00) http://hl7.org/fhir/us/davinci-hrex/2024Sep/package.r4.tgz http://hl7.org/fhir/us/davinci-hrex/2024Sep/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 11 Dec 2024 04:41:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-hrex.r4b#1.1.0-ballot 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, Aug 13, 2024 16:31+0000+00:00) http://hl7.org/fhir/us/davinci-hrex/2024Sep/package.r4b.tgz http://hl7.org/fhir/us/davinci-hrex/2024Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 11 Dec 2024 04:41:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.cpg.r4#2.0.0 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) http://hl7.org/fhir/uv/cpg/package.r4.tgz http://hl7.org/fhir/uv/cpg/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 27 Nov 2024 05:48:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.cpg.r4b#2.0.0 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) http://hl7.org/fhir/uv/cpg/package.r4b.tgz http://hl7.org/fhir/uv/cpg/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 27 Nov 2024 05:48:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.cpg.r4#2.0.0-ballot 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) http://hl7.org/fhir/uv/cpg/2024Jan/package.r4.tgz http://hl7.org/fhir/uv/cpg/2024Jan/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 27 Nov 2024 05:46:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.cpg.r4b#2.0.0-ballot 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) http://hl7.org/fhir/uv/cpg/2024Jan/package.r4b.tgz http://hl7.org/fhir/uv/cpg/2024Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 27 Nov 2024 05:46:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.core.v610#6.1.0 Package hl7.fhir.us.core.v610#6.1.0 http://hl7.org/fhir/us/core/v610/package.tgz http://hl7.org/fhir/us/core/v610/package.tgz HL7, Inc 4.0.1 IG Tue, 19 Nov 2024 07:15:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.cqfmeasures.r4#5.0.0 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) http://hl7.org/fhir/us/cqfmeasures/package.r4.tgz http://hl7.org/fhir/us/cqfmeasures/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 05 Nov 2024 08:21:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.cqfmeasures.r4b#5.0.0 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) http://hl7.org/fhir/us/cqfmeasures/package.r4b.tgz http://hl7.org/fhir/us/cqfmeasures/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 05 Nov 2024 08:21:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.cqfmeasures.r4#4.0.0-ballot The Fast Healthcare Interoperability Resource (FHIR) Quality Measure Implementation Guide (this IG) describes an approach to representing electronic Clinical Quality Measures (eCQMs) 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 Sun, Dec 4, 2022 15:27+0000+00:00) http://hl7.org/fhir/us/cqfmeasures/2023Jan/package.r4.tgz http://hl7.org/fhir/us/cqfmeasures/2023Jan/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 05 Nov 2024 08:19:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.cqfmeasures.r4b#4.0.0-ballot The Fast Healthcare Interoperability Resource (FHIR) Quality Measure Implementation Guide (this IG) describes an approach to representing electronic Clinical Quality Measures (eCQMs) 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 Sun, Dec 4, 2022 15:27+0000+00:00) http://hl7.org/fhir/us/cqfmeasures/2023Jan/package.r4b.tgz http://hl7.org/fhir/us/cqfmeasures/2023Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 05 Nov 2024 08:19:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.cqfmeasures.r4#5.0.0-ballot 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 Fri, Dec 15, 2023 17:42+0000+00:00) http://hl7.org/fhir/us/cqfmeasures/2024Jan/package.r4.tgz http://hl7.org/fhir/us/cqfmeasures/2024Jan/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 05 Nov 2024 08:18:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.cqfmeasures.r4b#5.0.0-ballot 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 Fri, Dec 15, 2023 17:42+0000+00:00) http://hl7.org/fhir/us/cqfmeasures/2024Jan/package.r4b.tgz http://hl7.org/fhir/us/cqfmeasures/2024Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 05 Nov 2024 08:18:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.cqfmeasures.r4#5.0.0-ballot2 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 Tue, Apr 9, 2024 13:15+0000+00:00) http://hl7.org/fhir/us/cqfmeasures/2024May/package.r4.tgz http://hl7.org/fhir/us/cqfmeasures/2024May/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 05 Nov 2024 08:16:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.cqfmeasures.r4b#5.0.0-ballot2 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 Tue, Apr 9, 2024 13:15+0000+00:00) http://hl7.org/fhir/us/cqfmeasures/2024May/package.r4b.tgz http://hl7.org/fhir/us/cqfmeasures/2024May/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 05 Nov 2024 08:16:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.cqfmeasures.r4#4.0.0 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, Aug 28, 2023 20:07+0000+00:00) http://hl7.org/fhir/us/cqfmeasures/STU4/package.r4.tgz http://hl7.org/fhir/us/cqfmeasures/STU4/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 05 Nov 2024 08:13:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.cqfmeasures.r4b#4.0.0 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, Aug 28, 2023 20:07+0000+00:00) http://hl7.org/fhir/us/cqfmeasures/STU4/package.r4b.tgz http://hl7.org/fhir/us/cqfmeasures/STU4/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 05 Nov 2024 08:13:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.ecr.r4#2.1.2 # Introduction and Purpose With 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. With 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. For 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). For Clinical Safety Information please refer to the [FHIR Implementer’s Safety Checklist](http://hl7.org/fhir/safety.html). <div style="background-color: #ffffcc; border-left: 6px solid #ffeb3b;"> <p><b>Known Issue:</b></p> <p>The following issue is related to a publication tooling issue. A technical correction is planned once the tooling issue has been addressed.</p> <ul> <li><a href="https://jira.hl7.org/browse/FHIR-30477" rel="external" target="_blank">FHIR-30477</a>: Resolution errors for FHIRHelpers and FHIR-ModelInfo.</li> </ul> </div> # Stakeholders * Regulatory Agencies * Standards Development Organizations * Vendors: EHR, PHR; Health Care IT; Clinical Decision Support Systems, Public Health Surveillance Systems * Providers: Ambulatory and Healthcare Institutions (hospitals, long term care, mental health) * Local, State, Tribal and Federal Public Health Agencies (built Wed, Oct 30, 2024 20:32+0000+00:00) http://hl7.org/fhir/us/ecr/package.r4.tgz http://hl7.org/fhir/us/ecr/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 31 Oct 2024 08:43:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.ecr.r4b#2.1.2 # Introduction and Purpose With 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. With 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. For 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). For Clinical Safety Information please refer to the [FHIR Implementer’s Safety Checklist](http://hl7.org/fhir/safety.html). <div style="background-color: #ffffcc; border-left: 6px solid #ffeb3b;"> <p><b>Known Issue:</b></p> <p>The following issue is related to a publication tooling issue. A technical correction is planned once the tooling issue has been addressed.</p> <ul> <li><a href="https://jira.hl7.org/browse/FHIR-30477" rel="external" target="_blank">FHIR-30477</a>: Resolution errors for FHIRHelpers and FHIR-ModelInfo.</li> </ul> </div> # Stakeholders * Regulatory Agencies * Standards Development Organizations * Vendors: EHR, PHR; Health Care IT; Clinical Decision Support Systems, Public Health Surveillance Systems * Providers: Ambulatory and Healthcare Institutions (hospitals, long term care, mental health) * Local, State, Tribal and Federal Public Health Agencies (built Wed, Oct 30, 2024 20:32+0000+00:00) http://hl7.org/fhir/us/ecr/package.r4b.tgz http://hl7.org/fhir/us/ecr/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 31 Oct 2024 08:43:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.ecr.r4#2.1.1 # Introduction and Purpose With 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. With 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. For 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). For Clinical Safety Information please refer to the [FHIR Implementer’s Safety Checklist](http://hl7.org/fhir/safety.html). <div style="background-color: #ffffcc; border-left: 6px solid #ffeb3b;"> <p><b>Known Issue:</b></p> <p>The following issue is related to a publication tooling issue. A technical correction is planned once the tooling issue has been addressed.</p> <ul> <li><a href="https://jira.hl7.org/browse/FHIR-30477" rel="external" target="_blank">FHIR-30477</a>: Resolution errors for FHIRHelpers and FHIR-ModelInfo.</li> </ul> </div> # Stakeholders * Regulatory Agencies * Standards Development Organizations * Vendors: EHR, PHR; Health Care IT; Clinical Decision Support Systems, Public Health Surveillance Systems * Providers: Ambulatory and Healthcare Institutions (hospitals, long term care, mental health) * Local, State, Tribal and Federal Public Health Agencies (built Thu, Dec 14, 2023 17:04+0000+00:00) http://hl7.org/fhir/us/ecr/old-STU2.1/package.r4.tgz http://hl7.org/fhir/us/ecr/old-STU2.1/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 31 Oct 2024 08:40:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.ecr.r4b#2.1.1 # Introduction and Purpose With 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. With 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. For 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). For Clinical Safety Information please refer to the [FHIR Implementer’s Safety Checklist](http://hl7.org/fhir/safety.html). <div style="background-color: #ffffcc; border-left: 6px solid #ffeb3b;"> <p><b>Known Issue:</b></p> <p>The following issue is related to a publication tooling issue. A technical correction is planned once the tooling issue has been addressed.</p> <ul> <li><a href="https://jira.hl7.org/browse/FHIR-30477" rel="external" target="_blank">FHIR-30477</a>: Resolution errors for FHIRHelpers and FHIR-ModelInfo.</li> </ul> </div> # Stakeholders * Regulatory Agencies * Standards Development Organizations * Vendors: EHR, PHR; Health Care IT; Clinical Decision Support Systems, Public Health Surveillance Systems * Providers: Ambulatory and Healthcare Institutions (hospitals, long term care, mental health) * Local, State, Tribal and Federal Public Health Agencies (built Thu, Dec 14, 2023 17:04+0000+00:00) http://hl7.org/fhir/us/ecr/old-STU2.1/package.r4b.tgz http://hl7.org/fhir/us/ecr/old-STU2.1/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 31 Oct 2024 08:40:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.phd.r4#1.1.0 ImplementationGuide for Personal Health Devices (PHD), used in remote patient monitoring (e.g., weight scales, blood pressure cuffs, glucose monitors, pulse-oximeters, etc.). (built Fri, Oct 18, 2024 13:36+0000+00:00) http://hl7.org/fhir/uv/phd/package.r4.tgz http://hl7.org/fhir/uv/phd/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 19 Oct 2024 00:59:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.phd.r4b#1.1.0 ImplementationGuide for Personal Health Devices (PHD), used in remote patient monitoring (e.g., weight scales, blood pressure cuffs, glucose monitors, pulse-oximeters, etc.). (built Fri, Oct 18, 2024 13:36+0000+00:00) http://hl7.org/fhir/uv/phd/package.r4b.tgz http://hl7.org/fhir/uv/phd/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 19 Oct 2024 00:59:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.phd.r4#2.0.0-ballot ImplementationGuide for Personal Health Devices (PHD), used in remote patient monitoring (e.g., weight scales, blood pressure cuffs, glucose monitors, pulse-oximeters, etc.). (built Fri, Aug 16, 2024 03:08+0000+00:00) http://hl7.org/fhir/uv/phd/2024Sep/package.r4.tgz http://hl7.org/fhir/uv/phd/2024Sep/package.r4.tgz HL7, Inc 4.0.0 IG Sat, 19 Oct 2024 00:58:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.phd.r4b#2.0.0-ballot ImplementationGuide for Personal Health Devices (PHD), used in remote patient monitoring (e.g., weight scales, blood pressure cuffs, glucose monitors, pulse-oximeters, etc.). (built Fri, Aug 16, 2024 03:08+0000+00:00) http://hl7.org/fhir/uv/phd/2024Sep/package.r4b.tgz http://hl7.org/fhir/uv/phd/2024Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 19 Oct 2024 00:58:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.vrdr.r4#3.0.0 Package hl7.fhir.us.vrdr.r4#3.0.0 http://hl7.org/fhir/us/vrdr/package.r4.tgz http://hl7.org/fhir/us/vrdr/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 17 Oct 2024 06:57:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.vrdr.r4b#3.0.0 Package hl7.fhir.us.vrdr.r4b#3.0.0 http://hl7.org/fhir/us/vrdr/package.r4b.tgz http://hl7.org/fhir/us/vrdr/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 17 Oct 2024 06:57:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.vrdr.r4#3.0.0-ballot Package hl7.fhir.us.vrdr.r4#3.0.0-ballot http://hl7.org/fhir/us/vrdr/2024May/package.r4.tgz http://hl7.org/fhir/us/vrdr/2024May/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 17 Oct 2024 06:55:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.vrdr.r4b#3.0.0-ballot Package hl7.fhir.us.vrdr.r4b#3.0.0-ballot http://hl7.org/fhir/us/vrdr/2024May/package.r4b.tgz http://hl7.org/fhir/us/vrdr/2024May/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 17 Oct 2024 06:55:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.vrdr.r4#2.1.0 Package hl7.fhir.us.vrdr.r4#2.1.0 http://hl7.org/fhir/us/vrdr/STU2.1/package.r4.tgz http://hl7.org/fhir/us/vrdr/STU2.1/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 17 Oct 2024 06:50:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.vrdr.r4b#2.1.0 Package hl7.fhir.us.vrdr.r4b#2.1.0 http://hl7.org/fhir/us/vrdr/STU2.1/package.r4b.tgz http://hl7.org/fhir/us/vrdr/STU2.1/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 17 Oct 2024 06:50:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.vrdr.r4#2.2.0 Package hl7.fhir.us.vrdr.r4#2.2.0 http://hl7.org/fhir/us/vrdr/STU2.2/package.r4.tgz http://hl7.org/fhir/us/vrdr/STU2.2/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 17 Oct 2024 06:48:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.vrdr.r4b#2.2.0 Package hl7.fhir.us.vrdr.r4b#2.2.0 http://hl7.org/fhir/us/vrdr/STU2.2/package.r4b.tgz http://hl7.org/fhir/us/vrdr/STU2.2/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 17 Oct 2024 06:48:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.pdmp.r4#1.0.0 US Prescription Drug Monitoring Program (PDMP) FHIR IG (built Tue, Oct 15, 2024 18:35+0000+00:00) http://hl7.org/fhir/us/pdmp/package.r4.tgz http://hl7.org/fhir/us/pdmp/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 16 Oct 2024 05:55:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.pdmp.r4b#1.0.0 US Prescription Drug Monitoring Program (PDMP) FHIR IG (built Tue, Oct 15, 2024 18:35+0000+00:00) http://hl7.org/fhir/us/pdmp/package.r4b.tgz http://hl7.org/fhir/us/pdmp/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 16 Oct 2024 05:55:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.pdmp.r4#1.0.0-ballot US Prescription Drug Monitoring Program (PDMP) FHIR IG (built Thu, Apr 4, 2024 15:32+0000+00:00) http://hl7.org/fhir/us/pdmp/2024May/package.r4.tgz http://hl7.org/fhir/us/pdmp/2024May/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 16 Oct 2024 05:54:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.pdmp.r4b#1.0.0-ballot US Prescription Drug Monitoring Program (PDMP) FHIR IG (built Thu, Apr 4, 2024 15:32+0000+00:00) http://hl7.org/fhir/us/pdmp/2024May/package.r4b.tgz http://hl7.org/fhir/us/pdmp/2024May/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 16 Oct 2024 05:54:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.bfdr.r4#2.0.0 Package hl7.fhir.us.bfdr.r4#2.0.0 http://hl7.org/fhir/us/bfdr/package.r4.tgz http://hl7.org/fhir/us/bfdr/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 16 Oct 2024 04:38:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.bfdr.r4b#2.0.0 Package hl7.fhir.us.bfdr.r4b#2.0.0 http://hl7.org/fhir/us/bfdr/package.r4b.tgz http://hl7.org/fhir/us/bfdr/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 16 Oct 2024 04:38:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.bfdr.r4#2.0.0-ballot Package hl7.fhir.us.bfdr.r4#2.0.0-ballot http://hl7.org/fhir/us/bfdr/2024Jan/package.r4.tgz http://hl7.org/fhir/us/bfdr/2024Jan/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 16 Oct 2024 04:35:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.bfdr.r4b#2.0.0-ballot Package hl7.fhir.us.bfdr.r4b#2.0.0-ballot http://hl7.org/fhir/us/bfdr/2024Jan/package.r4b.tgz http://hl7.org/fhir/us/bfdr/2024Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 16 Oct 2024 04:35:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.bfdr.r4#1.1.0 ### Description Birth and fetal death reporting includes the transmission of data from health care providers to jurisdictional vital records offices and national health statistics agencies. Data associated with the mother of the baby or delivered fetus may be communicated independently from data associated directly with the labor and delivery encounter at the responsible healthcare facility. Note that for the purposes of this guide, &quot;mother&quot; always refers to the woman who delivered the infant or fetus. In cases of surrogacy or gestational carrier, the information reported should be for the surrogate or the gestational carrier, that is, the woman who delivered the infant. Also, the national statistics agency referred to in this guide is the [National Center for Health Statistics - CDC](https://www.cdc.gov/nchs/index.htm) (NCHS). This implementation guide (IG) defines a series of Health Level Seven (HL7®) Fast Healthcare Interoperability Resources (FHIR®) profiles on the Composition resource to represent electronic birth and fetal death reporting (BFDR). It includes the content of medical/health information on live births and fetal deaths for select state and federal birth and fetal death reporting, as indicated in the [2003 Revision of the U.S. Standard Certificate of Live Birth](https://www.cdc.gov/nchs/data/dvs/birth11-03final-ACC.pdf) and the [2003 Revision of the U.S. Standard Report of Fetal Death](https://www.cdc.gov/nchs/data/dvs/FDEATH11-03finalACC.pdf). Additionally, it includes the content that is exchanged between electronic health record (EHR) systems, jurisdictions, and the Centers for Disease Control and Prevention/ National Center for Health Statistics (CDC/NCHS). ### Relationship to Other Standards This BFDR IG standard complements other vital records standards to support the expansion of information flows to and from the national statistics agency. The BFDR STU 1 drew on foundational work of early standards listed in the Background section, below. This current version of the BFDR IG is informed by : * [HL7, Vital Records Death Reporting (VRDR) FHIR Implementation Guide](http://hl7.org/fhir/us/vrdr/) * [Office of the National Coordinator for Health Information Technology (ONC), United States Core Data for Interoperability (USCDI)](https://www.healthit.gov/isa/united-states-core-data-interoperability-uscdi) ### Dependencies This implementation guide re-uses and further constrains profiles from the following guides: * [US Core Implementation Guide, STU5.0.1](http://hl7.org/fhir/us/core/STU5.0.1/) * [Vital Records Common Profiles Library](http://hl7.org/fhir/us/vr-common-library) * [Occupational Data for Health (ODH)](http://hl7.org/fhir/us/odh/) ### Audience This guide is for analysts and developers who require guidance on the use of the HL7 FHIR for providing birth and fetal death reporting information. The IG is informative to health care provider organizations, jurisdictional vital records offices, CDC/NCHS, health information exchange organizations, and other vital records fetal death reporting stakeholders. ### Background This FHIR IG builds on previous electronic data standards for transmitting vital records of death, birth, and fetal death. * [HL7, Version 2.6 Implementation Guide: Vital Records Birth and Fetal Death Reporting](https://www.hl7.org/implement/standards/product_brief.cfm?product_id=320) * [HL7, CDA® R2 Implementation Guide: Birth and Fetal Death Reporting](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=387) * [IHE , Quality, Research and Public Health Technical Framework Supplement - Birth and Fetal Death Reporting-Enhanced (BFDR-E)](https://www.ihe.net/uploadedFiles/Documents/QRPH/IHE_QRPH_Suppl_BFDR-E.pdf) This IG provides standardized data strutures for transmission of reliable and relevant clinical information to jurisdictional vital records offices and transfer of information from vital records offices to the national statistics agency. Electronic vital records work started with the HL7 Vital Records Domain Analysis Model (VR DAM), published as an Informative Specification in 2011. The VR DAM was updated in 2017 with the HL7 Cross-Paradigm Domain Analysis Model: Vital Records, Release 2, in 2018, with Release 3, and in November 2020 as Release 4. [VR DAM, Release 5](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=466) was published in May 2022. Implementers who review or reference the VR DAM should note that the active vital records FHIR IGs (such as BFDR and VRDR) may no longer aligned with the VR DAM. This FHIR IG uses the US Core profiles. Where this FHIR IG is unable to use a US Core profile, we have followed the Cross Group Projects Work Group's variance request process, and have provided the US Realm Steering Committee an approved rationale for deviation in the IG. ### How to Read This Guide This Guide is divided into several pages which are listed at the top of each page in the menu bar. * Home: Introduction and background for HL7 FHIR® Vital Records Common Profiles Library * [The Specification](the_specification.html): A technical overview of implementing the specification * [Use Cases](use_cases.html): The use cases supported by this guide * Implementer Guidance: The [worksheet Questionnaire format](patient_worksheet_questionnaires.html), [IJE Mapping](ije_mapping.html), and [Vital Records Forms Mapping](vital_records_forms_mapping.html) * [Terminology](terminology.html): A listing of the value sets used in this guide * [Downloads](downloads.html): Links to downloadable artifacts * [Change Log](change_log.html): Details of changes made in each version of this IG * [Artifact Index](artifacts.html): A list of the FHIR artifacts (profiles, examples, and value sets) defined as part of this guide * Appendices: Examples of live birth and fetal death reports and worksheets ### Other Information This is an update (STU 1.1) of the first FHIR BFDR standard. This guide is compliant with FHIR Release 4. For Clinical Safety Information please refer to the [FHIR Implementer’s Safety Checklist](http://hl7.org/fhir/safety.html). Disclaimer: All 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. (built Tue, Oct 10, 2023 13:06+0000+00:00) http://hl7.org/fhir/us/bfdr/STU1.1/package.r4.tgz http://hl7.org/fhir/us/bfdr/STU1.1/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 16 Oct 2024 04:30:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.bfdr.r4b#1.1.0 ### Description Birth and fetal death reporting includes the transmission of data from health care providers to jurisdictional vital records offices and national health statistics agencies. Data associated with the mother of the baby or delivered fetus may be communicated independently from data associated directly with the labor and delivery encounter at the responsible healthcare facility. Note that for the purposes of this guide, &quot;mother&quot; always refers to the woman who delivered the infant or fetus. In cases of surrogacy or gestational carrier, the information reported should be for the surrogate or the gestational carrier, that is, the woman who delivered the infant. Also, the national statistics agency referred to in this guide is the [National Center for Health Statistics - CDC](https://www.cdc.gov/nchs/index.htm) (NCHS). This implementation guide (IG) defines a series of Health Level Seven (HL7®) Fast Healthcare Interoperability Resources (FHIR®) profiles on the Composition resource to represent electronic birth and fetal death reporting (BFDR). It includes the content of medical/health information on live births and fetal deaths for select state and federal birth and fetal death reporting, as indicated in the [2003 Revision of the U.S. Standard Certificate of Live Birth](https://www.cdc.gov/nchs/data/dvs/birth11-03final-ACC.pdf) and the [2003 Revision of the U.S. Standard Report of Fetal Death](https://www.cdc.gov/nchs/data/dvs/FDEATH11-03finalACC.pdf). Additionally, it includes the content that is exchanged between electronic health record (EHR) systems, jurisdictions, and the Centers for Disease Control and Prevention/ National Center for Health Statistics (CDC/NCHS). ### Relationship to Other Standards This BFDR IG standard complements other vital records standards to support the expansion of information flows to and from the national statistics agency. The BFDR STU 1 drew on foundational work of early standards listed in the Background section, below. This current version of the BFDR IG is informed by : * [HL7, Vital Records Death Reporting (VRDR) FHIR Implementation Guide](http://hl7.org/fhir/us/vrdr/) * [Office of the National Coordinator for Health Information Technology (ONC), United States Core Data for Interoperability (USCDI)](https://www.healthit.gov/isa/united-states-core-data-interoperability-uscdi) ### Dependencies This implementation guide re-uses and further constrains profiles from the following guides: * [US Core Implementation Guide, STU5.0.1](http://hl7.org/fhir/us/core/STU5.0.1/) * [Vital Records Common Profiles Library](http://hl7.org/fhir/us/vr-common-library) * [Occupational Data for Health (ODH)](http://hl7.org/fhir/us/odh/) ### Audience This guide is for analysts and developers who require guidance on the use of the HL7 FHIR for providing birth and fetal death reporting information. The IG is informative to health care provider organizations, jurisdictional vital records offices, CDC/NCHS, health information exchange organizations, and other vital records fetal death reporting stakeholders. ### Background This FHIR IG builds on previous electronic data standards for transmitting vital records of death, birth, and fetal death. * [HL7, Version 2.6 Implementation Guide: Vital Records Birth and Fetal Death Reporting](https://www.hl7.org/implement/standards/product_brief.cfm?product_id=320) * [HL7, CDA® R2 Implementation Guide: Birth and Fetal Death Reporting](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=387) * [IHE , Quality, Research and Public Health Technical Framework Supplement - Birth and Fetal Death Reporting-Enhanced (BFDR-E)](https://www.ihe.net/uploadedFiles/Documents/QRPH/IHE_QRPH_Suppl_BFDR-E.pdf) This IG provides standardized data strutures for transmission of reliable and relevant clinical information to jurisdictional vital records offices and transfer of information from vital records offices to the national statistics agency. Electronic vital records work started with the HL7 Vital Records Domain Analysis Model (VR DAM), published as an Informative Specification in 2011. The VR DAM was updated in 2017 with the HL7 Cross-Paradigm Domain Analysis Model: Vital Records, Release 2, in 2018, with Release 3, and in November 2020 as Release 4. [VR DAM, Release 5](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=466) was published in May 2022. Implementers who review or reference the VR DAM should note that the active vital records FHIR IGs (such as BFDR and VRDR) may no longer aligned with the VR DAM. This FHIR IG uses the US Core profiles. Where this FHIR IG is unable to use a US Core profile, we have followed the Cross Group Projects Work Group's variance request process, and have provided the US Realm Steering Committee an approved rationale for deviation in the IG. ### How to Read This Guide This Guide is divided into several pages which are listed at the top of each page in the menu bar. * Home: Introduction and background for HL7 FHIR® Vital Records Common Profiles Library * [The Specification](the_specification.html): A technical overview of implementing the specification * [Use Cases](use_cases.html): The use cases supported by this guide * Implementer Guidance: The [worksheet Questionnaire format](patient_worksheet_questionnaires.html), [IJE Mapping](ije_mapping.html), and [Vital Records Forms Mapping](vital_records_forms_mapping.html) * [Terminology](terminology.html): A listing of the value sets used in this guide * [Downloads](downloads.html): Links to downloadable artifacts * [Change Log](change_log.html): Details of changes made in each version of this IG * [Artifact Index](artifacts.html): A list of the FHIR artifacts (profiles, examples, and value sets) defined as part of this guide * Appendices: Examples of live birth and fetal death reports and worksheets ### Other Information This is an update (STU 1.1) of the first FHIR BFDR standard. This guide is compliant with FHIR Release 4. For Clinical Safety Information please refer to the [FHIR Implementer’s Safety Checklist](http://hl7.org/fhir/safety.html). Disclaimer: All 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. (built Tue, Oct 10, 2023 13:06+0000+00:00) http://hl7.org/fhir/us/bfdr/STU1.1/package.r4b.tgz http://hl7.org/fhir/us/bfdr/STU1.1/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 16 Oct 2024 04:30:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.vr-common-library.r4#2.0.0 Package hl7.fhir.us.vr-common-library.r4#2.0.0 http://hl7.org/fhir/us/vr-common-library/package.r4.tgz http://hl7.org/fhir/us/vr-common-library/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 12 Oct 2024 06:14:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.vr-common-library.r4b#2.0.0 Package hl7.fhir.us.vr-common-library.r4b#2.0.0 http://hl7.org/fhir/us/vr-common-library/package.r4b.tgz http://hl7.org/fhir/us/vr-common-library/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 12 Oct 2024 06:14:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.vr-common-library.r4#2.0.0-ballot Package hl7.fhir.us.vr-common-library.r4#2.0.0-ballot http://hl7.org/fhir/us/vr-common-library/2024Jan/package.r4.tgz http://hl7.org/fhir/us/vr-common-library/2024Jan/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 12 Oct 2024 06:12:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.vr-common-library.r4b#2.0.0-ballot Package hl7.fhir.us.vr-common-library.r4b#2.0.0-ballot http://hl7.org/fhir/us/vr-common-library/2024Jan/package.r4b.tgz http://hl7.org/fhir/us/vr-common-library/2024Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 12 Oct 2024 06:12:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.vr-common-library.r4#1.1.0 ### Description This guide is a Fast Healthcare Interoperability Resources (FHIR) Profiles Library to support the needs of multiple vital records implementation guides (IGs). It does not provide any use case (scenario) specific content or additional guidance on how to use these artifacts, but serves as a source for a standard set of profiles for reuse in multiple use case specific IGs focusing on the exchange of vital records information. Implementation details such as how and when to use a given artifact will be supplied in these guides. ### Background Two FHIR IG projects, [Birth Defects](https://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=1532) and [Birth and Fetal Death Reporting](http://hl7.org/fhir/us/bfdr/), share many common data elements or concepts. The initial scope of this Vital Records Common Profiles Library included data elements common to these two FHIR projects in a US Realm framework. The current update adds data elements shared by two other vital records FHIR IGs, [Vital Records Death Reporting (VRDR)](http://hl7.org/fhir/us/vrdr/), and the [Medicolegal Death Investigation (MDI)](http://hl7.org/fhir/us/mdi/). Many of the data elements in the vital records IGs (BFDR, VRDR, and this Library) can be identified using the IJE (Inter-Jurisdictional Exchange) data element names (codes). The IJE codes are used for exchange of data among jurisdictions and with authorized data partners, such as NCHS. NCHS has implemented IJE codes for exchange of mortality data with jurisdictions via the VRDR IG, however, the use of IJE codes has not yet been implemented for birth and fetal death reporting to NCHS. [FHIR profile mappings to the IJE format are available for Mortality, Natality, and Fetal Death.](https://github.com/HL7/vr-common-library/raw/master/input/mapping/IJE_File_Layouts_Version_2021_FHIR-2023-02-22-All-Combined.xlsx) The mappings are based on information from: * [200X NCHS Mortality - Demographic File Description](https://www.cdc.gov/nchs/data/dvs/200XMOR_web_with%20clearance%20revisions-acc.pdf) * [200X NCHS Natality File Description](https://www.cdc.gov/nchs/data/dvs/200XNAT_web_with%20clearance%20revisions-acc.pdf) * [200X NCHS Fetal Death File Description](https://www.cdc.gov/nchs/data/dvs/200XFET_web_with%20clearance%20revisions-acc.pdf) A FHIR common profiles library avoids defining the same data element multiple times across IGs by allowing each IG to reference them. This profile library will provide a standard framework for vital records information to support interoperability among public health systems and reduce provider and implementer burden. This FHIR IG uses US Core profiles. Where unable to use a US Core profile, we have followed the Cross-Group Projects Work Group's variance request process and have provided the US Realm Steering Committee an approved rationale for deviation in the IG. For Clinical Safety Information please refer to the [FHIR Implementer’s Safety Checklist](http://hl7.org/fhir/safety.html). ### How to Read This Guide This Guide is divided into several pages which are listed at the top of each page in the menu bar. * Home: The introduction and background for HL7® FHIR® Vital Records Common Profiles Library * [Terminology](terminology.html): A listing of the value sets used in this guide * [Downloads](downloads.html): Links to downloadable artifacts * [Change Log](change_log.html): Details of changes made in each version of this IG * [Artifact Index](artifacts.html): A list of the defined FHIR artifacts (profiles, examples, and value sets) in this guide (built Fri, Oct 6, 2023 12:58+0000+00:00) http://hl7.org/fhir/us/vr-common-library/STU1.1/package.r4.tgz http://hl7.org/fhir/us/vr-common-library/STU1.1/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 12 Oct 2024 06:10:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.vr-common-library.r4b#1.1.0 ### Description This guide is a Fast Healthcare Interoperability Resources (FHIR) Profiles Library to support the needs of multiple vital records implementation guides (IGs). It does not provide any use case (scenario) specific content or additional guidance on how to use these artifacts, but serves as a source for a standard set of profiles for reuse in multiple use case specific IGs focusing on the exchange of vital records information. Implementation details such as how and when to use a given artifact will be supplied in these guides. ### Background Two FHIR IG projects, [Birth Defects](https://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=1532) and [Birth and Fetal Death Reporting](http://hl7.org/fhir/us/bfdr/), share many common data elements or concepts. The initial scope of this Vital Records Common Profiles Library included data elements common to these two FHIR projects in a US Realm framework. The current update adds data elements shared by two other vital records FHIR IGs, [Vital Records Death Reporting (VRDR)](http://hl7.org/fhir/us/vrdr/), and the [Medicolegal Death Investigation (MDI)](http://hl7.org/fhir/us/mdi/). Many of the data elements in the vital records IGs (BFDR, VRDR, and this Library) can be identified using the IJE (Inter-Jurisdictional Exchange) data element names (codes). The IJE codes are used for exchange of data among jurisdictions and with authorized data partners, such as NCHS. NCHS has implemented IJE codes for exchange of mortality data with jurisdictions via the VRDR IG, however, the use of IJE codes has not yet been implemented for birth and fetal death reporting to NCHS. [FHIR profile mappings to the IJE format are available for Mortality, Natality, and Fetal Death.](https://github.com/HL7/vr-common-library/raw/master/input/mapping/IJE_File_Layouts_Version_2021_FHIR-2023-02-22-All-Combined.xlsx) The mappings are based on information from: * [200X NCHS Mortality - Demographic File Description](https://www.cdc.gov/nchs/data/dvs/200XMOR_web_with%20clearance%20revisions-acc.pdf) * [200X NCHS Natality File Description](https://www.cdc.gov/nchs/data/dvs/200XNAT_web_with%20clearance%20revisions-acc.pdf) * [200X NCHS Fetal Death File Description](https://www.cdc.gov/nchs/data/dvs/200XFET_web_with%20clearance%20revisions-acc.pdf) A FHIR common profiles library avoids defining the same data element multiple times across IGs by allowing each IG to reference them. This profile library will provide a standard framework for vital records information to support interoperability among public health systems and reduce provider and implementer burden. This FHIR IG uses US Core profiles. Where unable to use a US Core profile, we have followed the Cross-Group Projects Work Group's variance request process and have provided the US Realm Steering Committee an approved rationale for deviation in the IG. For Clinical Safety Information please refer to the [FHIR Implementer’s Safety Checklist](http://hl7.org/fhir/safety.html). ### How to Read This Guide This Guide is divided into several pages which are listed at the top of each page in the menu bar. * Home: The introduction and background for HL7® FHIR® Vital Records Common Profiles Library * [Terminology](terminology.html): A listing of the value sets used in this guide * [Downloads](downloads.html): Links to downloadable artifacts * [Change Log](change_log.html): Details of changes made in each version of this IG * [Artifact Index](artifacts.html): A list of the defined FHIR artifacts (profiles, examples, and value sets) in this guide (built Fri, Oct 6, 2023 12:58+0000+00:00) http://hl7.org/fhir/us/vr-common-library/STU1.1/package.r4b.tgz http://hl7.org/fhir/us/vr-common-library/STU1.1/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 12 Oct 2024 06:10:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.core.v700#7.0.0 Package hl7.fhir.us.core.v700#7.0.0 http://hl7.org/fhir/us/core/v700/package.tgz http://hl7.org/fhir/us/core/v700/package.tgz HL7, Inc 4.0.1 IG Sat, 07 Sep 2024 09:08:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.core.v311#3.1.1 Package hl7.fhir.us.core.v311#3.1.1 http://hl7.org/fhir/us/core/v311/package.tgz http://hl7.org/fhir/us/core/v311/package.tgz HL7, Inc 4.0.1 IG Thu, 05 Sep 2024 20:45:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.r6.corexml#6.0.0-ballot2 FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (XML) (built Mon, Aug 12, 2024 16:52+0800+08:00) http://hl7.org/fhir/6.0.0-ballot2/hl7.fhir.r6.corexml.tgz http://hl7.org/fhir/6.0.0-ballot2/hl7.fhir.r6.corexml.tgz HL7, Inc 6.0.0-ballot2 IG Wed, 04 Sep 2024 22:15:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.r6.corexml#6.0.0-ballot1 FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (XML) (built Mon, Dec 18, 2023 15:12+1100+11:00) http://hl7.org/fhir/6.0.0-ballot1/hl7.fhir.r6.corexml.tgz http://hl7.org/fhir/6.0.0-ballot1/hl7.fhir.r6.corexml.tgz HL7, Inc 6.0.0-ballot1 IG Wed, 04 Sep 2024 21:33:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-deqm.r4#5.0.0-ballot Package hl7.fhir.us.davinci-deqm.r4#5.0.0-ballot http://hl7.org/fhir/us/davinci-deqm/2024Sep/package.r4.tgz http://hl7.org/fhir/us/davinci-deqm/2024Sep/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 28 Aug 2024 07:15:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-deqm.r4b#5.0.0-ballot Package hl7.fhir.us.davinci-deqm.r4b#5.0.0-ballot http://hl7.org/fhir/us/davinci-deqm/2024Sep/package.r4b.tgz http://hl7.org/fhir/us/davinci-deqm/2024Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 28 Aug 2024 07:15:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.sdoh-clinicalcare.r4#2.0.0 Social Determinants of Health (SDOH) are increasingly being recognized as essential factors that influence healthcare outcomes. This HL7 Implementation Guide (IG) defines how to exchange SDOH content defined by the [Gravity Project]( https://confluence.hl7.org/display/GRAV/The+Gravity+Project) using the HL7 FHIR standard. It defines how to represent coded content used to support the following care activities: screening, clinical assessment/diagnosis, goal setting, and the planning and performing of interventions. This IG addresses the need to gather SDOH information in multiple settings, share that information between stakeholders, and exchange referrals between organizations to address specific social risk needs, all with appropriate patient consent. In addition, the IG demonstrates how to share clinical data to support secondary purposes such as population health, quality, and research. The guide supports the following use cases: * Document SDOH data in conjunction with patient encounters with providers, payers, and community services * Document and track SDOH-related interventions to completion * Identify cohorts of individuals that have a common relationship to another entity (e.g., covered by the same payer) This implementation guide was developed by the Gravity Project, which specifically focuses on using HL7 FHIR to define standards for the exchange of SDOH-related information. Both the project and this implementation guide are focused on the U.S. environment. This implementation guide leverages content from the [US Core Implementation Guide](https://www.hl7.org/fhir/us/core/) and binds to US-specific terminology. However, the basic constructs and interaction patterns may well be applicable outside the U.S. Additional information regarding the background and use of this IG can be found on the [Gravity Confluence Technology Pages](https://confluence.hl7.org/display/GRAV/Technical+Workstream+Dashboard) ### Content and organization The implementation guide is organized into the following sections: * Background: Includes [Gravity Background](gravity_background.html), [SDOH Clinical Care Background](sdoh_clinical_care_background.html), [Functional Use Cases](functional_use_cases.html), and [Technical Background](technical_background.html), thesedescribe the environment in which this implementation guide establishes standards for information exchange * [Change History](stu2_ballot_changes.html) describes the changes included in the STU 2 ballot version of the IG and [Change History](stu2_publication_changes.html) describes the changes applied to the balloted version * Context: Describes the [Survey Instrument Support](survey_instrument_support.html),[ QuestionnaireResponse Mapping Instructions](mapping_instructions.html), [Support for Multiple Domains](support_for_multiple_domains.html), [Exchange Workflow](exchange_workflow.html) and [Synchronizing Applications with API Data Sources](synchronizing_applications_with_api_data_sources.html) that details a high-level overview of expected process flow * Specifications: Provides an overview of the [FHIR Artifacts](fhir_artifacts_overview.html) defined and used in this IG, [Checking Task Status](checking_task_status.html) to describe managing task status, [Privacy and Security](privacy_and_security.html) issues, [MustSupport and Missing Data](mustsupport_and_missing_data.html) concepts and [Draft Specifications for Personal Characteristics](draft_specifications_for_personal_characteristics.html) * [Downloads](downloads.html): Provides for the download of various IG related artifacts * [Credits](credits.html): Identifies the individuals and organizations involved in developing this implementation guide * [Artifacts Index](artifacts.html): Introduces and provides links to the FHIR R4 profiles, examples and other FHIR artifacts used in this implementation guide ### Note to Implementers Implementers should pay specific attention to the following sections: * [Technical Background](technical_background.html) if the implementer needs basic FHIR information references * [Survey Instrument Support](survey_instrument_support.html), and [ QuestionnaireResponse Mapping Instructions](mapping_instructions.html) if implementing support for structured assessment instruments * [Support for Multiple Domains](support_for_multiple_domains.html) to understand this IG's approach to domain specific value sets * [Exchange Workflow diagram](exchange_workflow.html) to understand the exchange workflows * [Synchronizing Applications with API Data Sources](synchronizing_applications_with_api_data_sources.html) that describes the suggested method for synchronizing patient/client or Community Based Organization applications with referral systems FHIR APIs * [FHIR Artifacts](fhir_artifacts_overview.html) to understand the individual FHIR artifacts described in this IG * [Privacy and Security](privacy_and_security.html) for implementers that are concerned with privacy and security aspects related to implementing the information exchanges defined in this IG * [MustSupport and Missing Data](mustsupport_and_missing_data.html) to understand the interpretation of the MustSupport flags and the treatment of Missing Data used in this IG * [Draft Specifications for Personal Characteristics](draft_specifications_for_personal_characteristics.html) for an introduction to draft observation profiles to exchange personal characteristics data, which includes the source and method of acquisition * [Artifacts Index](artifacts.html) provides easy access for all implementers the FHIR R4 profiles, examples and other FHIR artifacts defined in this implementation guide and linked from this section -- this section also includes details for the declared capability statements for espective servers and clients * [Downloads](downloads.html) links to allow implementers to download the IG and various artifacts ### Support for external terminologies for ServiceRequest and Procedure If implementers of this IG wish to use terminologies that are not part of the required value sets for specific elements that have a type of CodableConcept (such as ServiceRequest.code and Procedure.code) they may include a specific Coding that specifies a system (URL that is defined and supported by the terminology author) as well as the specific code (define in the terminology) as long as the meaning of the code is a concept that is logically the same as, or contained in the concept, of the required code. The following is an example for a ServiceRequest or Procedure where the external terminology URL is : http://terminologysystem and the code is : SummerProgram "code" : { "coding" : [ { "system" : "http://snomed.info/sct", "code" : "467681000124101", "display" : "Assistance with application for Summer Food Service Program" } ] }, { "coding" : [ { "system" : "http://terminologysystem", "code" : "SummerProgram", "display" : "Summer Food Service Program" } ] } ], ### Intellectual Property {% include ip-statements.xhtml %} ### Cross Version Analysis {% include cross-version-analysis.xhtml %} ### Dependencies {% include dependency-table.xhtml %} ### Globals {% include globals-table.xhtml %} (built Mon, Nov 21, 2022 18:33+0000+00:00) http://hl7.org/fhir/us/sdoh-clinicalcare/STU2/package.r4.tgz http://hl7.org/fhir/us/sdoh-clinicalcare/STU2/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 28 Aug 2024 03:48:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.sdoh-clinicalcare.r4b#2.0.0 Social Determinants of Health (SDOH) are increasingly being recognized as essential factors that influence healthcare outcomes. This HL7 Implementation Guide (IG) defines how to exchange SDOH content defined by the [Gravity Project]( https://confluence.hl7.org/display/GRAV/The+Gravity+Project) using the HL7 FHIR standard. It defines how to represent coded content used to support the following care activities: screening, clinical assessment/diagnosis, goal setting, and the planning and performing of interventions. This IG addresses the need to gather SDOH information in multiple settings, share that information between stakeholders, and exchange referrals between organizations to address specific social risk needs, all with appropriate patient consent. In addition, the IG demonstrates how to share clinical data to support secondary purposes such as population health, quality, and research. The guide supports the following use cases: * Document SDOH data in conjunction with patient encounters with providers, payers, and community services * Document and track SDOH-related interventions to completion * Identify cohorts of individuals that have a common relationship to another entity (e.g., covered by the same payer) This implementation guide was developed by the Gravity Project, which specifically focuses on using HL7 FHIR to define standards for the exchange of SDOH-related information. Both the project and this implementation guide are focused on the U.S. environment. This implementation guide leverages content from the [US Core Implementation Guide](https://www.hl7.org/fhir/us/core/) and binds to US-specific terminology. However, the basic constructs and interaction patterns may well be applicable outside the U.S. Additional information regarding the background and use of this IG can be found on the [Gravity Confluence Technology Pages](https://confluence.hl7.org/display/GRAV/Technical+Workstream+Dashboard) ### Content and organization The implementation guide is organized into the following sections: * Background: Includes [Gravity Background](gravity_background.html), [SDOH Clinical Care Background](sdoh_clinical_care_background.html), [Functional Use Cases](functional_use_cases.html), and [Technical Background](technical_background.html), thesedescribe the environment in which this implementation guide establishes standards for information exchange * [Change History](stu2_ballot_changes.html) describes the changes included in the STU 2 ballot version of the IG and [Change History](stu2_publication_changes.html) describes the changes applied to the balloted version * Context: Describes the [Survey Instrument Support](survey_instrument_support.html),[ QuestionnaireResponse Mapping Instructions](mapping_instructions.html), [Support for Multiple Domains](support_for_multiple_domains.html), [Exchange Workflow](exchange_workflow.html) and [Synchronizing Applications with API Data Sources](synchronizing_applications_with_api_data_sources.html) that details a high-level overview of expected process flow * Specifications: Provides an overview of the [FHIR Artifacts](fhir_artifacts_overview.html) defined and used in this IG, [Checking Task Status](checking_task_status.html) to describe managing task status, [Privacy and Security](privacy_and_security.html) issues, [MustSupport and Missing Data](mustsupport_and_missing_data.html) concepts and [Draft Specifications for Personal Characteristics](draft_specifications_for_personal_characteristics.html) * [Downloads](downloads.html): Provides for the download of various IG related artifacts * [Credits](credits.html): Identifies the individuals and organizations involved in developing this implementation guide * [Artifacts Index](artifacts.html): Introduces and provides links to the FHIR R4 profiles, examples and other FHIR artifacts used in this implementation guide ### Note to Implementers Implementers should pay specific attention to the following sections: * [Technical Background](technical_background.html) if the implementer needs basic FHIR information references * [Survey Instrument Support](survey_instrument_support.html), and [ QuestionnaireResponse Mapping Instructions](mapping_instructions.html) if implementing support for structured assessment instruments * [Support for Multiple Domains](support_for_multiple_domains.html) to understand this IG's approach to domain specific value sets * [Exchange Workflow diagram](exchange_workflow.html) to understand the exchange workflows * [Synchronizing Applications with API Data Sources](synchronizing_applications_with_api_data_sources.html) that describes the suggested method for synchronizing patient/client or Community Based Organization applications with referral systems FHIR APIs * [FHIR Artifacts](fhir_artifacts_overview.html) to understand the individual FHIR artifacts described in this IG * [Privacy and Security](privacy_and_security.html) for implementers that are concerned with privacy and security aspects related to implementing the information exchanges defined in this IG * [MustSupport and Missing Data](mustsupport_and_missing_data.html) to understand the interpretation of the MustSupport flags and the treatment of Missing Data used in this IG * [Draft Specifications for Personal Characteristics](draft_specifications_for_personal_characteristics.html) for an introduction to draft observation profiles to exchange personal characteristics data, which includes the source and method of acquisition * [Artifacts Index](artifacts.html) provides easy access for all implementers the FHIR R4 profiles, examples and other FHIR artifacts defined in this implementation guide and linked from this section -- this section also includes details for the declared capability statements for espective servers and clients * [Downloads](downloads.html) links to allow implementers to download the IG and various artifacts ### Support for external terminologies for ServiceRequest and Procedure If implementers of this IG wish to use terminologies that are not part of the required value sets for specific elements that have a type of CodableConcept (such as ServiceRequest.code and Procedure.code) they may include a specific Coding that specifies a system (URL that is defined and supported by the terminology author) as well as the specific code (define in the terminology) as long as the meaning of the code is a concept that is logically the same as, or contained in the concept, of the required code. The following is an example for a ServiceRequest or Procedure where the external terminology URL is : http://terminologysystem and the code is : SummerProgram "code" : { "coding" : [ { "system" : "http://snomed.info/sct", "code" : "467681000124101", "display" : "Assistance with application for Summer Food Service Program" } ] }, { "coding" : [ { "system" : "http://terminologysystem", "code" : "SummerProgram", "display" : "Summer Food Service Program" } ] } ], ### Intellectual Property {% include ip-statements.xhtml %} ### Cross Version Analysis {% include cross-version-analysis.xhtml %} ### Dependencies {% include dependency-table.xhtml %} ### Globals {% include globals-table.xhtml %} (built Mon, Nov 21, 2022 18:33+0000+00:00) http://hl7.org/fhir/us/sdoh-clinicalcare/STU2/package.r4b.tgz http://hl7.org/fhir/us/sdoh-clinicalcare/STU2/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 28 Aug 2024 03:48:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.sdoh-clinicalcare.r4#2.2.0 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 Tue, Aug 27, 2024 16:48+0000+00:00) http://hl7.org/fhir/us/sdoh-clinicalcare/STU2.2/package.r4.tgz http://hl7.org/fhir/us/sdoh-clinicalcare/STU2.2/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 28 Aug 2024 03:47:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.sdoh-clinicalcare.r4b#2.2.0 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 Tue, Aug 27, 2024 16:48+0000+00:00) http://hl7.org/fhir/us/sdoh-clinicalcare/STU2.2/package.r4b.tgz http://hl7.org/fhir/us/sdoh-clinicalcare/STU2.2/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 28 Aug 2024 03:47:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.sdoh-clinicalcare.r4#2.1.0 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, Jul 27, 2023 20:34+0000+00:00) http://hl7.org/fhir/us/sdoh-clinicalcare/STU2.1/package.r4.tgz http://hl7.org/fhir/us/sdoh-clinicalcare/STU2.1/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 28 Aug 2024 03:47:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.sdoh-clinicalcare.r4b#2.1.0 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, Jul 27, 2023 20:34+0000+00:00) http://hl7.org/fhir/us/sdoh-clinicalcare/STU2.1/package.r4b.tgz http://hl7.org/fhir/us/sdoh-clinicalcare/STU2.1/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 28 Aug 2024 03:47:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.core.r4#7.0.0 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. These 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 Wed, May 8, 2024 15:33+0000+00:00) http://hl7.org/fhir/us/core/STU7/package.r4.tgz http://hl7.org/fhir/us/core/STU7/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 23 Aug 2024 08:08:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.core.r4b#7.0.0 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. These 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 Wed, May 8, 2024 15:33+0000+00:00) http://hl7.org/fhir/us/core/STU7/package.r4b.tgz http://hl7.org/fhir/us/core/STU7/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 23 Aug 2024 08:08:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.codex-radiation-therapy.r4#2.0.0-ballot 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) http://hl7.org/fhir/us/codex-radiation-therapy/2024May/package.r4.tgz http://hl7.org/fhir/us/codex-radiation-therapy/2024May/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 23 Aug 2024 08:07:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.codex-radiation-therapy.r4b#2.0.0-ballot 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) http://hl7.org/fhir/us/codex-radiation-therapy/2024May/package.r4b.tgz http://hl7.org/fhir/us/codex-radiation-therapy/2024May/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 23 Aug 2024 08:07:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.subscriptions-backport.r4#1.2.0-ballot 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) http://hl7.org/fhir/uv/subscriptions-backport/2024Jan/package.r4.tgz http://hl7.org/fhir/uv/subscriptions-backport/2024Jan/package.r4.tgz HL7, Inc 4.0.0 IG Fri, 23 Aug 2024 08:07:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.subscriptions-backport.r4b#1.2.0-ballot 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) http://hl7.org/fhir/uv/subscriptions-backport/2024Jan/package.r4b.tgz http://hl7.org/fhir/uv/subscriptions-backport/2024Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 23 Aug 2024 08:07:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.ihe-sdc-ecc.r4#1.0.0 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) http://hl7.org/fhir/uv/ihe-sdc-ecc/STU1/package.r4.tgz http://hl7.org/fhir/uv/ihe-sdc-ecc/STU1/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 23 Aug 2024 08:05:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.ihe-sdc-ecc.r4b#1.0.0 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) http://hl7.org/fhir/uv/ihe-sdc-ecc/STU1/package.r4b.tgz http://hl7.org/fhir/uv/ihe-sdc-ecc/STU1/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 23 Aug 2024 08:05:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.crmi.r4#1.0.0-snapshot 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 Sat, Apr 6, 2024 06:47+1100+11:00) http://hl7.org/fhir/uv/crmi/1.0.0-snapshot/package.r4.tgz http://hl7.org/fhir/uv/crmi/1.0.0-snapshot/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 23 Aug 2024 08:04:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.crmi.r4b#1.0.0-snapshot 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 Sat, Apr 6, 2024 06:47+1100+11:00) http://hl7.org/fhir/uv/crmi/1.0.0-snapshot/package.r4b.tgz http://hl7.org/fhir/uv/crmi/1.0.0-snapshot/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 23 Aug 2024 08:04:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.cql.r4#1.0.0-snapshot 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 Sat, Apr 6, 2024 09:37+1100+11:00) http://hl7.org/fhir/uv/cql/1.0.0-snapshot/package.r4.tgz http://hl7.org/fhir/uv/cql/1.0.0-snapshot/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 23 Aug 2024 08:04:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.cql.r4b#1.0.0-snapshot 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 Sat, Apr 6, 2024 09:37+1100+11:00) http://hl7.org/fhir/uv/cql/1.0.0-snapshot/package.r4b.tgz http://hl7.org/fhir/uv/cql/1.0.0-snapshot/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 23 Aug 2024 08:04:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.physical-activity.r4#1.0.0-ballot This implementation guide provides standardization around patient physical activity, including:&#x0a;* measures for recording a patient's level of physical activity;&#x0a;* measures to support assertions of physical activity, including device-based measures;&#x0a;* goals and care plans related to improving a patient's physical activity level;&#x0a;* orders for interventions seeking to improve a patient's physical activity level; and&#x0a;* processes to support closing the loop and evaluating the success of such interventions. (built Tue, Mar 28, 2023 18:26+0000+00:00) http://hl7.org/fhir/us/physical-activity/2023May/package.r4.tgz http://hl7.org/fhir/us/physical-activity/2023May/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 23 Aug 2024 08:01:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.physical-activity.r4b#1.0.0-ballot This implementation guide provides standardization around patient physical activity, including:&#x0a;* measures for recording a patient's level of physical activity;&#x0a;* measures to support assertions of physical activity, including device-based measures;&#x0a;* goals and care plans related to improving a patient's physical activity level;&#x0a;* orders for interventions seeking to improve a patient's physical activity level; and&#x0a;* processes to support closing the loop and evaluating the success of such interventions. (built Tue, Mar 28, 2023 18:26+0000+00:00) http://hl7.org/fhir/us/physical-activity/2023May/package.r4b.tgz http://hl7.org/fhir/us/physical-activity/2023May/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 23 Aug 2024 08:01:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.registry-protocols.r4#1.0.0 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) http://hl7.org/fhir/us/registry-protocols/STU1/package.r4.tgz http://hl7.org/fhir/us/registry-protocols/STU1/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 23 Aug 2024 08:01:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.registry-protocols.r4b#1.0.0 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) http://hl7.org/fhir/us/registry-protocols/STU1/package.r4b.tgz http://hl7.org/fhir/us/registry-protocols/STU1/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 23 Aug 2024 08:01:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.eltss.r4b#2.0.0-ballot 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) http://hl7.org/fhir/us/eltss/2024Jan/package.r4b.tgz http://hl7.org/fhir/us/eltss/2024Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 23 Aug 2024 07:58:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.eltss.r4#2.0.0-ballot 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) http://hl7.org/fhir/us/eltss/2024Jan/package.r4.tgz http://hl7.org/fhir/us/eltss/2024Jan/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 23 Aug 2024 07:57:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.core.3.1.1#3.1.1 Package hl7.fhir.us.core.3.1.1#3.1.1 http://hl7.org/fhir/us/core/reuse/3.1.1/package.tgz http://hl7.org/fhir/us/core/reuse/3.1.1/package.tgz HL7, Inc 4.0.1 IG Fri, 23 Aug 2024 07:53:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.udap-security.r4#1.1.0 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 Wed, Aug 21, 2024 13:18+0000+00:00) http://hl7.org/fhir/us/udap-security/package.r4.tgz http://hl7.org/fhir/us/udap-security/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 21 Aug 2024 23:26:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.udap-security.r4b#1.1.0 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 Wed, Aug 21, 2024 13:18+0000+00:00) http://hl7.org/fhir/us/udap-security/package.r4b.tgz http://hl7.org/fhir/us/udap-security/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 21 Aug 2024 23:26:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.medication-rems.r4#1.0.0-ballot FHIR implementation options and guidance for medication REMS participants (built Fri, Apr 5, 2024 14:52+0000+00:00) http://hl7.org/fhir/us/medication-rems/2024May/package.r4.tgz http://hl7.org/fhir/us/medication-rems/2024May/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 20 Aug 2024 06:20:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.medication-rems.r4b#1.0.0-ballot FHIR implementation options and guidance for medication REMS participants (built Fri, Apr 5, 2024 14:52+0000+00:00) http://hl7.org/fhir/us/medication-rems/2024May/package.r4b.tgz http://hl7.org/fhir/us/medication-rems/2024May/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 20 Aug 2024 06:20:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.medication-rems.r4#1.0.0 FHIR implementation options and guidance for medication REMS participants (built Mon, Aug 19, 2024 20:02+0000+00:00) http://hl7.org/fhir/us/medication-rems/STU1/package.r4.tgz http://hl7.org/fhir/us/medication-rems/STU1/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 20 Aug 2024 06:20:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.medication-rems.r4b#1.0.0 FHIR implementation options and guidance for medication REMS participants (built Mon, Aug 19, 2024 20:02+0000+00:00) http://hl7.org/fhir/us/medication-rems/STU1/package.r4b.tgz http://hl7.org/fhir/us/medication-rems/STU1/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 20 Aug 2024 06:20:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.shorthand.r4#3.0.0-ballot 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) http://hl7.org/fhir/uv/shorthand/2023Sep/package.r4.tgz http://hl7.org/fhir/uv/shorthand/2023Sep/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 20 Aug 2024 01:28:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.shorthand.r4b#3.0.0-ballot 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) http://hl7.org/fhir/uv/shorthand/2023Sep/package.r4b.tgz http://hl7.org/fhir/uv/shorthand/2023Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 20 Aug 2024 01:28:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.shorthand.r4#3.0.0 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) http://hl7.org/fhir/uv/shorthand/package.r4.tgz http://hl7.org/fhir/uv/shorthand/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 20 Aug 2024 01:28:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.shorthand.r4b#3.0.0 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) http://hl7.org/fhir/uv/shorthand/package.r4b.tgz http://hl7.org/fhir/uv/shorthand/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 20 Aug 2024 01:28:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.lab-report.r4#1.0.0-ballot This guide describes how the Laboratory Report can be represented in the UV REALM. (built Wed, Aug 14, 2024 20:47+0000+00:00) http://hl7.org/fhir/uv/lab-report/2024Sep/package.r4.tgz http://hl7.org/fhir/uv/lab-report/2024Sep/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 15 Aug 2024 07:05:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.lab-report.r4b#1.0.0-ballot This guide describes how the Laboratory Report can be represented in the UV REALM. (built Wed, Aug 14, 2024 20:47+0000+00:00) http://hl7.org/fhir/uv/lab-report/2024Sep/package.r4b.tgz http://hl7.org/fhir/uv/lab-report/2024Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 15 Aug 2024 07:05:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pdex.r4#2.1.0-ballot This specification has undergone ballot and connectathon testing. It is expected to continue to evolve, possibly significantly, as part of that process. Feedback 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. This 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. [Financial Management](https://confluence.hl7.org/display/FM/Financial+Management+Home) is the Sponsoring Work Group for this Implementation Guide. **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.** The 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_ andin STU2.1 the IG has been expanded to meet the requirements of the CMS Prior Authorization Rule (CMS-0057). This 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. This IG covers the exchange of: - Claims-based information (without financials) - Clinical Information (such as Lab Results, Allergies and Conditions) - Prior Authorization information This 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. This IG covers the exchange of a Member's Health History in the following scenarios: - Provider requested exchange using SMART-on-FHIR Bulk exchange - Health Plan Exchange using SMART-on-FHIR - Member-authorized Health Plan to Health Plan exchange - Member-authorized Health Plan to Third-Party Application exchange The latter two scenarios are provided to meet the requirements identified in the CMS Interoperability and Patient Access Final Rule. **There are items in this guide that are subject to update**. This includes: - Value Sets - Vocabularies (X12, NUBC etc.) - Examples **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). See the [Table of Contents](toc.html) for more information. (built Wed, Aug 14, 2024 19:57+0000+00:00) http://hl7.org/fhir/us/davinci-pdex/2024SEP/package.r4.tgz http://hl7.org/fhir/us/davinci-pdex/2024SEP/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 15 Aug 2024 06:31:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pdex.r4b#2.1.0-ballot This specification has undergone ballot and connectathon testing. It is expected to continue to evolve, possibly significantly, as part of that process. Feedback 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. This 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. [Financial Management](https://confluence.hl7.org/display/FM/Financial+Management+Home) is the Sponsoring Work Group for this Implementation Guide. **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.** The 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_ andin STU2.1 the IG has been expanded to meet the requirements of the CMS Prior Authorization Rule (CMS-0057). This 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. This IG covers the exchange of: - Claims-based information (without financials) - Clinical Information (such as Lab Results, Allergies and Conditions) - Prior Authorization information This 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. This IG covers the exchange of a Member's Health History in the following scenarios: - Provider requested exchange using SMART-on-FHIR Bulk exchange - Health Plan Exchange using SMART-on-FHIR - Member-authorized Health Plan to Health Plan exchange - Member-authorized Health Plan to Third-Party Application exchange The latter two scenarios are provided to meet the requirements identified in the CMS Interoperability and Patient Access Final Rule. **There are items in this guide that are subject to update**. This includes: - Value Sets - Vocabularies (X12, NUBC etc.) - Examples **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). See the [Table of Contents](toc.html) for more information. (built Wed, Aug 14, 2024 19:57+0000+00:00) http://hl7.org/fhir/us/davinci-pdex/2024SEP/package.r4b.tgz http://hl7.org/fhir/us/davinci-pdex/2024SEP/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 15 Aug 2024 06:31:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.termchangeset.r4#1.0.0-ballot 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) http://hl7.org/fhir/uv/termchangeset/2024Sep/package.r4.tgz http://hl7.org/fhir/uv/termchangeset/2024Sep/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 15 Aug 2024 01:08:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.termchangeset.r4b#1.0.0-ballot 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) http://hl7.org/fhir/uv/termchangeset/2024Sep/package.r4b.tgz http://hl7.org/fhir/uv/termchangeset/2024Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 15 Aug 2024 01:08:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.smp.r4#1.0.0-ballot Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Wed, Aug 14, 2024 18:30+0800+08:00) http://hl7.org/fhir/us/smp/2024Sep/package.r4.tgz http://hl7.org/fhir/us/smp/2024Sep/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 14 Aug 2024 21:02:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.smp.r4b#1.0.0-ballot Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Wed, Aug 14, 2024 18:30+0800+08:00) http://hl7.org/fhir/us/smp/2024Sep/package.r4b.tgz http://hl7.org/fhir/us/smp/2024Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 14 Aug 2024 21:02:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.mcc.r4#1.0.0-ballot ### Introduction This HL7&reg; 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. A 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: 1. Query for patient data across providers and compile into a consolidated care plan representation. 2. Encourage capture of and communication of a patient's health concerns and related goals, interventions, and outcomes. 3. 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.) This 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. ### How to Read this Guide and Cautions This 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. ### Value Set Library Rather 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. This 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. ### History of the Care Plan and Electronic Care Plans The 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. Most 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. We 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. ### Project Overview More 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. Care 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. The 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. Initiated 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. The HL7-based activities of the MCC eCare Plan Project include: - Identified use cases to support the documentation and exchange of MCC eCare plan data within EHRs and related systems. - 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. - Develop, test, and ballot an HL7® Fast Health Interoperability Resources (FHIR®) Implementation Guide based on the defined use cases and MCC data elements. Non-HL7 related activities of the MCC eCare Plan project will be facilitated through the [AHRQ eCare Plan Project Confluence](https://ecareplan.ahrq.gov/collaborate): - 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. #### Project Timelines - January 2024: A For comment ballot to gather community input prior to the formal STU Ballot - September 2024: Formal STU Ballot - May 2025 Formal HL7 Publication ### Guidance The 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. #### Relationship to US Core This 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. This 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 ##### General US Core IG Conformance This 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. ##### Provenance This 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). ##### Must Support This IG will adhere to the US Core [Must Support](https://www.hl7.org/fhir/us/core/general-guidance.html#must-support) concept and rules. ### Acknowledgements This 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. This 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) **Implementation Guide Contributors:** <table border="1" cellspacing="0" style="width:100.0%"> <tbody> <tr> <td style="background-color:#d9e2f3; width:89.75pt"> <p><strong>Contributor</strong></p> </td> <td style="background-color:#d9e2f3; width:148.5pt"> <p><strong>Organization</strong></p> </td> <td style="background-color:#d9e2f3; width:229.5pt"> <p><strong>Role</strong></p> </td> <td style="background-color:#d9e2f3; width:211.5pt"> <p><strong>email</strong></p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Jenna Norton</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>NIH/NIDDK</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Project Champion</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>jenna.norton@nih.gov</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Kevin Abbott</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>NIH/NIDDK</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Project Champion</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>kevin.abbott@nih.gov</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Arlene Bierman</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>AHRQ</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Project Champion</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>arlene.bierman@ahrq.hhs.gov</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Evelyn Gallego</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>EMI Advisors</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Project Champion</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>evelyn.gallego@emiadvisors.net</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Gay Dolin</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>Namaste Informatics</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>IG Design Lead</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>gdolin@namasteinformatics.com</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Bret Heale</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>Humanized Health Consulting</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>IG Developer</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>bheale@humanizedhealthconsulting.com</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Himali Saitwal</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>EMI Advisors</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Terminologist</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>himali.saitwal@emiadvisors.net</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Sara Armson</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>RTI/ONC</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Terminologist</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>sara.armson@hhs.gov</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Karen Bertodatti</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>EMI Advisors</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Project Manager</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>karen.bertodatti@emiadvisors.net</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Savanah Mueller</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>EMI Advisors</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Analyst</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>savanah.mueller@emiadvisors.net</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Emma Jones</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>Allscripts Veradigm</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Domain Expert</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>emma.jones@allscripts.com</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Dave Carlson</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>Clinical Cloud Solutions</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Solutions Architect, Test Implementations</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>dcarlson@clinicalcloud.solutions</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Sean Muir</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>JKM Software</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Developer, Test Implementations</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>sean.muir@jkmsoftware.com</p> </td> </tr> </tbody> </table> (built Sun, Dec 4, 2022 03:53+0000+00:00) http://hl7.org/fhir/us/mcc/2023Jan/package.r4.tgz http://hl7.org/fhir/us/mcc/2023Jan/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 14 Aug 2024 07:42:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.mcc.r4b#1.0.0-ballot ### Introduction This HL7&reg; 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. A 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: 1. Query for patient data across providers and compile into a consolidated care plan representation. 2. Encourage capture of and communication of a patient's health concerns and related goals, interventions, and outcomes. 3. 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.) This 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. ### How to Read this Guide and Cautions This 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. ### Value Set Library Rather 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. This 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. ### History of the Care Plan and Electronic Care Plans The 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. Most 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. We 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. ### Project Overview More 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. Care 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. The 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. Initiated 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. The HL7-based activities of the MCC eCare Plan Project include: - Identified use cases to support the documentation and exchange of MCC eCare plan data within EHRs and related systems. - 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. - Develop, test, and ballot an HL7® Fast Health Interoperability Resources (FHIR®) Implementation Guide based on the defined use cases and MCC data elements. Non-HL7 related activities of the MCC eCare Plan project will be facilitated through the [AHRQ eCare Plan Project Confluence](https://ecareplan.ahrq.gov/collaborate): - 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. #### Project Timelines - January 2024: A For comment ballot to gather community input prior to the formal STU Ballot - September 2024: Formal STU Ballot - May 2025 Formal HL7 Publication ### Guidance The 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. #### Relationship to US Core This 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. This 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 ##### General US Core IG Conformance This 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. ##### Provenance This 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). ##### Must Support This IG will adhere to the US Core [Must Support](https://www.hl7.org/fhir/us/core/general-guidance.html#must-support) concept and rules. ### Acknowledgements This 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. This 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) **Implementation Guide Contributors:** <table border="1" cellspacing="0" style="width:100.0%"> <tbody> <tr> <td style="background-color:#d9e2f3; width:89.75pt"> <p><strong>Contributor</strong></p> </td> <td style="background-color:#d9e2f3; width:148.5pt"> <p><strong>Organization</strong></p> </td> <td style="background-color:#d9e2f3; width:229.5pt"> <p><strong>Role</strong></p> </td> <td style="background-color:#d9e2f3; width:211.5pt"> <p><strong>email</strong></p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Jenna Norton</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>NIH/NIDDK</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Project Champion</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>jenna.norton@nih.gov</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Kevin Abbott</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>NIH/NIDDK</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Project Champion</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>kevin.abbott@nih.gov</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Arlene Bierman</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>AHRQ</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Project Champion</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>arlene.bierman@ahrq.hhs.gov</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Evelyn Gallego</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>EMI Advisors</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Project Champion</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>evelyn.gallego@emiadvisors.net</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Gay Dolin</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>Namaste Informatics</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>IG Design Lead</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>gdolin@namasteinformatics.com</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Bret Heale</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>Humanized Health Consulting</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>IG Developer</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>bheale@humanizedhealthconsulting.com</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Himali Saitwal</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>EMI Advisors</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Terminologist</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>himali.saitwal@emiadvisors.net</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Sara Armson</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>RTI/ONC</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Terminologist</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>sara.armson@hhs.gov</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Karen Bertodatti</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>EMI Advisors</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Project Manager</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>karen.bertodatti@emiadvisors.net</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Savanah Mueller</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>EMI Advisors</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Analyst</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>savanah.mueller@emiadvisors.net</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Emma Jones</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>Allscripts Veradigm</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Domain Expert</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>emma.jones@allscripts.com</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Dave Carlson</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>Clinical Cloud Solutions</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Solutions Architect, Test Implementations</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>dcarlson@clinicalcloud.solutions</p> </td> </tr> <tr> <td style="vertical-align:top; width:89.75pt"> <p>Sean Muir</p> </td> <td style="vertical-align:top; width:148.5pt"> <p>JKM Software</p> </td> <td style="vertical-align:top; width:229.5pt"> <p>Developer, Test Implementations</p> </td> <td style="vertical-align:top; width:211.5pt"> <p>sean.muir@jkmsoftware.com</p> </td> </tr> </tbody> </table> (built Sun, Dec 4, 2022 03:53+0000+00:00) http://hl7.org/fhir/us/mcc/2023Jan/package.r4b.tgz http://hl7.org/fhir/us/mcc/2023Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 14 Aug 2024 07:42:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.mcc.r4#1.0.0 ### Introduction This HL7&reg; 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. A 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: 1. Query for patient data across providers and compile into a consolidated care plan representation. 2. Encourage capture of and communication of a patient's health concerns and related goals, interventions, and outcomes. 3. 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.) This 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. ### How to Read this Guide and Cautions This 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. ### Value Set Library Rather 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. This 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. ### History of the Care Plan and Electronic Care Plans The 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. Most 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. We 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. ### Project Overview More 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. Care 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. The 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. Initiated 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. The HL7-based activities of the MCC eCare Plan Project include: - Identified use cases to support the documentation and exchange of MCC eCare plan data within EHRs and related systems. - 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. - Develop, test, and ballot an HL7® Fast Health Interoperability Resources (FHIR®) Implementation Guide based on the defined use cases and MCC data elements. Non-HL7 related activities of the MCC eCare Plan project will be facilitated through the [AHRQ eCare Plan Project Confluence](https://ecareplan.ahrq.gov/collaborate): - 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. #### Project Timelines - January 2024: A For comment ballot to gather community input prior to the formal STU Ballot - September 2024: Formal STU Ballot - May 2025 Formal HL7 Publication ### Guidance The 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. #### Relationship to US Core This 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. This 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 ##### General US Core IG Conformance This 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. ##### Provenance This 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). ##### Must Support This IG will adhere to the US Core [Must Support](https://www.hl7.org/fhir/us/core/general-guidance.html#must-support) concept and rules. ### Acknowledgements This 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. This 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) (built Tue, Aug 13, 2024 21:18+0000+00:00) http://hl7.org/fhir/us/mcc/package.r4.tgz http://hl7.org/fhir/us/mcc/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 14 Aug 2024 07:42:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.mcc.r4b#1.0.0 ### Introduction This HL7&reg; 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. A 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: 1. Query for patient data across providers and compile into a consolidated care plan representation. 2. Encourage capture of and communication of a patient's health concerns and related goals, interventions, and outcomes. 3. 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.) This 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. ### How to Read this Guide and Cautions This 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. ### Value Set Library Rather 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. This 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. ### History of the Care Plan and Electronic Care Plans The 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. Most 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. We 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. ### Project Overview More 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. Care 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. The 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. Initiated 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. The HL7-based activities of the MCC eCare Plan Project include: - Identified use cases to support the documentation and exchange of MCC eCare plan data within EHRs and related systems. - 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. - Develop, test, and ballot an HL7® Fast Health Interoperability Resources (FHIR®) Implementation Guide based on the defined use cases and MCC data elements. Non-HL7 related activities of the MCC eCare Plan project will be facilitated through the [AHRQ eCare Plan Project Confluence](https://ecareplan.ahrq.gov/collaborate): - 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. #### Project Timelines - January 2024: A For comment ballot to gather community input prior to the formal STU Ballot - September 2024: Formal STU Ballot - May 2025 Formal HL7 Publication ### Guidance The 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. #### Relationship to US Core This 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. This 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 ##### General US Core IG Conformance This 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. ##### Provenance This 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). ##### Must Support This IG will adhere to the US Core [Must Support](https://www.hl7.org/fhir/us/core/general-guidance.html#must-support) concept and rules. ### Acknowledgements This 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. This 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) (built Tue, Aug 13, 2024 21:18+0000+00:00) http://hl7.org/fhir/us/mcc/package.r4b.tgz http://hl7.org/fhir/us/mcc/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 14 Aug 2024 07:42:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.mcc.r4#1.0.0-ballot2 ### Introduction This HL7&reg; 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. A 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: 1. Query for patient data across providers and compile into a consolidated care plan representation. 2. Encourage capture of and communication of a patient's health concerns and related goals, interventions, and outcomes. 3. 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.) This 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. ### How to Read this Guide and Cautions This 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. ### Value Set Library Rather 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. This 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. ### History of the Care Plan and Electronic Care Plans The 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. Most 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. We 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. ### Project Overview More 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. Care 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. The 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. Initiated 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. The HL7-based activities of the MCC eCare Plan Project include: - Identified use cases to support the documentation and exchange of MCC eCare plan data within EHRs and related systems. - 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. - Develop, test, and ballot an HL7® Fast Health Interoperability Resources (FHIR®) Implementation Guide based on the defined use cases and MCC data elements. Non-HL7 related activities of the MCC eCare Plan project will be facilitated through the [AHRQ eCare Plan Project Confluence](https://ecareplan.ahrq.gov/collaborate): - 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. #### Project Timelines - January 2024: A For comment ballot to gather community input prior to the formal STU Ballot - September 2024: Formal STU Ballot - May 2025 Formal HL7 Publication ### Guidance The 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. #### Relationship to US Core This 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. This 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 ##### General US Core IG Conformance This 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. ##### Provenance This 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). ##### Must Support This IG will adhere to the US Core [Must Support](https://www.hl7.org/fhir/us/core/general-guidance.html#must-support) concept and rules. ### Acknowledgements This 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. This 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) (built Fri, Jul 28, 2023 17:45+0000+00:00) http://hl7.org/fhir/us/mcc/2023Sep/package.r4.tgz http://hl7.org/fhir/us/mcc/2023Sep/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 14 Aug 2024 07:41:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.mcc.r4b#1.0.0-ballot2 ### Introduction This HL7&reg; 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. A 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: 1. Query for patient data across providers and compile into a consolidated care plan representation. 2. Encourage capture of and communication of a patient's health concerns and related goals, interventions, and outcomes. 3. 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.) This 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. ### How to Read this Guide and Cautions This 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. ### Value Set Library Rather 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. This 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. ### History of the Care Plan and Electronic Care Plans The 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. Most 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. We 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. ### Project Overview More 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. Care 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. The 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. Initiated 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. The HL7-based activities of the MCC eCare Plan Project include: - Identified use cases to support the documentation and exchange of MCC eCare plan data within EHRs and related systems. - 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. - Develop, test, and ballot an HL7® Fast Health Interoperability Resources (FHIR®) Implementation Guide based on the defined use cases and MCC data elements. Non-HL7 related activities of the MCC eCare Plan project will be facilitated through the [AHRQ eCare Plan Project Confluence](https://ecareplan.ahrq.gov/collaborate): - 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. #### Project Timelines - January 2024: A For comment ballot to gather community input prior to the formal STU Ballot - September 2024: Formal STU Ballot - May 2025 Formal HL7 Publication ### Guidance The 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. #### Relationship to US Core This 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. This 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 ##### General US Core IG Conformance This 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. ##### Provenance This 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). ##### Must Support This IG will adhere to the US Core [Must Support](https://www.hl7.org/fhir/us/core/general-guidance.html#must-support) concept and rules. ### Acknowledgements This 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. This 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) (built Fri, Jul 28, 2023 17:45+0000+00:00) http://hl7.org/fhir/us/mcc/2023Sep/package.r4b.tgz http://hl7.org/fhir/us/mcc/2023Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 14 Aug 2024 07:41:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.pacio-pfe.r4#2.0.0-ballot 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 Tue, Aug 13, 2024 15:07+0000+00:00) http://hl7.org/fhir/us/pacio-pfe/2024Sep/package.r4.tgz http://hl7.org/fhir/us/pacio-pfe/2024Sep/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 14 Aug 2024 01:32:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.pacio-pfe.r4b#2.0.0-ballot 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 Tue, Aug 13, 2024 15:07+0000+00:00) http://hl7.org/fhir/us/pacio-pfe/2024Sep/package.r4b.tgz http://hl7.org/fhir/us/pacio-pfe/2024Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 14 Aug 2024 01:32:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.application-feature.r4#1.0.0-ballot Package hl7.fhir.uv.application-feature.r4#1.0.0-ballot http://hl7.org/fhir/uv/application-feature/2024Sep/package.r4.tgz http://hl7.org/fhir/uv/application-feature/2024Sep/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 14 Aug 2024 00:07:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.application-feature.r4b#1.0.0-ballot Package hl7.fhir.uv.application-feature.r4b#1.0.0-ballot http://hl7.org/fhir/uv/application-feature/2024Sep/package.r4b.tgz http://hl7.org/fhir/uv/application-feature/2024Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 14 Aug 2024 00:07:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.ips.r4#2.0.0-ballot Package hl7.fhir.uv.ips.r4#2.0.0-ballot http://hl7.org/fhir/uv/ips/2024Sep/package.r4.tgz http://hl7.org/fhir/uv/ips/2024Sep/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 13 Aug 2024 06:21:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.ips.r4b#2.0.0-ballot Package hl7.fhir.uv.ips.r4b#2.0.0-ballot http://hl7.org/fhir/uv/ips/2024Sep/package.r4b.tgz http://hl7.org/fhir/uv/ips/2024Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 13 Aug 2024 06:21:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.identity-matching.r4#2.0.0-ballot Package hl7.fhir.us.identity-matching.r4#2.0.0-ballot http://hl7.org/fhir/us/identity-matching/2024SEP/package.r4.tgz http://hl7.org/fhir/us/identity-matching/2024SEP/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 13 Aug 2024 04:48:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.identity-matching.r4b#2.0.0-ballot Package hl7.fhir.us.identity-matching.r4b#2.0.0-ballot http://hl7.org/fhir/us/identity-matching/2024SEP/package.r4b.tgz http://hl7.org/fhir/us/identity-matching/2024SEP/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 13 Aug 2024 04:48:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.nhsn-dqm.r4#1.0.0-ballot 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 Mon, Aug 12, 2024 17:39+0000+00:00) http://hl7.org/fhir/us/nhsn-dqm/2024Sep/package.r4.tgz http://hl7.org/fhir/us/nhsn-dqm/2024Sep/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 13 Aug 2024 04:04:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.nhsn-dqm.r4b#1.0.0-ballot 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 Mon, Aug 12, 2024 17:39+0000+00:00) http://hl7.org/fhir/us/nhsn-dqm/2024Sep/package.r4b.tgz http://hl7.org/fhir/us/nhsn-dqm/2024Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 13 Aug 2024 04:04:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.qicore.r4#7.0.0-ballot 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 Mon, Aug 12, 2024 16:12+0000+00:00) http://hl7.org/fhir/us/qicore/2024Sep/package.r4.tgz http://hl7.org/fhir/us/qicore/2024Sep/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 13 Aug 2024 02:53:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.qicore.r4b#7.0.0-ballot 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 Mon, Aug 12, 2024 16:12+0000+00:00) http://hl7.org/fhir/us/qicore/2024Sep/package.r4b.tgz http://hl7.org/fhir/us/qicore/2024Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 13 Aug 2024 02:53:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.smart-health-cards-and-links.r4#1.0.0-ballot FHIR Implementation Guide for SMART Health Cards and Links (built Thu, Aug 8, 2024 20:50+0000+00:00) http://hl7.org/fhir/uv/smart-health-cards-and-links/2024Sep/package.r4.tgz http://hl7.org/fhir/uv/smart-health-cards-and-links/2024Sep/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 09 Aug 2024 06:58:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.smart-health-cards-and-links.r4b#1.0.0-ballot FHIR Implementation Guide for SMART Health Cards and Links (built Thu, Aug 8, 2024 20:50+0000+00:00) http://hl7.org/fhir/uv/smart-health-cards-and-links/2024Sep/package.r4b.tgz http://hl7.org/fhir/uv/smart-health-cards-and-links/2024Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 09 Aug 2024 06:58:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.home-lab-report.r4#1.0.0 |Implementation Guide (IG) Characteristic | Value | |------------------------------------------------------|--------------------------------------------| |**FHIR Version:** | FHIR R4 | |**IG Realm:** | US | |**IG Type:** | STU Ballot | |**Exchange Methods:** | RESTfulAPI, Messages, Transactions, Tasks | |**IG Note:** | This HL7 FHIR Guide utilizes and adopts guidance or profiles developed in the US Core FHIR&reg; Implementation Guide. This FHIR IG has narrative pages describing the HL7 V2 Message for At-Home In-Vitro Test Reporting and provides some example messages. Presently public health departments usually only can handle and store HL7 V2| {:.table-striped} |IG Dependencies | |----------------------------------| | [HL7 FHIR US Core Version 5.0.1](http://hl7.org/fhir/us/core/STU5.0.1/) | {:.table-striped} ### Background Point-of-care (POC) and At-Home In-Vitro Tests offer increased accessibility to needed diagnostic solutions during a pandemic. Test results provide value to both the individual taking the tests and also to public health authorities responsible for coordinating a regional and national response. Digital platforms are being developed that allow individual test results, with permission of the individual, to be captured, organized, and transmitted to public health systems. Test manufacturers, working in partnership with these digital platforms, are seeking guidance on how to send test results. With multiple tests already entering the market, there is a need for a unified strategy on data flow of test results from the apps to downstream systems. A national data exchange standard should be supported that guides data exchange from test results residing on individual users’ digital test applications to public health authorities, at both the federal and regional levels. ### Introduction This implementation guide (IG) constrains the FHIR [US Core Diagnostic Report for Laboratory Results](http://hl7.org/fhir/us/core/StructureDefinition/us-core-diagnosticreport-lab) and the [US Core Laboratory Observation Profile](http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab) for use in transmitting At-Home In-Vitro Test results to local, state, territorial and federal health agencies. The IG will be be used in real world testing. It was developed as part of a collaborative project with the NIH/NIBIB, ONC, a vendor manufacturer of diagnostic healthcare products that makes one of the FDA approved At-Home In-Vitro Test kits, and an app developer who is a leading provider of secure interoperability solutions. The intention of this guide is to assist developers in producing and sending standardized FHIR test result data from tests perfomed at home. FHIR eases app development and the FHIR US Core IG is in a rapid adoption curve. This guide points to already existing US Core Guidance and other guidance with respect to FHIR Parameters, FHIR operations, and RESTful and SMART on FHIR information. Due to Public Health Departments' familiarity with V2, a test implementation project related to this implementation guide will initially send COVID-19 At-Home In-Vitro Test Reports as V2 lab messages. Longer term the intent is to leverage FHIR for app creativity, growth, and interoperability. For as long as needed to comply with Public Health Department dependecies on V2, the apps will be designed to transform from FHIR to V2. In addition, as a parallel effort, a V2 <-> FHIR data mapping table has been developed [In-Vitro At-Home Test V2 FHIR Mapping.xlsx]. **Please note** : This guide is a framework for future work. It contains "framework" profiles that contain constraints common to all At-Home In-Vitro Test Reporting use cases. These framework profiles can be further constrained to a particular use case such as the COVID-19 At-Home In-Vitro Test Reporting use case. The COVID-19 use case profiles have been created and included in this guide. ### Further Information [RADx® MARS - Mobile Application Reporting through Standards](https://www.nibib.nih.gov/covid-19/radx-tech-program/mars) [LOINC In Vitro Diagnostic (LIVD) Test Code Mapping for SARS-CoV-2 Tests](https://www.cdc.gov/csels/dls/sars-cov-2-livd-codes.html) [Test-Specific HL7v2 Field Values Tool](https://app.powerbigov.us/view?r=eyJrIjoiNjQyZjBkOGEtNjE0ZS00NjUyLTg3NjEtZTIxN2JmODE0ZGE1IiwidCI6IjE0Yjc3NTc4LTk3NzMtNDJkNS04NTA3LTI1MWNhMmRjMmIwNiJ9&pageName=ReportSectionhttps://app.powerbigov.us/view?r=eyJrIjoiNjQyZjBkOGEtNjE0ZS00NjUyLTg3NjEtZTIxN2JmODE0ZGE1IiwidCI6IjE0Yjc3NTc4LTk3NzMtNDJkNS04NTA3LTI1MWNhMmRjMmIwNiJ9&pageName=ReportSection3147535a75468ee60d16) ### Acknowledgements/Primary Authors * [NIBIB-Interagency Project Team](mailto:krishna.Juluru@pif.gov) * [CareEvolution](https://careevolution.com) * [Association of Public Health Laboratories](https://www.aphl.org/Pages/default.aspx) * [Gay Dolin MSN RN (Namaste Informatics)](mailto:gdolin@NamasteInformatics.com) * [Sarah Gaunt](mailto:sarah.gaunt@lantanaconsulting.com) (built Sat, Mar 25, 2023 16:44+0000+00:00) http://hl7.org/fhir/us/home-lab-report/STU1/package.r4.tgz http://hl7.org/fhir/us/home-lab-report/STU1/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 09 Aug 2024 06:06:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.home-lab-report.r4b#1.0.0 |Implementation Guide (IG) Characteristic | Value | |------------------------------------------------------|--------------------------------------------| |**FHIR Version:** | FHIR R4 | |**IG Realm:** | US | |**IG Type:** | STU Ballot | |**Exchange Methods:** | RESTfulAPI, Messages, Transactions, Tasks | |**IG Note:** | This HL7 FHIR Guide utilizes and adopts guidance or profiles developed in the US Core FHIR&reg; Implementation Guide. This FHIR IG has narrative pages describing the HL7 V2 Message for At-Home In-Vitro Test Reporting and provides some example messages. Presently public health departments usually only can handle and store HL7 V2| {:.table-striped} |IG Dependencies | |----------------------------------| | [HL7 FHIR US Core Version 5.0.1](http://hl7.org/fhir/us/core/STU5.0.1/) | {:.table-striped} ### Background Point-of-care (POC) and At-Home In-Vitro Tests offer increased accessibility to needed diagnostic solutions during a pandemic. Test results provide value to both the individual taking the tests and also to public health authorities responsible for coordinating a regional and national response. Digital platforms are being developed that allow individual test results, with permission of the individual, to be captured, organized, and transmitted to public health systems. Test manufacturers, working in partnership with these digital platforms, are seeking guidance on how to send test results. With multiple tests already entering the market, there is a need for a unified strategy on data flow of test results from the apps to downstream systems. A national data exchange standard should be supported that guides data exchange from test results residing on individual users’ digital test applications to public health authorities, at both the federal and regional levels. ### Introduction This implementation guide (IG) constrains the FHIR [US Core Diagnostic Report for Laboratory Results](http://hl7.org/fhir/us/core/StructureDefinition/us-core-diagnosticreport-lab) and the [US Core Laboratory Observation Profile](http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab) for use in transmitting At-Home In-Vitro Test results to local, state, territorial and federal health agencies. The IG will be be used in real world testing. It was developed as part of a collaborative project with the NIH/NIBIB, ONC, a vendor manufacturer of diagnostic healthcare products that makes one of the FDA approved At-Home In-Vitro Test kits, and an app developer who is a leading provider of secure interoperability solutions. The intention of this guide is to assist developers in producing and sending standardized FHIR test result data from tests perfomed at home. FHIR eases app development and the FHIR US Core IG is in a rapid adoption curve. This guide points to already existing US Core Guidance and other guidance with respect to FHIR Parameters, FHIR operations, and RESTful and SMART on FHIR information. Due to Public Health Departments' familiarity with V2, a test implementation project related to this implementation guide will initially send COVID-19 At-Home In-Vitro Test Reports as V2 lab messages. Longer term the intent is to leverage FHIR for app creativity, growth, and interoperability. For as long as needed to comply with Public Health Department dependecies on V2, the apps will be designed to transform from FHIR to V2. In addition, as a parallel effort, a V2 <-> FHIR data mapping table has been developed [In-Vitro At-Home Test V2 FHIR Mapping.xlsx]. **Please note** : This guide is a framework for future work. It contains "framework" profiles that contain constraints common to all At-Home In-Vitro Test Reporting use cases. These framework profiles can be further constrained to a particular use case such as the COVID-19 At-Home In-Vitro Test Reporting use case. The COVID-19 use case profiles have been created and included in this guide. ### Further Information [RADx® MARS - Mobile Application Reporting through Standards](https://www.nibib.nih.gov/covid-19/radx-tech-program/mars) [LOINC In Vitro Diagnostic (LIVD) Test Code Mapping for SARS-CoV-2 Tests](https://www.cdc.gov/csels/dls/sars-cov-2-livd-codes.html) [Test-Specific HL7v2 Field Values Tool](https://app.powerbigov.us/view?r=eyJrIjoiNjQyZjBkOGEtNjE0ZS00NjUyLTg3NjEtZTIxN2JmODE0ZGE1IiwidCI6IjE0Yjc3NTc4LTk3NzMtNDJkNS04NTA3LTI1MWNhMmRjMmIwNiJ9&pageName=ReportSectionhttps://app.powerbigov.us/view?r=eyJrIjoiNjQyZjBkOGEtNjE0ZS00NjUyLTg3NjEtZTIxN2JmODE0ZGE1IiwidCI6IjE0Yjc3NTc4LTk3NzMtNDJkNS04NTA3LTI1MWNhMmRjMmIwNiJ9&pageName=ReportSection3147535a75468ee60d16) ### Acknowledgements/Primary Authors * [NIBIB-Interagency Project Team](mailto:krishna.Juluru@pif.gov) * [CareEvolution](https://careevolution.com) * [Association of Public Health Laboratories](https://www.aphl.org/Pages/default.aspx) * [Gay Dolin MSN RN (Namaste Informatics)](mailto:gdolin@NamasteInformatics.com) * [Sarah Gaunt](mailto:sarah.gaunt@lantanaconsulting.com) (built Sat, Mar 25, 2023 16:44+0000+00:00) http://hl7.org/fhir/us/home-lab-report/STU1/package.r4b.tgz http://hl7.org/fhir/us/home-lab-report/STU1/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 09 Aug 2024 06:06:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.home-lab-report.r4#1.1.0 Package hl7.fhir.us.home-lab-report.r4#1.1.0 http://hl7.org/fhir/us/home-lab-report/package.r4.tgz http://hl7.org/fhir/us/home-lab-report/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 09 Aug 2024 06:06:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.home-lab-report.r4b#1.1.0 Package hl7.fhir.us.home-lab-report.r4b#1.1.0 http://hl7.org/fhir/us/home-lab-report/STU1.1/package.r4b.tgz http://hl7.org/fhir/us/home-lab-report/STU1.1/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 09 Aug 2024 06:06:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.fhir-clinical-document.r4#1.0.0-ballot Package hl7.fhir.uv.fhir-clinical-document.r4#1.0.0-ballot http://hl7.org/fhir/uv/fhir-clinical-document/2024Sep/package.r4.tgz http://hl7.org/fhir/uv/fhir-clinical-document/2024Sep/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 09 Aug 2024 04:23:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.fhir-clinical-document.r4b#1.0.0-ballot Package hl7.fhir.uv.fhir-clinical-document.r4b#1.0.0-ballot http://hl7.org/fhir/uv/fhir-clinical-document/2024Sep/package.r4b.tgz http://hl7.org/fhir/uv/fhir-clinical-document/2024Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 09 Aug 2024 04:23:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.carin-bb.r4#2.1.0-snapshot1 CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) (built Sat, Jul 27, 2024 20:08+0800+08:00) http://hl7.org/fhir/us/carin-bb/2.1.0-snapshot1/package.r4.tgz http://hl7.org/fhir/us/carin-bb/2.1.0-snapshot1/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 27 Jul 2024 23:42:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.carin-bb.r4b#2.1.0-snapshot1 CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) (built Sat, Jul 27, 2024 20:08+0800+08:00) http://hl7.org/fhir/us/carin-bb/2.1.0-snapshot1/package.r4b.tgz http://hl7.org/fhir/us/carin-bb/2.1.0-snapshot1/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 27 Jul 2024 23:42:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.mdi.r4#2.0.0-snapshot1 Package hl7.fhir.us.mdi.r4#2.0.0-snapshot1 http://hl7.org/fhir/us/mdi/2.0.0-snapshot1/package.r4.tgz http://hl7.org/fhir/us/mdi/2.0.0-snapshot1/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 20 Jun 2024 12:26:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.mdi.r4b#2.0.0-snapshot1 Package hl7.fhir.us.mdi.r4b#2.0.0-snapshot1 http://hl7.org/fhir/us/mdi/2.0.0-snapshot1/package.r4b.tgz http://hl7.org/fhir/us/mdi/2.0.0-snapshot1/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 20 Jun 2024 12:26:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-vbpr.r4#1.0.0-ballot The Da Vinci Fast Healthcare Interoperability Resource (FHIR) Value-Based Performance Reporting Implementation Guide (this IG) describes exchange of value-based performance reports among stakeholders such as payers, providers, and government care programs. (built Mon, Jul 31, 2023 14:29+0000+00:00) http://hl7.org/fhir/us/davinci-vbpr/2023Sep/package.r4.tgz http://hl7.org/fhir/us/davinci-vbpr/2023Sep/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 18 Jun 2024 00:15:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-vbpr.r4b#1.0.0-ballot The Da Vinci Fast Healthcare Interoperability Resource (FHIR) Value-Based Performance Reporting Implementation Guide (this IG) describes exchange of value-based performance reports among stakeholders such as payers, providers, and government care programs. (built Mon, Jul 31, 2023 14:29+0000+00:00) http://hl7.org/fhir/us/davinci-vbpr/2023Sep/package.r4b.tgz http://hl7.org/fhir/us/davinci-vbpr/2023Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 18 Jun 2024 00:15:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-vbpr.r4#1.0.0 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) http://hl7.org/fhir/us/davinci-vbpr/package.r4.tgz http://hl7.org/fhir/us/davinci-vbpr/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 18 Jun 2024 00:15:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-vbpr.r4b#1.0.0 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) http://hl7.org/fhir/us/davinci-vbpr/package.r4b.tgz http://hl7.org/fhir/us/davinci-vbpr/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 18 Jun 2024 00:15:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.crmi.r4#1.0.0 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, May 31, 2024 16:57+0000+00:00) http://hl7.org/fhir/uv/crmi/package.r4.tgz http://hl7.org/fhir/uv/crmi/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 01 Jun 2024 03:27:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.crmi.r4b#1.0.0 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, May 31, 2024 16:57+0000+00:00) http://hl7.org/fhir/uv/crmi/package.r4b.tgz http://hl7.org/fhir/uv/crmi/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 01 Jun 2024 03:27:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.crmi.r4#1.0.0-ballot 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 Thu, Aug 3, 2023 14:50+0000+00:00) http://hl7.org/fhir/uv/crmi/2023Sep/package.r4.tgz http://hl7.org/fhir/uv/crmi/2023Sep/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 01 Jun 2024 03:26:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.crmi.r4b#1.0.0-ballot 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 Thu, Aug 3, 2023 14:50+0000+00:00) http://hl7.org/fhir/uv/crmi/2023Sep/package.r4b.tgz http://hl7.org/fhir/uv/crmi/2023Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 01 Jun 2024 03:26:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.crmi.r4#1.0.0-ballot2 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 Wed, Dec 20, 2023 03:22+0000+00:00) http://hl7.org/fhir/uv/crmi/2024Jan/package.r4.tgz http://hl7.org/fhir/uv/crmi/2024Jan/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 01 Jun 2024 03:25:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.crmi.r4b#1.0.0-ballot2 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 Wed, Dec 20, 2023 03:22+0000+00:00) http://hl7.org/fhir/uv/crmi/2024Jan/package.r4b.tgz http://hl7.org/fhir/uv/crmi/2024Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 01 Jun 2024 03:25:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.cql.r4#1.0.0-ballot 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 Wed, Dec 20, 2023 01:16+0000+00:00) http://hl7.org/fhir/uv/cql/2024Jan/package.r4.tgz http://hl7.org/fhir/uv/cql/2024Jan/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 01 Jun 2024 00:40:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.cql.r4b#1.0.0-ballot 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 Wed, Dec 20, 2023 01:16+0000+00:00) http://hl7.org/fhir/uv/cql/2024Jan/package.r4b.tgz http://hl7.org/fhir/uv/cql/2024Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 01 Jun 2024 00:40:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.cql.r4#1.0.0 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 Fri, May 31, 2024 14:18+0000+00:00) http://hl7.org/fhir/uv/cql/STU1/package.r4.tgz http://hl7.org/fhir/uv/cql/STU1/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 01 Jun 2024 00:39:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.cql.r4b#1.0.0 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 Fri, May 31, 2024 14:18+0000+00:00) http://hl7.org/fhir/uv/cql/STU1/package.r4b.tgz http://hl7.org/fhir/uv/cql/STU1/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 01 Jun 2024 00:39:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.central-cancer-registry-reporting.r4#1.0.0 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) http://hl7.org/fhir/us/central-cancer-registry-reporting/package.r4.tgz http://hl7.org/fhir/us/central-cancer-registry-reporting/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 31 May 2024 23:26:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.central-cancer-registry-reporting.r4b#1.0.0 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) http://hl7.org/fhir/us/central-cancer-registry-reporting/package.r4b.tgz http://hl7.org/fhir/us/central-cancer-registry-reporting/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 31 May 2024 23:26:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.eltss.r4#2.0.0 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) http://hl7.org/fhir/us/eltss/package.r4.tgz http://hl7.org/fhir/us/eltss/package.r4.tgz HL7, Inc 4.0.1 IG Mon, 27 May 2024 13:17:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.eltss.r4b#2.0.0 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) http://hl7.org/fhir/us/eltss/package.r4b.tgz http://hl7.org/fhir/us/eltss/package.r4b.tgz HL7, Inc 4.3.0 IG Mon, 27 May 2024 13:17:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.core.r4#6.0.0-ballot 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. These 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 Mon, Dec 5, 2022 15:26+0000+00:00) http://hl7.org/fhir/us/core/2023Jan/package.r4.tgz http://hl7.org/fhir/us/core/2023Jan/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 09 May 2024 05:10:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.core.r4b#6.0.0-ballot 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. These 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 Mon, Dec 5, 2022 15:26+0000+00:00) http://hl7.org/fhir/us/core/2023Jan/package.r4b.tgz http://hl7.org/fhir/us/core/2023Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 09 May 2024 05:10:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.core.r4#7.0.0-ballot 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. These 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, Dec 19, 2023 21:01+0000+00:00) http://hl7.org/fhir/us/core/2024Jan/package.r4.tgz http://hl7.org/fhir/us/core/2024Jan/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 09 May 2024 05:09:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.core.r4b#7.0.0-ballot 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. These 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, Dec 19, 2023 21:01+0000+00:00) http://hl7.org/fhir/us/core/2024Jan/package.r4b.tgz http://hl7.org/fhir/us/core/2024Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 09 May 2024 05:09:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.core.r4#6.0.0 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. These 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 Wed, May 3, 2023 21:17+0000+00:00) http://hl7.org/fhir/us/core/STU6/package.r4.tgz http://hl7.org/fhir/us/core/STU6/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 09 May 2024 04:59:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.core.r4b#6.0.0 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. These 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 Wed, May 3, 2023 21:17+0000+00:00) http://hl7.org/fhir/us/core/STU6/package.r4b.tgz http://hl7.org/fhir/us/core/STU6/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 09 May 2024 04:59:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.core.r4#6.1.0 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. These 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 Fri, Jun 30, 2023 14:02+0000+00:00) http://hl7.org/fhir/us/core/STU6.1/package.r4.tgz http://hl7.org/fhir/us/core/STU6.1/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 09 May 2024 04:58:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.core.r4b#6.1.0 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. These 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 Fri, Jun 30, 2023 14:02+0000+00:00) http://hl7.org/fhir/us/core/STU6.1/package.r4b.tgz http://hl7.org/fhir/us/core/STU6.1/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 09 May 2024 04:58:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.core.r4#6.1.0-snapshot1 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. These 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 Sat, May 27, 2023 08:07+1000+10:00) http://hl7.org/fhir/us/core/STU6.1-snapshot1/package.r4.tgz http://hl7.org/fhir/us/core/STU6.1-snapshot1/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 09 May 2024 04:57:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.core.r4b#6.1.0-snapshot1 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. These 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 Sat, May 27, 2023 08:07+1000+10:00) http://hl7.org/fhir/us/core/STU6.1-snapshot1/package.r4b.tgz http://hl7.org/fhir/us/core/STU6.1-snapshot1/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 09 May 2024 04:57:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.ae-research-backport-ig.r4#1.0.0-ballot ### 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 Fri, Jul 28, 2023 19:51+0000+00:00) http://hl7.org/fhir/uv/ae-research-backport-ig/2023Sep/package.r4.tgz http://hl7.org/fhir/uv/ae-research-backport-ig/2023Sep/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 01 May 2024 07:16:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.ae-research-backport-ig.r4b#1.0.0-ballot ### 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 Fri, Jul 28, 2023 19:51+0000+00:00) http://hl7.org/fhir/uv/ae-research-backport-ig/2023Sep/package.r4b.tgz http://hl7.org/fhir/uv/ae-research-backport-ig/2023Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 01 May 2024 07:16:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.ae-research-backport-ig.r4#1.0.1 ### 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) http://hl7.org/fhir/uv/ae-research-backport-ig/STU1/package.r4.tgz http://hl7.org/fhir/uv/ae-research-backport-ig/STU1/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 01 May 2024 07:16:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.ae-research-backport-ig.r4b#1.0.1 ### 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) http://hl7.org/fhir/uv/ae-research-backport-ig/STU1/package.r4b.tgz http://hl7.org/fhir/uv/ae-research-backport-ig/STU1/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 01 May 2024 07:16:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.smart.dstu2#1.0.0 Package hl7.fhir.smart.dstu2#1.0.0 http://hl7.org/fhir/smart-app-launch/1.0.0/dstu2-package.tgz http://hl7.org/fhir/smart-app-launch/1.0.0/dstu2-package.tgz HL7, Inc 4.0.0 IG Wed, 01 May 2024 05:34:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.smart-app-launch.r4#2.2.0 Package hl7.fhir.uv.smart-app-launch.r4#2.2.0 http://hl7.org/fhir/smart-app-launch/package.r4.tgz http://hl7.org/fhir/smart-app-launch/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 01 May 2024 05:34:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.smart-app-launch.r4b#2.2.0 Package hl7.fhir.uv.smart-app-launch.r4b#2.2.0 http://hl7.org/fhir/smart-app-launch/package.r4b.tgz http://hl7.org/fhir/smart-app-launch/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 01 May 2024 05:34:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.smart-app-launch.r4#2.1.0-ballot Package hl7.fhir.uv.smart-app-launch.r4#2.1.0-ballot http://hl7.org/fhir/smart-app-launch/2023Jan/package.r4.tgz http://hl7.org/fhir/smart-app-launch/2023Jan/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 01 May 2024 05:33:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.smart-app-launch.r4b#2.1.0-ballot Package hl7.fhir.uv.smart-app-launch.r4b#2.1.0-ballot http://hl7.org/fhir/smart-app-launch/2023Jan/package.r4b.tgz http://hl7.org/fhir/smart-app-launch/2023Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 01 May 2024 05:33:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.smart-app-launch.r4#2.1.0 Package hl7.fhir.uv.smart-app-launch.r4#2.1.0 http://hl7.org/fhir/smart-app-launch/STU2.1/package.r4.tgz http://hl7.org/fhir/smart-app-launch/STU2.1/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 01 May 2024 05:33:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.smart-app-launch.r4b#2.1.0 Package hl7.fhir.uv.smart-app-launch.r4b#2.1.0 http://hl7.org/fhir/smart-app-launch/STU2.1/package.r4b.tgz http://hl7.org/fhir/smart-app-launch/STU2.1/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 01 May 2024 05:33:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.smart-app-launch.r4#2.2.0-ballot Package hl7.fhir.uv.smart-app-launch.r4#2.2.0-ballot http://hl7.org/fhir/smart-app-launch/2024Jan/package.r4.tgz http://hl7.org/fhir/smart-app-launch/2024Jan/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 01 May 2024 05:33:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.smart-app-launch.r4b#2.2.0-ballot Package hl7.fhir.uv.smart-app-launch.r4b#2.2.0-ballot http://hl7.org/fhir/smart-app-launch/2024Jan/package.r4b.tgz http://hl7.org/fhir/smart-app-launch/2024Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 01 May 2024 05:33:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.cancer-reporting.r4#1.0.0 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 to a central registry, the FHIR Messaging paradigm shall be required; however when sending between LIS and EHR systems, implementors may choose to use alterantive transport and processing modalities, such as FHIR transaciton 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 message bundle and is compliant with FHIR Release 4. (built Tue, Jul 11, 2023 15:47+0000+00:00) http://hl7.org/fhir/us/cancer-reporting/STU1/package.r4.tgz http://hl7.org/fhir/us/cancer-reporting/STU1/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 17 Apr 2024 05:09:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.cancer-reporting.r4b#1.0.0 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 to a central registry, the FHIR Messaging paradigm shall be required; however when sending between LIS and EHR systems, implementors may choose to use alterantive transport and processing modalities, such as FHIR transaciton 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 message bundle and is compliant with FHIR Release 4. (built Tue, Jul 11, 2023 15:47+0000+00:00) http://hl7.org/fhir/us/cancer-reporting/STU1/package.r4b.tgz http://hl7.org/fhir/us/cancer-reporting/STU1/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 17 Apr 2024 05:09:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.cancer-reporting.r4#1.0.1 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 to a central registry, the FHIR Messaging paradigm shall be required; however when sending between LIS and EHR systems, implementors may choose to use alterantive transport and processing modalities, such as FHIR transaciton 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 message bundle and is compliant with FHIR Release 4. (built Tue, Apr 16, 2024 18:41+0000+00:00) http://hl7.org/fhir/us/cancer-reporting/STU1.0.1/package.r4.tgz http://hl7.org/fhir/us/cancer-reporting/STU1.0.1/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 17 Apr 2024 05:08:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.cancer-reporting.r4b#1.0.1 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 to a central registry, the FHIR Messaging paradigm shall be required; however when sending between LIS and EHR systems, implementors may choose to use alterantive transport and processing modalities, such as FHIR transaciton 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 message bundle and is compliant with FHIR Release 4. (built Tue, Apr 16, 2024 18:41+0000+00:00) http://hl7.org/fhir/us/cancer-reporting/STU1.0.1/package.r4b.tgz http://hl7.org/fhir/us/cancer-reporting/STU1.0.1/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 17 Apr 2024 05:08:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.insurance-card.r4#1.1.0 CARIN Digital Insurance Card (built Tue, Apr 16, 2024 17:35+0000+00:00) http://hl7.org/fhir/us/insurance-card/package.r4.tgz http://hl7.org/fhir/us/insurance-card/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 17 Apr 2024 03:50:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.insurance-card.r4b#1.1.0 CARIN Digital Insurance Card (built Tue, Apr 16, 2024 17:35+0000+00:00) http://hl7.org/fhir/us/insurance-card/package.r4b.tgz http://hl7.org/fhir/us/insurance-card/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 17 Apr 2024 03:50:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.fhircast.r4#3.0.0-ballot 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) http://hl7.org/fhir/uv/fhircast/2024May/package.r4.tgz http://hl7.org/fhir/uv/fhircast/2024May/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 11 Apr 2024 01:30:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.fhircast.r4b#3.0.0-ballot 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) http://hl7.org/fhir/uv/fhircast/2024May/package.r4b.tgz http://hl7.org/fhir/uv/fhircast/2024May/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 11 Apr 2024 01:30:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pct.r4#2.0.0-ballot To support the request for cost information for specific services and items 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 Mon, Apr 8, 2024 16:49+0000+00:00) http://hl7.org/fhir/us/davinci-pct/2024May/package.r4.tgz http://hl7.org/fhir/us/davinci-pct/2024May/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 09 Apr 2024 03:14:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pct.r4b#2.0.0-ballot To support the request for cost information for specific services and items 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 Mon, Apr 8, 2024 16:49+0000+00:00) http://hl7.org/fhir/us/davinci-pct/2024May/package.r4b.tgz http://hl7.org/fhir/us/davinci-pct/2024May/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 09 Apr 2024 03:14:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.mdi.r4#2.0.0-ballot Package hl7.fhir.us.mdi.r4#2.0.0-ballot http://hl7.org/fhir/us/mdi/2024May/package.r4.tgz http://hl7.org/fhir/us/mdi/2024May/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 06 Apr 2024 05:56:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.mdi.r4b#2.0.0-ballot Package hl7.fhir.us.mdi.r4b#2.0.0-ballot http://hl7.org/fhir/us/mdi/2024May/package.r4b.tgz http://hl7.org/fhir/us/mdi/2024May/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 06 Apr 2024 05:56:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.ccda.r4#1.2.0 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. This 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). The 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. We 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. ### Scope To represent Consolidated CDA Templates for Clinical Notes (C-CDA) 2.1 templates using FHIR profiles. This first stage of the project defines all the C-CDA document-level profiles on the Composition resource and contained sections. Any 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. For further information see the C-CDA specification here: http://www.hl7.org/implement/standards/product_brief.cfm?product_id=408. (built Tue, Mar 12, 2024 19:23+0000+00:00) http://hl7.org/fhir/us/ccda/package.r4.tgz http://hl7.org/fhir/us/ccda/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 13 Mar 2024 06:53:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.ccda.r4b#1.2.0 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. This 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). The 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. We 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. ### Scope To represent Consolidated CDA Templates for Clinical Notes (C-CDA) 2.1 templates using FHIR profiles. This first stage of the project defines all the C-CDA document-level profiles on the Composition resource and contained sections. Any 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. For further information see the C-CDA specification here: http://www.hl7.org/implement/standards/product_brief.cfm?product_id=408. (built Tue, Mar 12, 2024 19:23+0000+00:00) http://hl7.org/fhir/us/ccda/package.r4b.tgz http://hl7.org/fhir/us/ccda/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 13 Mar 2024 06:53:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.ccda.r4#1.2.0-ballot 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. This 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). The 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. We 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. ### Scope To represent Consolidated CDA Templates for Clinical Notes (C-CDA) 2.1 templates using FHIR profiles. This first stage of the project defines all the C-CDA document-level profiles on the Composition resource and contained sections. Any 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. For further information see the C-CDA specification here: http://www.hl7.org/implement/standards/product_brief.cfm?product_id=408. (built Mon, Mar 27, 2023 20:41+0000+00:00) http://hl7.org/fhir/us/ccda/2023May/package.r4.tgz http://hl7.org/fhir/us/ccda/2023May/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 13 Mar 2024 06:52:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.ccda.r4b#1.2.0-ballot 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. This 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). The 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. We 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. ### Scope To represent Consolidated CDA Templates for Clinical Notes (C-CDA) 2.1 templates using FHIR profiles. This first stage of the project defines all the C-CDA document-level profiles on the Composition resource and contained sections. Any 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. For further information see the C-CDA specification here: http://www.hl7.org/implement/standards/product_brief.cfm?product_id=408. (built Mon, Mar 27, 2023 20:41+0000+00:00) http://hl7.org/fhir/us/ccda/2023May/package.r4b.tgz http://hl7.org/fhir/us/ccda/2023May/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 13 Mar 2024 06:52:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.qicore.r4#6.0.0-ballot 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 Thu, Aug 3, 2023 13:26+0000+00:00) http://hl7.org/fhir/us/qicore/2023Sep/package.r4.tgz http://hl7.org/fhir/us/qicore/2023Sep/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 02 Mar 2024 06:45:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.qicore.r4b#6.0.0-ballot 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 Thu, Aug 3, 2023 13:26+0000+00:00) http://hl7.org/fhir/us/qicore/2023Sep/package.r4b.tgz http://hl7.org/fhir/us/qicore/2023Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 02 Mar 2024 06:45:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.qicore.r4#5.0.0 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 Tue, Apr 4, 2023 13:39+0000+00:00) http://hl7.org/fhir/us/qicore/STU5/package.r4.tgz http://hl7.org/fhir/us/qicore/STU5/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 02 Mar 2024 06:41:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.qicore.r4b#5.0.0 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 Tue, Apr 4, 2023 13:39+0000+00:00) http://hl7.org/fhir/us/qicore/STU5/package.r4b.tgz http://hl7.org/fhir/us/qicore/STU5/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 02 Mar 2024 06:41:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.qicore.r4#6.0.0 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, Mar 1, 2024 18:46+0000+00:00) http://hl7.org/fhir/us/qicore/STU6/package.r4.tgz http://hl7.org/fhir/us/qicore/STU6/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 02 Mar 2024 06:40:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.qicore.r4b#6.0.0 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, Mar 1, 2024 18:46+0000+00:00) http://hl7.org/fhir/us/qicore/STU6/package.r4b.tgz http://hl7.org/fhir/us/qicore/STU6/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 02 Mar 2024 06:40:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.pacio-adi.r4#1.0.0 PACIO Advance Directive Interoperability Implementation Guide (built Thu, Jan 11, 2024 18:02+0000+00:00) http://hl7.org/fhir/us/pacio-adi/package.r4.tgz http://hl7.org/fhir/us/pacio-adi/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 12 Jan 2024 05:28:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.pacio-adi.r4b#1.0.0 PACIO Advance Directive Interoperability Implementation Guide (built Thu, Jan 11, 2024 18:02+0000+00:00) http://hl7.org/fhir/us/pacio-adi/package.r4b.tgz http://hl7.org/fhir/us/pacio-adi/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 12 Jan 2024 05:28:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-atr.r4#2.0.0-ballot Exchange of member attribution list between payers and providers (built Mon, Dec 5, 2022 16:58+0000+00:00) http://hl7.org/fhir/us/davinci-atr/2023Jan/package.r4.tgz http://hl7.org/fhir/us/davinci-atr/2023Jan/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 10 Jan 2024 07:42:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-atr.r4b#2.0.0-ballot Exchange of member attribution list between payers and providers (built Mon, Dec 5, 2022 16:58+0000+00:00) http://hl7.org/fhir/us/davinci-atr/2023Jan/package.r4b.tgz http://hl7.org/fhir/us/davinci-atr/2023Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 10 Jan 2024 07:42:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-atr.r4#2.0.0 Exchange of member attribution list between payers and providers (built Tue, Jan 9, 2024 20:14+0000+00:00) http://hl7.org/fhir/us/davinci-atr/STU2/package.r4.tgz http://hl7.org/fhir/us/davinci-atr/STU2/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 10 Jan 2024 07:41:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-atr.r4b#2.0.0 Exchange of member attribution list between payers and providers (built Tue, Jan 9, 2024 20:14+0000+00:00) http://hl7.org/fhir/us/davinci-atr/STU2/package.r4b.tgz http://hl7.org/fhir/us/davinci-atr/STU2/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 10 Jan 2024 07:41:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pdex.r4#2.0.0 This specification has undergone ballot and connectathon testing. It is expected to evolve, possibly significantly, as part of that process. Feedback 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. This 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. [Financial Management](https://confluence.hl7.org/display/FM/Financial+Management+Home) is the Sponsoring Work Group for this Implementation Guide. **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 Profiles based on FHIR R4) which can be understood by providers and, if they choose to, committed to their Electronic Medical Records (EMR) System.** The 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. This IG uses the same Member Health History "payload" for member-authorized exchange of information with other Health Plans 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. This IG covers the exchange of: - Claims-based information - Clinical Information (such as Lab Results, Allergies and Conditions) This 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. This IG covers the exchange of a Member's Health History in the following scenarios: - Provider requested Provider-Health Plan Exchange using CDS-Hooks and SMART-on-FHIR - Member-authorized Health Plan to Health Plan exchange - Member-authorized Health Plan to Third-Party Application exchange The latter two scenarios are provided to meet the requirements identified in the CMS Interoperability and Patient Access Final Rule. **There are items in this guide that are subject to update**. This includes: - Value Sets - Vocabularies (X12, NUBC etc.) - Examples **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). See the [Table of Contents](toc.html) for more information. (built Sat, Jan 6, 2024 03:03+0000+00:00) http://hl7.org/fhir/us/davinci-pdex/STU2/package.r4.tgz http://hl7.org/fhir/us/davinci-pdex/STU2/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 06 Jan 2024 14:38:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pdex.r4b#2.0.0 This specification has undergone ballot and connectathon testing. It is expected to evolve, possibly significantly, as part of that process. Feedback 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. This 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. [Financial Management](https://confluence.hl7.org/display/FM/Financial+Management+Home) is the Sponsoring Work Group for this Implementation Guide. **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 Profiles based on FHIR R4) which can be understood by providers and, if they choose to, committed to their Electronic Medical Records (EMR) System.** The 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. This IG uses the same Member Health History "payload" for member-authorized exchange of information with other Health Plans 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. This IG covers the exchange of: - Claims-based information - Clinical Information (such as Lab Results, Allergies and Conditions) This 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. This IG covers the exchange of a Member's Health History in the following scenarios: - Provider requested Provider-Health Plan Exchange using CDS-Hooks and SMART-on-FHIR - Member-authorized Health Plan to Health Plan exchange - Member-authorized Health Plan to Third-Party Application exchange The latter two scenarios are provided to meet the requirements identified in the CMS Interoperability and Patient Access Final Rule. **There are items in this guide that are subject to update**. This includes: - Value Sets - Vocabularies (X12, NUBC etc.) - Examples **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). See the [Table of Contents](toc.html) for more information. (built Sat, Jan 6, 2024 03:03+0000+00:00) http://hl7.org/fhir/us/davinci-pdex/STU2/package.r4b.tgz http://hl7.org/fhir/us/davinci-pdex/STU2/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 06 Jan 2024 14:38:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.pacio-pfe.r4#1.0.0 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 Fri, Jan 5, 2024 16:53+0000+00:00) http://hl7.org/fhir/us/pacio-pfe/STU1/package.r4.tgz http://hl7.org/fhir/us/pacio-pfe/STU1/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 06 Jan 2024 04:36:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.pacio-pfe.r4b#1.0.0 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 Fri, Jan 5, 2024 16:53+0000+00:00) http://hl7.org/fhir/us/pacio-pfe/STU1/package.r4b.tgz http://hl7.org/fhir/us/pacio-pfe/STU1/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 06 Jan 2024 04:36:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pct.r4#1.0.0 To support the request for cost information for specific services and items 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 Thu, Mar 30, 2023 13:31+0000+00:00) http://hl7.org/fhir/us/davinci-pct/STU1/package.r4.tgz http://hl7.org/fhir/us/davinci-pct/STU1/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 04 Jan 2024 05:45:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pct.r4b#1.0.0 To support the request for cost information for specific services and items 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 Thu, Mar 30, 2023 13:31+0000+00:00) http://hl7.org/fhir/us/davinci-pct/STU1/package.r4b.tgz http://hl7.org/fhir/us/davinci-pct/STU1/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 04 Jan 2024 05:45:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pct.r4#1.1.0 To support the request for cost information for specific services and items 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, Jan 3, 2024 18:16+0000+00:00) http://hl7.org/fhir/us/davinci-pct/STU1.1/package.r4.tgz http://hl7.org/fhir/us/davinci-pct/STU1.1/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 04 Jan 2024 05:45:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-pct.r4b#1.1.0 To support the request for cost information for specific services and items 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, Jan 3, 2024 18:16+0000+00:00) http://hl7.org/fhir/us/davinci-pct/STU1.1/package.r4b.tgz http://hl7.org/fhir/us/davinci-pct/STU1.1/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 04 Jan 2024 05:45:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.ehrs-rle.r4#1.0.0-ballot EHRS Functional Model - Record Lifecycle Events - FHIR Implementation Guide (built Wed, Dec 7, 2022 16:55+0000+00:00) http://hl7.org/fhir/uv/ehrs-rle/2023Jan/package.r4.tgz http://hl7.org/fhir/uv/ehrs-rle/2023Jan/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 03 Jan 2024 09:11:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.ehrs-rle.r4b#1.0.0-ballot EHRS Functional Model - Record Lifecycle Events - FHIR Implementation Guide (built Wed, Dec 7, 2022 16:55+0000+00:00) http://hl7.org/fhir/uv/ehrs-rle/2023Jan/package.r4b.tgz http://hl7.org/fhir/uv/ehrs-rle/2023Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 03 Jan 2024 09:11:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.livd.r4#1.0.0-ballot Recommended LOINC mappings for IVD Devices (built Thu, Dec 21, 2023 20:53+0000+00:00) http://hl7.org/fhir/uv/livd/2024Jan/package.r4.tgz http://hl7.org/fhir/uv/livd/2024Jan/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 22 Dec 2023 08:05:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.livd.r4b#1.0.0-ballot Recommended LOINC mappings for IVD Devices (built Thu, Dec 21, 2023 20:53+0000+00:00) http://hl7.org/fhir/uv/livd/2024Jan/package.r4b.tgz http://hl7.org/fhir/uv/livd/2024Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 22 Dec 2023 08:05:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.resp-net.r4#1.0.0-ballot 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 Thu, Dec 21, 2023 13:44+0000+00:00) http://hl7.org/fhir/us/resp-net/2024Jan/package.r4.tgz http://hl7.org/fhir/us/resp-net/2024Jan/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 22 Dec 2023 01:03:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.resp-net.r4b#1.0.0-ballot 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 Thu, Dec 21, 2023 13:44+0000+00:00) http://hl7.org/fhir/us/resp-net/2024Jan/package.r4b.tgz http://hl7.org/fhir/us/resp-net/2024Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 22 Dec 2023 01:03:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.ecr#2.1.1 # Introduction and Purpose With 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. With 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. For 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). For Clinical Safety Information please refer to the [FHIR Implementer’s Safety Checklist](http://hl7.org/fhir/safety.html). <div style="background-color: #ffffcc; border-left: 6px solid #ffeb3b;"> <p><b>Known Issue:</b></p> <p>The following issue is related to a publication tooling issue. A technical correction is planned once the tooling issue has been addressed.</p> <ul> <li><a href="https://jira.hl7.org/browse/FHIR-30477" rel="external" target="_blank">FHIR-30477</a>: Resolution errors for FHIRHelpers and FHIR-ModelInfo.</li> </ul> </div> # Stakeholders * Regulatory Agencies * Standards Development Organizations * Vendors: EHR, PHR; Health Care IT; Clinical Decision Support Systems, Public Health Surveillance Systems * Providers: Ambulatory and Healthcare Institutions (hospitals, long term care, mental health) * Local, State, Tribal and Federal Public Health Agencies (built Thu, Dec 14, 2023 17:36+0000+00:00) http://hl7.org/fhir/us/ecr/old-STU2.1.1/package.tgz http://hl7.org/fhir/us/ecr/old-STU2.1.1/package.tgz HL7, Inc 4.0.1 IG Thu, 21 Dec 2023 23:30:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.v2mappings.r4#1.0.0-ballot 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 Wed, Dec 20, 2023 15:18+0000+00:00) http://hl7.org/fhir/uv/v2mappings/2024Jan/package.r4.tgz http://hl7.org/fhir/uv/v2mappings/2024Jan/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 21 Dec 2023 02:47:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.v2mappings.r4b#1.0.0-ballot 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 Wed, Dec 20, 2023 15:18+0000+00:00) http://hl7.org/fhir/uv/v2mappings/2024Jan/package.r4b.tgz http://hl7.org/fhir/uv/v2mappings/2024Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 21 Dec 2023 02:47:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-drug-formulary.r4#2.0.1 DaVinci Payer Data Exchange (PDex) US Drug Formulary, Release 2.0.1 - US Realm STU" (built Fri, Dec 1, 2023 22:17+0000+00:00) http://hl7.org/fhir/us/davinci-drug-formulary/STU2.0.1/package.r4.tgz http://hl7.org/fhir/us/davinci-drug-formulary/STU2.0.1/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 02 Dec 2023 09:42:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-drug-formulary.r4b#2.0.1 DaVinci Payer Data Exchange (PDex) US Drug Formulary, Release 2.0.1 - US Realm STU" (built Fri, Dec 1, 2023 22:17+0000+00:00) http://hl7.org/fhir/us/davinci-drug-formulary/STU2.0.1/package.r4b.tgz http://hl7.org/fhir/us/davinci-drug-formulary/STU2.0.1/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 02 Dec 2023 09:42:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.mdi.r4#1.1.0 This US-specific implementation guide (IG) provides guidance on the exchange of information to and from medicolegal death investigation (MDI) information systems. It supports interoperability between the MDI case management systems (CMS) used by medical examiner and coroner offices; forensic toxicology and other laboratory information management systems (LIMS); electronic death registration systems (EDRS) of jurisdictional vital records offices (VROs); and ancillary workflows whose systems have the capability of using Fast Healthcare Interoperability Resources (FHIR). This guide provides MDI CMS developers with the technical details and best practices to standardize MDI fields and interfaces. Stakeholders may use the narrative portions of this guide to inform policies and practices for data exchange between systems contributing to, and using information from, death investigations. This guide can serve as a base for local specifications. (built Thu, Nov 16, 2023 21:49+0000+00:00) http://hl7.org/fhir/us/mdi/STU1.1/package.r4.tgz http://hl7.org/fhir/us/mdi/STU1.1/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 17 Nov 2023 09:22:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.mdi.r4b#1.1.0 This US-specific implementation guide (IG) provides guidance on the exchange of information to and from medicolegal death investigation (MDI) information systems. It supports interoperability between the MDI case management systems (CMS) used by medical examiner and coroner offices; forensic toxicology and other laboratory information management systems (LIMS); electronic death registration systems (EDRS) of jurisdictional vital records offices (VROs); and ancillary workflows whose systems have the capability of using Fast Healthcare Interoperability Resources (FHIR). This guide provides MDI CMS developers with the technical details and best practices to standardize MDI fields and interfaces. Stakeholders may use the narrative portions of this guide to inform policies and practices for data exchange between systems contributing to, and using information from, death investigations. This guide can serve as a base for local specifications. (built Thu, Nov 16, 2023 21:49+0000+00:00) http://hl7.org/fhir/us/mdi/STU1.1/package.r4b.tgz http://hl7.org/fhir/us/mdi/STU1.1/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 17 Nov 2023 09:22:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.registry-protocols.r4#1.0.0-ballot 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 Wed, Mar 29, 2023 01:16+0000+00:00) http://hl7.org/fhir/us/registry-protocols/2023May/package.r4.tgz http://hl7.org/fhir/us/registry-protocols/2023May/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 15 Nov 2023 06:22:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.registry-protocols.r4b#1.0.0-ballot 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 Wed, Mar 29, 2023 01:16+0000+00:00) http://hl7.org/fhir/us/registry-protocols/2023May/package.r4b.tgz http://hl7.org/fhir/us/registry-protocols/2023May/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 15 Nov 2023 06:22:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.hsds.r4#1.0.0-ballot fhir-human-services-directory (built Thu, Dec 8, 2022 20:19+0000+00:00) http://hl7.org/fhir/us/hsds/2023Jan/package.r4.tgz http://hl7.org/fhir/us/hsds/2023Jan/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 05 Oct 2023 06:07:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.hsds.r4b#1.0.0-ballot fhir-human-services-directory (built Thu, Dec 8, 2022 20:19+0000+00:00) http://hl7.org/fhir/us/hsds/2023Jan/package.r4b.tgz http://hl7.org/fhir/us/hsds/2023Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 05 Oct 2023 06:07:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.hsds.r4#1.0.0 fhir-human-services-directory (built Wed, Oct 4, 2023 18:49+0000+00:00) http://hl7.org/fhir/us/hsds/STU1/package.r4.tgz http://hl7.org/fhir/us/hsds/STU1/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 05 Oct 2023 06:07:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.hsds.r4b#1.0.0 fhir-human-services-directory (built Wed, Oct 4, 2023 18:49+0000+00:00) http://hl7.org/fhir/us/hsds/STU1/package.r4b.tgz http://hl7.org/fhir/us/hsds/STU1/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 05 Oct 2023 06:07:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-deqm.stu3#0.1.0 Package hl7.fhir.us.davinci-deqm.stu3#0.1.0 http://hl7.org/fhir/us/davinci-deqm/2018Sep/STU3/package.tgz http://hl7.org/fhir/us/davinci-deqm/2018Sep/STU3/package.tgz HL7, Inc 3.0.1 IG Wed, 04 Oct 2023 06:48:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-deqm.stu3#0.2.0 Package hl7.fhir.us.davinci-deqm.stu3#0.2.0 http://hl7.org/fhir/us/davinci-deqm/2019May/STU3/package.tgz http://hl7.org/fhir/us/davinci-deqm/2019May/STU3/package.tgz HL7, Inc 3.0.1 IG Wed, 04 Oct 2023 06:48:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-deqm.r4#4.0.0-ballot Package hl7.fhir.us.davinci-deqm.r4#4.0.0-ballot http://hl7.org/fhir/us/davinci-deqm/2023Jan/package.r4.tgz http://hl7.org/fhir/us/davinci-deqm/2023Jan/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 04 Oct 2023 06:47:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-deqm.r4b#4.0.0-ballot Package hl7.fhir.us.davinci-deqm.r4b#4.0.0-ballot http://hl7.org/fhir/us/davinci-deqm/2023Jan/package.r4b.tgz http://hl7.org/fhir/us/davinci-deqm/2023Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 04 Oct 2023 06:47:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-deqm.r4#3.1.0 Package hl7.fhir.us.davinci-deqm.r4#3.1.0 http://hl7.org/fhir/us/davinci-deqm/STU3.1/package.r4.tgz http://hl7.org/fhir/us/davinci-deqm/STU3.1/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 04 Oct 2023 06:46:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-deqm.r4b#3.1.0 Package hl7.fhir.us.davinci-deqm.r4b#3.1.0 http://hl7.org/fhir/us/davinci-deqm/STU3.1/package.r4b.tgz http://hl7.org/fhir/us/davinci-deqm/STU3.1/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 04 Oct 2023 06:46:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-deqm.r4#4.0.0 Package hl7.fhir.us.davinci-deqm.r4#4.0.0 http://hl7.org/fhir/us/davinci-deqm/STU4/package.r4.tgz http://hl7.org/fhir/us/davinci-deqm/STU4/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 04 Oct 2023 06:45:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-deqm.r4b#4.0.0 Package hl7.fhir.us.davinci-deqm.r4b#4.0.0 http://hl7.org/fhir/us/davinci-deqm/STU4/package.r4b.tgz http://hl7.org/fhir/us/davinci-deqm/STU4/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 04 Oct 2023 06:45:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.hai.r4#2.1.0 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. As reports are modified and new report types are defined, CDC and Health Level Seven (HL7) will develop and publish additional constraints. Throughout 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. Note 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) http://hl7.org/fhir/us/hai/package.r4.tgz http://hl7.org/fhir/us/hai/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 07 Sep 2023 06:17:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.hai.r4b#2.1.0 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. As reports are modified and new report types are defined, CDC and Health Level Seven (HL7) will develop and publish additional constraints. Throughout 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. Note 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) http://hl7.org/fhir/us/hai/package.r4b.tgz http://hl7.org/fhir/us/hai/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 07 Sep 2023 06:17:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.icsr-ae-reporting.r4#1.0.1 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) http://hl7.org/fhir/us/icsr-ae-reporting/package.r4.tgz http://hl7.org/fhir/us/icsr-ae-reporting/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 30 Aug 2023 08:02:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.icsr-ae-reporting.r4b#1.0.1 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) http://hl7.org/fhir/us/icsr-ae-reporting/package.r4b.tgz http://hl7.org/fhir/us/icsr-ae-reporting/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 30 Aug 2023 08:02:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.physical-activity.r4#1.0.0 This implementation guide provides standardization around patient physical activity, including:&#x0a;* measures for recording a patient's level of physical activity;&#x0a;* measures to support assertions of physical activity, including device-based measures;&#x0a;* goals and care plans related to improving a patient's physical activity level;&#x0a;* orders for interventions seeking to improve a patient's physical activity level; and&#x0a;* processes to support closing the loop and evaluating the success of such interventions. (built Fri, Aug 25, 2023 15:58+0000+00:00) http://hl7.org/fhir/us/physical-activity/package.r4.tgz http://hl7.org/fhir/us/physical-activity/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 26 Aug 2023 02:36:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.physical-activity.r4b#1.0.0 This implementation guide provides standardization around patient physical activity, including:&#x0a;* measures for recording a patient's level of physical activity;&#x0a;* measures to support assertions of physical activity, including device-based measures;&#x0a;* goals and care plans related to improving a patient's physical activity level;&#x0a;* orders for interventions seeking to improve a patient's physical activity level; and&#x0a;* processes to support closing the loop and evaluating the success of such interventions. (built Fri, Aug 25, 2023 15:58+0000+00:00) http://hl7.org/fhir/us/physical-activity/package.r4b.tgz http://hl7.org/fhir/us/physical-activity/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 26 Aug 2023 02:36:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.health-care-surveys-reporting.r4#1.0.0 The Health Care Surveys Content IG provides healthcare organizations the necessary data exchange mechanisms to report health care survey data to public health agencies. (built Tue, Aug 22, 2023 19:16+0000+00:00) http://hl7.org/fhir/us/health-care-surveys-reporting/STU1/package.r4.tgz http://hl7.org/fhir/us/health-care-surveys-reporting/STU1/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 23 Aug 2023 05:43:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.health-care-surveys-reporting.r4b#1.0.0 The Health Care Surveys Content IG provides healthcare organizations the necessary data exchange mechanisms to report health care survey data to public health agencies. (built Tue, Aug 22, 2023 19:16+0000+00:00) http://hl7.org/fhir/us/health-care-surveys-reporting/STU1/package.r4b.tgz http://hl7.org/fhir/us/health-care-surveys-reporting/STU1/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 23 Aug 2023 05:43:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.ichom-breast-cancer.r4#1.0.0-ballot Package hl7.fhir.uv.ichom-breast-cancer.r4#1.0.0-ballot http://hl7.org/fhir/uv/ichom-breast-cancer/2023Jan/package.r4.tgz http://hl7.org/fhir/uv/ichom-breast-cancer/2023Jan/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 22 Aug 2023 03:53:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.ichom-breast-cancer.r4b#1.0.0-ballot Package hl7.fhir.uv.ichom-breast-cancer.r4b#1.0.0-ballot http://hl7.org/fhir/uv/ichom-breast-cancer/2023Jan/package.r4b.tgz http://hl7.org/fhir/uv/ichom-breast-cancer/2023Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 22 Aug 2023 03:53:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.ichom-breast-cancer.r4#1.0.0 Package hl7.fhir.uv.ichom-breast-cancer.r4#1.0.0 http://hl7.org/fhir/uv/ichom-breast-cancer/package.r4.tgz http://hl7.org/fhir/uv/ichom-breast-cancer/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 22 Aug 2023 03:53:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.ichom-breast-cancer.r4b#1.0.0 Package hl7.fhir.uv.ichom-breast-cancer.r4b#1.0.0 http://hl7.org/fhir/uv/ichom-breast-cancer/package.r4b.tgz http://hl7.org/fhir/uv/ichom-breast-cancer/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 22 Aug 2023 03:53:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.ph-library.r4#1.0.0 Package hl7.fhir.us.ph-library.r4#1.0.0 http://hl7.org/fhir/us/ph-library/package.r4.tgz http://hl7.org/fhir/us/ph-library/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 18 Aug 2023 00:42:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.ph-library.r4b#1.0.0 Package hl7.fhir.us.ph-library.r4b#1.0.0 http://hl7.org/fhir/us/ph-library/package.r4b.tgz http://hl7.org/fhir/us/ph-library/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 18 Aug 2023 00:42:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.bser.r4#2.0.0-ballot Package hl7.fhir.us.bser.r4#2.0.0-ballot http://hl7.org/fhir/us/bser/2023Sep/package.r4.tgz http://hl7.org/fhir/us/bser/2023Sep/package.r4.tgz HL7, Inc 4.0.1 IG Mon, 31 Jul 2023 12:46:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.bser.r4b#2.0.0-ballot Package hl7.fhir.us.bser.r4b#2.0.0-ballot http://hl7.org/fhir/us/bser/2023Sep/package.r4b.tgz http://hl7.org/fhir/us/bser/2023Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Mon, 31 Jul 2023 12:46:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.ndh.r4#1.0.0-ballot Package hl7.fhir.us.ndh.r4#1.0.0-ballot http://hl7.org/fhir/us/ndh/2023Sep/package.r4.tgz http://hl7.org/fhir/us/ndh/2023Sep/package.r4.tgz HL7, Inc 4.0.1 IG Mon, 31 Jul 2023 01:36:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.ndh.r4b#1.0.0-ballot Package hl7.fhir.us.ndh.r4b#1.0.0-ballot http://hl7.org/fhir/us/ndh/2023Sep/package.r4b.tgz http://hl7.org/fhir/us/ndh/2023Sep/package.r4b.tgz HL7, Inc 4.3.0 IG Mon, 31 Jul 2023 01:36:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.codex-radiation-therapy.r4#1.0.0 CodeX™ Radiation Therapy is an initiative intended to assemble a core set of structured data elements for radiation therapy electronic health records. (built Fri, Jul 28, 2023 13:01+0000+00:00) http://hl7.org/fhir/us/codex-radiation-therapy/STU1/package.r4.tgz http://hl7.org/fhir/us/codex-radiation-therapy/STU1/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 28 Jul 2023 23:57:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.codex-radiation-therapy.r4b#1.0.0 CodeX™ Radiation Therapy is an initiative intended to assemble a core set of structured data elements for radiation therapy electronic health records. (built Fri, Jul 28, 2023 13:01+0000+00:00) http://hl7.org/fhir/us/codex-radiation-therapy/STU1/package.r4b.tgz http://hl7.org/fhir/us/codex-radiation-therapy/STU1/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 28 Jul 2023 23:57:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.medmorph.r4#1.0.0 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) http://hl7.org/fhir/us/medmorph/package.r4.tgz http://hl7.org/fhir/us/medmorph/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 09 Jun 2023 05:20:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.medmorph.r4b#1.0.0 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) http://hl7.org/fhir/us/medmorph/package.r4b.tgz http://hl7.org/fhir/us/medmorph/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 09 Jun 2023 05:20:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.identity-matching.r4#1.0.0 Package hl7.fhir.us.identity-matching.r4#1.0.0 http://hl7.org/fhir/us/identity-matching/STU1/package.r4.tgz http://hl7.org/fhir/us/identity-matching/STU1/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 02 Jun 2023 13:11:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.identity-matching.r4b#1.0.0 Package hl7.fhir.us.identity-matching.r4b#1.0.0 http://hl7.org/fhir/us/identity-matching/STU1/package.r4b.tgz http://hl7.org/fhir/us/identity-matching/STU1/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 02 Jun 2023 13:11:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.military-service.r4#1.0.0 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) http://hl7.org/fhir/us/military-service/package.r4.tgz http://hl7.org/fhir/us/military-service/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 31 May 2023 01:18:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.military-service.r4b#1.0.0 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) http://hl7.org/fhir/us/military-service/package.r4b.tgz http://hl7.org/fhir/us/military-service/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 31 May 2023 01:18:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.vulcan-rwd.r4#1.0.0 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) http://hl7.org/fhir/uv/vulcan-rwd/package.r4.tgz http://hl7.org/fhir/uv/vulcan-rwd/package.r4.tgz HL7, Inc 4.0.1 IG Sat, 27 May 2023 00:10:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.vulcan-rwd.r4b#1.0.0 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) http://hl7.org/fhir/uv/vulcan-rwd/package.r4b.tgz http://hl7.org/fhir/uv/vulcan-rwd/package.r4b.tgz HL7, Inc 4.3.0 IG Sat, 27 May 2023 00:10:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.vulcan-rwd.r4#1.0.0-ballot 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 Sun, Dec 4, 2022 19:33+0000+00:00) http://hl7.org/fhir/uv/vulcan-rwd/2023Jan/package.r4.tgz http://hl7.org/fhir/uv/vulcan-rwd/2023Jan/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 26 May 2023 23:53:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.vulcan-rwd.r4b#1.0.0-ballot 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 Sun, Dec 4, 2022 19:33+0000+00:00) http://hl7.org/fhir/uv/vulcan-rwd/2023Jan/package.r4b.tgz http://hl7.org/fhir/uv/vulcan-rwd/2023Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 26 May 2023 23:53:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.specialty-rx.r4#2.0.0 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) http://hl7.org/fhir/us/specialty-rx/package.r4.tgz http://hl7.org/fhir/us/specialty-rx/package.r4.tgz HL7, Inc 4.0.1 IG Fri, 05 May 2023 00:48:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.specialty-rx.r4b#2.0.0 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) http://hl7.org/fhir/us/specialty-rx/package.r4b.tgz http://hl7.org/fhir/us/specialty-rx/package.r4b.tgz HL7, Inc 4.3.0 IG Fri, 05 May 2023 00:48:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.sirb.r4#1.0.0 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) http://hl7.org/fhir/us/sirb/STU1/package.r4.tgz http://hl7.org/fhir/us/sirb/STU1/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 20 Apr 2023 23:54:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.sirb.r4b#1.0.0 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) http://hl7.org/fhir/us/sirb/STU1/package.r4b.tgz http://hl7.org/fhir/us/sirb/STU1/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 20 Apr 2023 23:54:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.hai-ltcf.r4#1.0.0 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. As reports are modified and new report types are defined, CDC and Health Level Seven (HL7) will develop and publish additional constraints. Throughout 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. Note 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). ### Relationship to Another Standard HL7 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. In this release, the new forms included in both the CDA and FHIR standards are: * **NHSN HAI LTCF Population Summary Report**: MDRO and CDI LabID Event Reporting Monthly Summary Data for LTCF * **NHSN HAI LTCF Single-Person Event Report**: Laboratory-identified MDRO or CDI Event for LTCF For further details see the [NHSN website](https://www.cdc.gov/nhsn/) for reporting healthcare-associated infections in long-term care facilities. ### Audience The audience for this work is all developers of software systems who want to enable their systems for reporting HAI data to the NHSN. ### Change Notification Process CDC 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. ### Acknowledgements This 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). Special 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. The 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. |-----|-----|-----|-----| |Primary Editor:|Sarah Gaunt|Lantana Consulting Group|sarah.gaunt@lantanagroup.com| |Primary Editor:|Zabrina Gonzaga|Lantana Consulting Group|zabrina.gonzaga@lantanagroup.com| |Primary Editor:|Dave deRoode|Lantana Consulting Group|david.deroode@lantanagroup.com| |Co-Editor:|Jeneita Bell, MD, MPH|CDC|hpq8@cdc.gov| |Co-Editor:|Angella Antilla PhD, MSN|CDC|vtb9@cdc.gov| |Co-Editor:|Daniel Pollock, M.D.|CDC|DPollock@cdc.gov| |Co-Editor:|Ahmed Tahir|Leidos Consultant to CDC/NHSN|nmn8@cdc.gov| |Co-Editor:|Mindy Durrance|Leidos Consultant to CDC/NHSN|mdq1@cdc.gov| |Co-Editor:|Sheri Chernetsky Tejedor, MD|CDC|yei9@cdc.gov| |Co-Editor:|Sheila Abner|CDC|sha8@cdc.gov| |Co-Chair:|Erin Holt MPH|Tennessee Department of Health|erin.holt@tn.gov| |Co-Chair:|Laura Rappleye|Altarum|laura.rappleye@altarum.org| |Co-Chair:|Craig Newman|Altarum|craig.newman@altarum.org| |Co-Chair:|Danny Wise|Allscripts|danny.wise@allscripts.com| |Co-Chair:|Joginder Madra|Madra Consulting Inc.|hl7@madraconsulting.com| |Co-Chair:|Gaye Dolin M.S.N., R.N. |Intelligent Medical Objects |gdolin@imo-online.com| |Co-Chair:|Calvin Beebe|Mayo Clinic|cbeebe@mayo.edu| |Co-Chair:|Austin Kreisler|Leidos Consultant to CDC/NHSN|duz1@cdc.gov| |Co-Chair:|Andrew Statler|Cerner Corp|andrew.statler@cerner.com| |Co-Chair:|Sean McIlvenna| Lantana Consulting Group|sean.mcilvenna@lantanagroup.com| |Co-Chair:|Benjamin Flessner|Redox|benjamin@redoxengine.com| |Co-Editor:|Beau Bannerman|Lantana Consulting Group|beau.bannerman@lantanagroup.com| |Technical Editor:|Diana Wright|Lantana Consulting Group|diana.wright@lantanagroup.com| |Technical Editor:|Chris Hannigan|Lantana Consulting Group|chris.hannigan@lantanagroup.com| (built Mon, Jan 9, 2023 21:55+0000+00:00) http://hl7.org/fhir/us/hai-ltcf/STU1/package.r4.tgz http://hl7.org/fhir/us/hai-ltcf/STU1/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 20 Apr 2023 01:10:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.hai-ltcf.r4b#1.0.0 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. As reports are modified and new report types are defined, CDC and Health Level Seven (HL7) will develop and publish additional constraints. Throughout 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. Note 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). ### Relationship to Another Standard HL7 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. In this release, the new forms included in both the CDA and FHIR standards are: * **NHSN HAI LTCF Population Summary Report**: MDRO and CDI LabID Event Reporting Monthly Summary Data for LTCF * **NHSN HAI LTCF Single-Person Event Report**: Laboratory-identified MDRO or CDI Event for LTCF For further details see the [NHSN website](https://www.cdc.gov/nhsn/) for reporting healthcare-associated infections in long-term care facilities. ### Audience The audience for this work is all developers of software systems who want to enable their systems for reporting HAI data to the NHSN. ### Change Notification Process CDC 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. ### Acknowledgements This 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). Special 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. The 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. |-----|-----|-----|-----| |Primary Editor:|Sarah Gaunt|Lantana Consulting Group|sarah.gaunt@lantanagroup.com| |Primary Editor:|Zabrina Gonzaga|Lantana Consulting Group|zabrina.gonzaga@lantanagroup.com| |Primary Editor:|Dave deRoode|Lantana Consulting Group|david.deroode@lantanagroup.com| |Co-Editor:|Jeneita Bell, MD, MPH|CDC|hpq8@cdc.gov| |Co-Editor:|Angella Antilla PhD, MSN|CDC|vtb9@cdc.gov| |Co-Editor:|Daniel Pollock, M.D.|CDC|DPollock@cdc.gov| |Co-Editor:|Ahmed Tahir|Leidos Consultant to CDC/NHSN|nmn8@cdc.gov| |Co-Editor:|Mindy Durrance|Leidos Consultant to CDC/NHSN|mdq1@cdc.gov| |Co-Editor:|Sheri Chernetsky Tejedor, MD|CDC|yei9@cdc.gov| |Co-Editor:|Sheila Abner|CDC|sha8@cdc.gov| |Co-Chair:|Erin Holt MPH|Tennessee Department of Health|erin.holt@tn.gov| |Co-Chair:|Laura Rappleye|Altarum|laura.rappleye@altarum.org| |Co-Chair:|Craig Newman|Altarum|craig.newman@altarum.org| |Co-Chair:|Danny Wise|Allscripts|danny.wise@allscripts.com| |Co-Chair:|Joginder Madra|Madra Consulting Inc.|hl7@madraconsulting.com| |Co-Chair:|Gaye Dolin M.S.N., R.N. |Intelligent Medical Objects |gdolin@imo-online.com| |Co-Chair:|Calvin Beebe|Mayo Clinic|cbeebe@mayo.edu| |Co-Chair:|Austin Kreisler|Leidos Consultant to CDC/NHSN|duz1@cdc.gov| |Co-Chair:|Andrew Statler|Cerner Corp|andrew.statler@cerner.com| |Co-Chair:|Sean McIlvenna| Lantana Consulting Group|sean.mcilvenna@lantanagroup.com| |Co-Chair:|Benjamin Flessner|Redox|benjamin@redoxengine.com| |Co-Editor:|Beau Bannerman|Lantana Consulting Group|beau.bannerman@lantanagroup.com| |Technical Editor:|Diana Wright|Lantana Consulting Group|diana.wright@lantanagroup.com| |Technical Editor:|Chris Hannigan|Lantana Consulting Group|chris.hannigan@lantanagroup.com| (built Mon, Jan 9, 2023 21:55+0000+00:00) http://hl7.org/fhir/us/hai-ltcf/STU1/package.r4b.tgz http://hl7.org/fhir/us/hai-ltcf/STU1/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 20 Apr 2023 01:10:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.hai-ltcf.r4#1.1.0 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. As reports are modified and new report types are defined, CDC and Health Level Seven (HL7) will develop and publish additional constraints. Throughout 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. Note 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). ### Relationship to Another Standard HL7 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. In this release, the new forms included in both the CDA and FHIR standards are: * **NHSN HAI LTCF Population Summary Report**: MDRO and CDI LabID Event Reporting Monthly Summary Data for LTCF * **NHSN HAI LTCF Single-Person Event Report**: Laboratory-identified MDRO or CDI Event for LTCF For further details see the [NHSN website](https://www.cdc.gov/nhsn/) for reporting healthcare-associated infections in long-term care facilities. ### Audience The audience for this work is all developers of software systems who want to enable their systems for reporting HAI data to the NHSN. ### Change Notification Process CDC 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. ### Acknowledgements This 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). Special 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. The 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. |-----|-----|-----|-----| |Primary Editor:|Sarah Gaunt|Lantana Consulting Group|sarah.gaunt@lantanagroup.com| |Primary Editor:|Zabrina Gonzaga|Lantana Consulting Group|zabrina.gonzaga@lantanagroup.com| |Primary Editor:|Dave deRoode|Lantana Consulting Group|david.deroode@lantanagroup.com| |Co-Editor:|Jeneita Bell, MD, MPH|CDC|hpq8@cdc.gov| |Co-Editor:|Angella Antilla PhD, MSN|CDC|vtb9@cdc.gov| |Co-Editor:|Daniel Pollock, M.D.|CDC|DPollock@cdc.gov| |Co-Editor:|Ahmed Tahir|Leidos Consultant to CDC/NHSN|nmn8@cdc.gov| |Co-Editor:|Mindy Durrance|Leidos Consultant to CDC/NHSN|mdq1@cdc.gov| |Co-Editor:|Sheri Chernetsky Tejedor, MD|CDC|yei9@cdc.gov| |Co-Editor:|Sheila Abner|CDC|sha8@cdc.gov| |Co-Chair:|Erin Holt MPH|Tennessee Department of Health|erin.holt@tn.gov| |Co-Chair:|Laura Rappleye|Altarum|laura.rappleye@altarum.org| |Co-Chair:|Craig Newman|Altarum|craig.newman@altarum.org| |Co-Chair:|Danny Wise|Allscripts|danny.wise@allscripts.com| |Co-Chair:|Joginder Madra|Madra Consulting Inc.|hl7@madraconsulting.com| |Co-Chair:|Gaye Dolin M.S.N., R.N. |Intelligent Medical Objects |gdolin@imo-online.com| |Co-Chair:|Calvin Beebe|Mayo Clinic|cbeebe@mayo.edu| |Co-Chair:|Austin Kreisler|Leidos Consultant to CDC/NHSN|duz1@cdc.gov| |Co-Chair:|Andrew Statler|Cerner Corp|andrew.statler@cerner.com| |Co-Chair:|Sean McIlvenna| Lantana Consulting Group|sean.mcilvenna@lantanagroup.com| |Co-Chair:|Benjamin Flessner|Redox|benjamin@redoxengine.com| |Co-Editor:|Beau Bannerman|Lantana Consulting Group|beau.bannerman@lantanagroup.com| |Technical Editor:|Diana Wright|Lantana Consulting Group|diana.wright@lantanagroup.com| |Technical Editor:|Chris Hannigan|Lantana Consulting Group|chris.hannigan@lantanagroup.com| (built Wed, Apr 19, 2023 15:05+0000+00:00) http://hl7.org/fhir/us/hai-ltcf/package.r4.tgz http://hl7.org/fhir/us/hai-ltcf/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 20 Apr 2023 01:10:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.hai-ltcf.r4b#1.1.0 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. As reports are modified and new report types are defined, CDC and Health Level Seven (HL7) will develop and publish additional constraints. Throughout 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. Note 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). ### Relationship to Another Standard HL7 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. In this release, the new forms included in both the CDA and FHIR standards are: * **NHSN HAI LTCF Population Summary Report**: MDRO and CDI LabID Event Reporting Monthly Summary Data for LTCF * **NHSN HAI LTCF Single-Person Event Report**: Laboratory-identified MDRO or CDI Event for LTCF For further details see the [NHSN website](https://www.cdc.gov/nhsn/) for reporting healthcare-associated infections in long-term care facilities. ### Audience The audience for this work is all developers of software systems who want to enable their systems for reporting HAI data to the NHSN. ### Change Notification Process CDC 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. ### Acknowledgements This 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). Special 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. The 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. |-----|-----|-----|-----| |Primary Editor:|Sarah Gaunt|Lantana Consulting Group|sarah.gaunt@lantanagroup.com| |Primary Editor:|Zabrina Gonzaga|Lantana Consulting Group|zabrina.gonzaga@lantanagroup.com| |Primary Editor:|Dave deRoode|Lantana Consulting Group|david.deroode@lantanagroup.com| |Co-Editor:|Jeneita Bell, MD, MPH|CDC|hpq8@cdc.gov| |Co-Editor:|Angella Antilla PhD, MSN|CDC|vtb9@cdc.gov| |Co-Editor:|Daniel Pollock, M.D.|CDC|DPollock@cdc.gov| |Co-Editor:|Ahmed Tahir|Leidos Consultant to CDC/NHSN|nmn8@cdc.gov| |Co-Editor:|Mindy Durrance|Leidos Consultant to CDC/NHSN|mdq1@cdc.gov| |Co-Editor:|Sheri Chernetsky Tejedor, MD|CDC|yei9@cdc.gov| |Co-Editor:|Sheila Abner|CDC|sha8@cdc.gov| |Co-Chair:|Erin Holt MPH|Tennessee Department of Health|erin.holt@tn.gov| |Co-Chair:|Laura Rappleye|Altarum|laura.rappleye@altarum.org| |Co-Chair:|Craig Newman|Altarum|craig.newman@altarum.org| |Co-Chair:|Danny Wise|Allscripts|danny.wise@allscripts.com| |Co-Chair:|Joginder Madra|Madra Consulting Inc.|hl7@madraconsulting.com| |Co-Chair:|Gaye Dolin M.S.N., R.N. |Intelligent Medical Objects |gdolin@imo-online.com| |Co-Chair:|Calvin Beebe|Mayo Clinic|cbeebe@mayo.edu| |Co-Chair:|Austin Kreisler|Leidos Consultant to CDC/NHSN|duz1@cdc.gov| |Co-Chair:|Andrew Statler|Cerner Corp|andrew.statler@cerner.com| |Co-Chair:|Sean McIlvenna| Lantana Consulting Group|sean.mcilvenna@lantanagroup.com| |Co-Chair:|Benjamin Flessner|Redox|benjamin@redoxengine.com| |Co-Editor:|Beau Bannerman|Lantana Consulting Group|beau.bannerman@lantanagroup.com| |Technical Editor:|Diana Wright|Lantana Consulting Group|diana.wright@lantanagroup.com| |Technical Editor:|Chris Hannigan|Lantana Consulting Group|chris.hannigan@lantanagroup.com| (built Wed, Apr 19, 2023 15:05+0000+00:00) http://hl7.org/fhir/us/hai-ltcf/package.r4b.tgz http://hl7.org/fhir/us/hai-ltcf/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 20 Apr 2023 01:10:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.vulcan-schedule.r4#1.0.0 FHIR Implementation Guide representing a Clinical Study Schedule of Activities (built Tue, Apr 18, 2023 16:39+0000+00:00) http://hl7.org/fhir/uv/vulcan-schedule/package.r4.tgz http://hl7.org/fhir/uv/vulcan-schedule/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 19 Apr 2023 02:45:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.vulcan-schedule.r4b#1.0.0 FHIR Implementation Guide representing a Clinical Study Schedule of Activities (built Tue, Apr 18, 2023 16:39+0000+00:00) http://hl7.org/fhir/uv/vulcan-schedule/package.r4b.tgz http://hl7.org/fhir/uv/vulcan-schedule/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 19 Apr 2023 02:45:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.vulcan-schedule.r4#1.0.0-ballot FHIR Implementation Guide representing a Clinical Study Schedule of Activites (built Sun, Dec 4, 2022 20:06+0000+00:00) http://hl7.org/fhir/uv/vulcan-schedule/2023Jan/package.r4.tgz http://hl7.org/fhir/uv/vulcan-schedule/2023Jan/package.r4.tgz HL7, Inc 4.0.1 IG Wed, 19 Apr 2023 02:44:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.vulcan-schedule.r4b#1.0.0-ballot FHIR Implementation Guide representing a Clinical Study Schedule of Activites (built Sun, Dec 4, 2022 20:06+0000+00:00) http://hl7.org/fhir/uv/vulcan-schedule/2023Jan/package.r4b.tgz http://hl7.org/fhir/uv/vulcan-schedule/2023Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 19 Apr 2023 02:44:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.security-label-ds4p.r4#1.0.0 FHIR data segmentation for privacy security label implementation guide (built Mon, Apr 17, 2023 19:19+0000+00:00) http://hl7.org/fhir/uv/security-label-ds4p/STU1/package.r4.tgz http://hl7.org/fhir/uv/security-label-ds4p/STU1/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 18 Apr 2023 05:29:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.uv.security-label-ds4p.r4b#1.0.0 FHIR data segmentation for privacy security label implementation guide (built Mon, Apr 17, 2023 19:19+0000+00:00) http://hl7.org/fhir/uv/security-label-ds4p/STU1/package.r4b.tgz http://hl7.org/fhir/uv/security-label-ds4p/STU1/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 18 Apr 2023 05:29:00 +1000 Added from file system scan on 28/10/2025 hl7.fhir.us.mihr.r4#1.0.0 ### Scope The 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. This 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. ### Background The 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). The 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. Future 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. ### Maternal Research Use Cases This 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. Initial 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: * 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. * Hypertensive Disorders of pregnancy: This use case focuses on women with a diagnosis of hypertensive disorders of pregnancy. In 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. In the future, the IG will expand this framework to a range of use cases including: * Risks for children related to maternal exposure to medications taken during pregnancy * Potential adverse maternal obstetric history impacts on child outcomes * Access to relevant sensitive health information * Retrospective population-based analysis of inherited disorders * The impacts of [work habits, work environment, and work-associated health insurance](http://hl7.org/fhir/us/odh/) impacts to pregnancy and maternal health This guide fundamentally relies on creating structural relationships between: * Maternal and child records to effectively diagnose and treat otherwise fatal child outcomes * Maternal and child birth records and/or maternal and child death records * Maternal and child records in multiple disparate systems ### Audience The 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. ### Authors & Project Team This table lists the authors, subject matter experts, and the affiliations which contributed to this standard. <style type="text/css"> .tg {border-collapse:collapse;border-spacing:0;} .tg td{border-color:black;border-style:solid;border-width:1px;font-family:Arial, sans-serif;font-size:14px; overflow:hidden;padding:10px 5px;word-break:normal;} .tg th{border-color:black;border-style:solid;border-width:1px;font-family:Arial, sans-serif;font-size:14px; font-weight:normal;overflow:hidden;padding:10px 5px;word-break:normal;} .tg .tg-4erg{border-color:inherit;font-style:italic;font-weight:bold;text-align:left;vertical-align:top} .tg .tg-0r4h{border-color:inherit;font-family:serif !important;font-weight:bold;text-align:left;vertical-align:top} .tg .tg-fymr{border-color:inherit;font-weight:bold;text-align:left;vertical-align:top} .tg .tg-0pky{border-color:inherit;text-align:left;vertical-align:top} </style> <table class="tg"> <thead> <tr> <th class="tg-fymr">Name &amp; Affiliation</th> <th class="tg-0r4h">Role</th> <th class="tg-fymr">Contact</th> </tr> </thead> <tbody> <tr> <td class="tg-4erg">Lantana Consulting Group</td> <td class="tg-0pky"> </td> <td class="tg-0pky"> </td> </tr> <tr> <td class="tg-0pky">Courtney Panaia-Rodi </td> <td class="tg-0pky">Project Executive</td> <td class="tg-0pky">courtney.panaia-rodi@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Wendy Wise</td> <td class="tg-0pky">Project Manager</td> <td class="tg-0pky">wendy.wise@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Lani Johnson</td> <td class="tg-0pky">Associate Project Manager</td> <td class="tg-0pky">lani.johnson@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Rick Geimer</td> <td class="tg-0pky">FHIR Subject Matter Expert</td> <td class="tg-0pky">rick.geimer@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Zabrina Gonzaga</td> <td class="tg-0pky">Terminology Subject Matter Expert</td> <td class="tg-0pky">zabrina.gonzaga@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Sarah Gaunt</td> <td class="tg-0pky">Senior FHIR/CDA Analyst</td> <td class="tg-0pky">sarah.gaunt@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Dave deRoode</td> <td class="tg-0pky">FHIR/CDA Analyst</td> <td class="tg-0pky">david.deroode@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Ming Dunajick</td> <td class="tg-0pky">FHIR/CDA Analyst</td> <td class="tg-0pky">ming.dunajick@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Ruby Nash</td> <td class="tg-0pky">FHIR Analyst</td> <td class="tg-0pky">ruby.nash@lantanagroup.com</td> </tr> <tr> <td class="tg-4erg">Office of the Assistant Secretary for Planning and Evaluation (ASPE)</td> <td class="tg-0pky"> </td> <td class="tg-0pky"> </td> </tr> <tr> <td class="tg-0pky">Violanda Grigorescu, MD, MSPH</td> <td class="tg-0pky">Senior Health Scientist <br>Division of Healthcare Quality and Outcomes, Office of Health Policy</td> <td class="tg-0pky">violanda.grigorescu@hhs.gov</td> </tr> <tr> <td class="tg-4erg">Centers for Disease Control and Prevention (CDC)</td> <td class="tg-0pky"> </td> <td class="tg-0pky"> </td> </tr> <tr> <td class="tg-0pky">Margaret Lampe, RN, MPH</td> <td class="tg-0pky">Nurse Epidemiologist &amp; Project Officer <br>Perinatal HIV Prevention Program</td> <td class="tg-0pky">mol0@cdc.gov</td> </tr> <tr> <td class="tg-0pky">Lisa Romero, DrPH</td> <td class="tg-0pky">Health Scientist <br>Division of Adolescent School Health</td> <td class="tg-0pky">eon1@cdc.gov</td> </tr> <tr> <td class="tg-4erg">National Institutes of Health (NIH) <br>Eunice Kennedy Shriver National Institute of Child Health and Human Development (NICHD) <br>National Information Center on Health Services Research and Health Care Technology (NICHSR)</td> <td class="tg-0pky"> </td> <td class="tg-0pky"> </td> </tr> <tr> <td class="tg-0pky">Alison Cernich</td> <td class="tg-0pky">NICHD Deputy Director</td> <td class="tg-0pky">alison.cernich@nih.hhs.gov</td> </tr> <tr> <td class="tg-0pky">John (Jack) Moye, Jr., MD</td> <td class="tg-0pky">Acting Director - National Children's Study <br>NICHD Medical Officer - Maternal &amp; Pediatric Infectious Disease Branch</td> <td class="tg-0pky">moyej@exchange.nih.gov</td> </tr> <tr> <td class="tg-0pky">Nahida Chakhtoura, MD, MsGH</td> <td class="tg-0pky">NICHD Medical Officer <br>Maternal and Pediatric Infectious Disease Branch</td> <td class="tg-0pky">nahida.chakhtoura@nih.gov</td> </tr> <tr> <td class="tg-0pky">Juanita Chinn, PhD</td> <td class="tg-0pky">NICHD Program Director <br>Population Dynamics Branch</td> <td class="tg-0pky">juanita.chinn@nih.gov</td> </tr> <tr> <td class="tg-0pky">Valerie Cotton</td> <td class="tg-0pky">NICHD Deputy Director <br>Office of Data Science and Sharing</td> <td class="tg-0pky">valerie.cotton@nih.gov</td> </tr> <tr> <td class="tg-0pky">Liz Amos, MLIS</td> <td class="tg-0pky">Special Assistant to the Chief Health Data Standards Officer <br>National Library of Medicine</td> <td class="tg-0pky">liz.amos@nih.gov</td> </tr> <tr> <td class="tg-4erg">Office of the National Coordinator for Health IT (ONC)</td> <td class="tg-0pky"> </td> <td class="tg-0pky"> </td> </tr> <tr> <td class="tg-0pky">Carmen Smiley</td> <td class="tg-0pky">IT Specialist (Systems Analysis)</td> <td class="tg-0pky">carmen.smiley@hhs.gov</td> </tr> <tr> <td class="tg-0pky">Rachel Abbey</td> <td class="tg-0pky">Public Health Analyst &amp; Program Officer</td> <td class="tg-0pky">rachel.abbey@hhs.gov</td> </tr> <tr> <td class="tg-0pky">Stephanie Garcia</td> <td class="tg-0pky">Senior Program Analyst</td> <td class="tg-0pky">stephanie.garcia@hhs.gov</td> </tr> <tr> <td class="tg-0pky">Brittney Boakye, MPH</td> <td class="tg-0pky">Program Assistant <br>Scientific Advancement Branch</td> <td class="tg-0pky">brittney.boakye@hhs.gov<br></td> </tr> <tr> <td class="tg-0pky">Alan Taylor</td> <td class="tg-0pky">Medical Informatics Officer, Standards and Terminology</td> <td class="tg-0pky">albert.taylor@hhs.gov</td> </tr> </tbody> </table> ### Acknowledgements This 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. The 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. Health Level Seven, HL7, CDA, CCD, FHIR and the [FLAME DESIGN] are registered trademarks of Health Level Seven International, registered in the US Trademark Office. This 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. This 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) http://hl7.org/fhir/us/mihr/package.r4.tgz http://hl7.org/fhir/us/mihr/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 30 Mar 2023 06:44:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.mihr.r4b#1.0.0 ### Scope The 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. This 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. ### Background The 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). The 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. Future 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. ### Maternal Research Use Cases This 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. Initial 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: * 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. * Hypertensive Disorders of pregnancy: This use case focuses on women with a diagnosis of hypertensive disorders of pregnancy. In 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. In the future, the IG will expand this framework to a range of use cases including: * Risks for children related to maternal exposure to medications taken during pregnancy * Potential adverse maternal obstetric history impacts on child outcomes * Access to relevant sensitive health information * Retrospective population-based analysis of inherited disorders * The impacts of [work habits, work environment, and work-associated health insurance](http://hl7.org/fhir/us/odh/) impacts to pregnancy and maternal health This guide fundamentally relies on creating structural relationships between: * Maternal and child records to effectively diagnose and treat otherwise fatal child outcomes * Maternal and child birth records and/or maternal and child death records * Maternal and child records in multiple disparate systems ### Audience The 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. ### Authors & Project Team This table lists the authors, subject matter experts, and the affiliations which contributed to this standard. <style type="text/css"> .tg {border-collapse:collapse;border-spacing:0;} .tg td{border-color:black;border-style:solid;border-width:1px;font-family:Arial, sans-serif;font-size:14px; overflow:hidden;padding:10px 5px;word-break:normal;} .tg th{border-color:black;border-style:solid;border-width:1px;font-family:Arial, sans-serif;font-size:14px; font-weight:normal;overflow:hidden;padding:10px 5px;word-break:normal;} .tg .tg-4erg{border-color:inherit;font-style:italic;font-weight:bold;text-align:left;vertical-align:top} .tg .tg-0r4h{border-color:inherit;font-family:serif !important;font-weight:bold;text-align:left;vertical-align:top} .tg .tg-fymr{border-color:inherit;font-weight:bold;text-align:left;vertical-align:top} .tg .tg-0pky{border-color:inherit;text-align:left;vertical-align:top} </style> <table class="tg"> <thead> <tr> <th class="tg-fymr">Name &amp; Affiliation</th> <th class="tg-0r4h">Role</th> <th class="tg-fymr">Contact</th> </tr> </thead> <tbody> <tr> <td class="tg-4erg">Lantana Consulting Group</td> <td class="tg-0pky"> </td> <td class="tg-0pky"> </td> </tr> <tr> <td class="tg-0pky">Courtney Panaia-Rodi </td> <td class="tg-0pky">Project Executive</td> <td class="tg-0pky">courtney.panaia-rodi@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Wendy Wise</td> <td class="tg-0pky">Project Manager</td> <td class="tg-0pky">wendy.wise@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Lani Johnson</td> <td class="tg-0pky">Associate Project Manager</td> <td class="tg-0pky">lani.johnson@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Rick Geimer</td> <td class="tg-0pky">FHIR Subject Matter Expert</td> <td class="tg-0pky">rick.geimer@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Zabrina Gonzaga</td> <td class="tg-0pky">Terminology Subject Matter Expert</td> <td class="tg-0pky">zabrina.gonzaga@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Sarah Gaunt</td> <td class="tg-0pky">Senior FHIR/CDA Analyst</td> <td class="tg-0pky">sarah.gaunt@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Dave deRoode</td> <td class="tg-0pky">FHIR/CDA Analyst</td> <td class="tg-0pky">david.deroode@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Ming Dunajick</td> <td class="tg-0pky">FHIR/CDA Analyst</td> <td class="tg-0pky">ming.dunajick@lantanagroup.com</td> </tr> <tr> <td class="tg-0pky">Ruby Nash</td> <td class="tg-0pky">FHIR Analyst</td> <td class="tg-0pky">ruby.nash@lantanagroup.com</td> </tr> <tr> <td class="tg-4erg">Office of the Assistant Secretary for Planning and Evaluation (ASPE)</td> <td class="tg-0pky"> </td> <td class="tg-0pky"> </td> </tr> <tr> <td class="tg-0pky">Violanda Grigorescu, MD, MSPH</td> <td class="tg-0pky">Senior Health Scientist <br>Division of Healthcare Quality and Outcomes, Office of Health Policy</td> <td class="tg-0pky">violanda.grigorescu@hhs.gov</td> </tr> <tr> <td class="tg-4erg">Centers for Disease Control and Prevention (CDC)</td> <td class="tg-0pky"> </td> <td class="tg-0pky"> </td> </tr> <tr> <td class="tg-0pky">Margaret Lampe, RN, MPH</td> <td class="tg-0pky">Nurse Epidemiologist &amp; Project Officer <br>Perinatal HIV Prevention Program</td> <td class="tg-0pky">mol0@cdc.gov</td> </tr> <tr> <td class="tg-0pky">Lisa Romero, DrPH</td> <td class="tg-0pky">Health Scientist <br>Division of Adolescent School Health</td> <td class="tg-0pky">eon1@cdc.gov</td> </tr> <tr> <td class="tg-4erg">National Institutes of Health (NIH) <br>Eunice Kennedy Shriver National Institute of Child Health and Human Development (NICHD) <br>National Information Center on Health Services Research and Health Care Technology (NICHSR)</td> <td class="tg-0pky"> </td> <td class="tg-0pky"> </td> </tr> <tr> <td class="tg-0pky">Alison Cernich</td> <td class="tg-0pky">NICHD Deputy Director</td> <td class="tg-0pky">alison.cernich@nih.hhs.gov</td> </tr> <tr> <td class="tg-0pky">John (Jack) Moye, Jr., MD</td> <td class="tg-0pky">Acting Director - National Children's Study <br>NICHD Medical Officer - Maternal &amp; Pediatric Infectious Disease Branch</td> <td class="tg-0pky">moyej@exchange.nih.gov</td> </tr> <tr> <td class="tg-0pky">Nahida Chakhtoura, MD, MsGH</td> <td class="tg-0pky">NICHD Medical Officer <br>Maternal and Pediatric Infectious Disease Branch</td> <td class="tg-0pky">nahida.chakhtoura@nih.gov</td> </tr> <tr> <td class="tg-0pky">Juanita Chinn, PhD</td> <td class="tg-0pky">NICHD Program Director <br>Population Dynamics Branch</td> <td class="tg-0pky">juanita.chinn@nih.gov</td> </tr> <tr> <td class="tg-0pky">Valerie Cotton</td> <td class="tg-0pky">NICHD Deputy Director <br>Office of Data Science and Sharing</td> <td class="tg-0pky">valerie.cotton@nih.gov</td> </tr> <tr> <td class="tg-0pky">Liz Amos, MLIS</td> <td class="tg-0pky">Special Assistant to the Chief Health Data Standards Officer <br>National Library of Medicine</td> <td class="tg-0pky">liz.amos@nih.gov</td> </tr> <tr> <td class="tg-4erg">Office of the National Coordinator for Health IT (ONC)</td> <td class="tg-0pky"> </td> <td class="tg-0pky"> </td> </tr> <tr> <td class="tg-0pky">Carmen Smiley</td> <td class="tg-0pky">IT Specialist (Systems Analysis)</td> <td class="tg-0pky">carmen.smiley@hhs.gov</td> </tr> <tr> <td class="tg-0pky">Rachel Abbey</td> <td class="tg-0pky">Public Health Analyst &amp; Program Officer</td> <td class="tg-0pky">rachel.abbey@hhs.gov</td> </tr> <tr> <td class="tg-0pky">Stephanie Garcia</td> <td class="tg-0pky">Senior Program Analyst</td> <td class="tg-0pky">stephanie.garcia@hhs.gov</td> </tr> <tr> <td class="tg-0pky">Brittney Boakye, MPH</td> <td class="tg-0pky">Program Assistant <br>Scientific Advancement Branch</td> <td class="tg-0pky">brittney.boakye@hhs.gov<br></td> </tr> <tr> <td class="tg-0pky">Alan Taylor</td> <td class="tg-0pky">Medical Informatics Officer, Standards and Terminology</td> <td class="tg-0pky">albert.taylor@hhs.gov</td> </tr> </tbody> </table> ### Acknowledgements This 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. The 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. Health Level Seven, HL7, CDA, CCD, FHIR and the [FLAME DESIGN] are registered trademarks of Health Level Seven International, registered in the US Trademark Office. This 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. This 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) http://hl7.org/fhir/us/mihr/package.r4b.tgz http://hl7.org/fhir/us/mihr/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 30 Mar 2023 06:44:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-ra.r4#2.0.0-ballot 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 Tue, Mar 28, 2023 02:00+0000+00:00) http://hl7.org/fhir/us/davinci-ra/2023May/package.r4.tgz http://hl7.org/fhir/us/davinci-ra/2023May/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 28 Mar 2023 13:12:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-ra.r4b#2.0.0-ballot 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 Tue, Mar 28, 2023 02:00+0000+00:00) http://hl7.org/fhir/us/davinci-ra/2023May/package.r4b.tgz http://hl7.org/fhir/us/davinci-ra/2023May/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 28 Mar 2023 13:12:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.r5.corexml#5.0.0 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) http://hl7.org/fhir/hl7.fhir.r5.corexml.tgz http://hl7.org/fhir/hl7.fhir.r5.corexml.tgz HL7, Inc 5.0.0 IG Mon, 27 Mar 2023 17:04:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.odh.r4#1.3.0 **HL7 FHIR Profile: Occupational Data for Health (ODH), Release 1.3 (Standard for Trial Use)** This 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. **Introduction and Guidance** This 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. This 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. While 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. **Background** The 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. The 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. **Scope** The 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: • Employment Status • Retirement Date • Combat Zone Period • Past or Present Job for the patient or a household member, which includes: o Past or Present Job Occupation o Past or Present Job Industry o Work Classification o Work Schedule, which includes: - Weekly Work Days - Daily Work Hours o Job Duty o Occupational Hazard o Employer name o Employer address o Related Subject (when it is Past or Present Job of a household member of the person) o Start/End Dates • Usual Work of the patient or a household member, which includes: o Usual Occupation o Usual Industry o Usual Occupation Duration o Related Subject (when it is Usual Work of a household member of the person) o Start Date **Known Issues and Limitations** This 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. While multiple retirement dates are supported, the retirement date is not linked to any specific job, or usual occupation. **Credits** Co-Editor: Lori Reed-Fourquet e-HealthSign, LLC lfourquet@ehealthsign.com Co-Editor: Rob Hausam Hausam Consulting rob@hausamconsulting.com Co-Editor: Mark Kramer MITRE Corporation mkramer@mitre.org This 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). The 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. **Authors** Name Email/URL HL7 International - Public Health http://www.hl7.org/Special/committees/pher (built Mon, Mar 27, 2023 09:54+1100+11:00) http://hl7.org/fhir/us/odh/STU1.3/package.r4.tgz http://hl7.org/fhir/us/odh/STU1.3/package.r4.tgz HL7, Inc 4.0.1 IG Mon, 27 Mar 2023 11:24:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.odh.r4b#1.3.0 **HL7 FHIR Profile: Occupational Data for Health (ODH), Release 1.3 (Standard for Trial Use)** This 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. **Introduction and Guidance** This 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. This 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. While 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. **Background** The 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. The 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. **Scope** The 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: • Employment Status • Retirement Date • Combat Zone Period • Past or Present Job for the patient or a household member, which includes: o Past or Present Job Occupation o Past or Present Job Industry o Work Classification o Work Schedule, which includes: - Weekly Work Days - Daily Work Hours o Job Duty o Occupational Hazard o Employer name o Employer address o Related Subject (when it is Past or Present Job of a household member of the person) o Start/End Dates • Usual Work of the patient or a household member, which includes: o Usual Occupation o Usual Industry o Usual Occupation Duration o Related Subject (when it is Usual Work of a household member of the person) o Start Date **Known Issues and Limitations** This 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. While multiple retirement dates are supported, the retirement date is not linked to any specific job, or usual occupation. **Credits** Co-Editor: Lori Reed-Fourquet e-HealthSign, LLC lfourquet@ehealthsign.com Co-Editor: Rob Hausam Hausam Consulting rob@hausamconsulting.com Co-Editor: Mark Kramer MITRE Corporation mkramer@mitre.org This 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). The 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. **Authors** Name Email/URL HL7 International - Public Health http://www.hl7.org/Special/committees/pher (built Mon, Mar 27, 2023 09:54+1100+11:00) http://hl7.org/fhir/us/odh/STU1.3/package.r4b.tgz http://hl7.org/fhir/us/odh/STU1.3/package.r4b.tgz HL7, Inc 4.3.0 IG Mon, 27 Mar 2023 11:24:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.ipa.r4#1.0.0 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 Sun, Mar 26, 2023 20:50+0000+00:00) http://hl7.org/fhir/uv/ipa/STU1/package.r4.tgz http://hl7.org/fhir/uv/ipa/STU1/package.r4.tgz HL7, Inc 4.0.1 IG Mon, 27 Mar 2023 08:04:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.ipa.r4b#1.0.0 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 Sun, Mar 26, 2023 20:50+0000+00:00) http://hl7.org/fhir/uv/ipa/STU1/package.r4b.tgz http://hl7.org/fhir/uv/ipa/STU1/package.r4b.tgz HL7, Inc 4.3.0 IG Mon, 27 Mar 2023 08:04:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.r5.corexml#5.0.0-draft-final FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (XML) (built Wed, Mar 1, 2023 23:03+1100+11:00) http://hl7.org/fhir/5.0.0-draft-final/hl7.fhir.r5.corexml.tgz http://hl7.org/fhir/5.0.0-draft-final/hl7.fhir.r5.corexml.tgz HL7, Inc 5.0.0-draft-final IG Thu, 02 Mar 2023 07:29:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.subscriptions-backport.r4#1.1.0 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 Wed, Jan 11, 2023 15:34+1100+11:00) http://hl7.org/fhir/uv/subscriptions-backport/STU1.1/package.r4.tgz http://hl7.org/fhir/uv/subscriptions-backport/STU1.1/package.r4.tgz HL7, Inc 4.0.0 IG Wed, 11 Jan 2023 16:52:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.subscriptions-backport.r4b#1.1.0 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 Wed, Jan 11, 2023 15:34+1100+11:00) http://hl7.org/fhir/uv/subscriptions-backport/STU1.1/package.r4b.tgz http://hl7.org/fhir/uv/subscriptions-backport/STU1.1/package.r4b.tgz HL7, Inc 4.3.0 IG Wed, 11 Jan 2023 16:52:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.r5.corexml#5.0.0-snapshot3 FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (XML) (built Wed, Dec 14, 2022 07:12+1100+11:00) http://hl7.org/fhir/5.0.0-snapshot3/hl7.fhir.r5.corexml.tgz http://hl7.org/fhir/5.0.0-snapshot3/hl7.fhir.r5.corexml.tgz HL7, Inc 5.0.0-snapshot3 IG Thu, 15 Dec 2022 22:48:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.pddi.r4#1.0.0-ballot Package hl7.fhir.uv.pddi.r4#1.0.0-ballot http://hl7.org/fhir/uv/pddi/2023Jan/package.r4.tgz http://hl7.org/fhir/uv/pddi/2023Jan/package.r4.tgz HL7, Inc 4.0.1 IG Thu, 08 Dec 2022 02:11:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.pddi.r4b#1.0.0-ballot Package hl7.fhir.uv.pddi.r4b#1.0.0-ballot http://hl7.org/fhir/uv/pddi/2023Jan/package.r4b.tgz http://hl7.org/fhir/uv/pddi/2023Jan/package.r4b.tgz HL7, Inc 4.3.0 IG Thu, 08 Dec 2022 02:11:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.carin-bb.r4#2.0.0 CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) (built Mon, Nov 28, 2022 15:15+0000+00:00) http://hl7.org/fhir/us/carin-bb/STU2/package.r4.tgz http://hl7.org/fhir/us/carin-bb/STU2/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 29 Nov 2022 02:58:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.carin-bb.r4b#2.0.0 CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) (built Mon, Nov 28, 2022 15:15+0000+00:00) http://hl7.org/fhir/us/carin-bb/STU2/package.r4b.tgz http://hl7.org/fhir/us/carin-bb/STU2/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 29 Nov 2022 02:58:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.ips.r4#1.1.0 International Patient Summary (IPS) FHIR Implementation Guide (built Tue, Nov 22, 2022 03:24+0000+00:00) http://hl7.org/fhir/uv/ips/STU1.1/package.r4.tgz http://hl7.org/fhir/uv/ips/STU1.1/package.r4.tgz HL7, Inc 4.0.1 IG Tue, 22 Nov 2022 14:58:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.ips.r4b#1.1.0 International Patient Summary (IPS) FHIR Implementation Guide (built Tue, Nov 22, 2022 03:24+0000+00:00) http://hl7.org/fhir/uv/ips/STU1.1/package.r4b.tgz http://hl7.org/fhir/uv/ips/STU1.1/package.r4b.tgz HL7, Inc 4.3.0 IG Tue, 22 Nov 2022 14:58:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.vitalsigns#0.1.0 Package hl7.fhir.us.vitalsigns#0.1.0 http://hl7.org/fhir/us/vitals/2020Sep/package.tgz http://hl7.org/fhir/us/vitals/2020Sep/package.tgz HL7, Inc 4.0.1 IG Thu, 20 Oct 2022 12:03:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.uv.sdc#1.6 Package hl7.fhir.uv.sdc#1.6 http://hl7.org/fhir/us/sdc/2016Sep/package.tgz http://hl7.org/fhir/us/sdc/2016Sep/package.tgz HL7, Inc 1.6.0 IG Thu, 20 Oct 2022 12:00:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.sdc#2.0 The SDC specification provides an infrastructure to standardize the capture and expanded use of patient-level data collected within an EHR.<br/>This includes two components:<br/>* Support more sophisticated questionnaire/form use-cases such as those needed for research, oncology, pathology and other clinical domains.<br/>*Support pre-population and auto-population of EHR data into forms/questionnaires for uses outside direct clinical care (patient safety, adverse event reporting, public health reporting, etc.). http://hl7.org/fhir/us/sdc/package.tgz http://hl7.org/fhir/us/sdc/package.tgz HL7, Inc 3.0.1 IG Thu, 20 Oct 2022 12:00:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.sdcde#1.6 Package hl7.fhir.us.sdcde#1.6 http://hl7.org/fhir/us/sdcde/2016Sep/package.tgz http://hl7.org/fhir/us/sdcde/2016Sep/package.tgz HL7, Inc 1.6.0 IG Thu, 20 Oct 2022 12:00:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.sdcde#2.0 This implementation guide is a supplement to the base Structured Data Capture (SDC) implementation guide. It defines expectations for Data Element registries, as well as those systems that are responsible for the creation and maintenance of data elements within those registries. This capability is documented as a distinct implementation guide because the expectations for systems creating and maintaining data elements are higher than for those systems that are merely responsible for referencing data elements when creating forms or configuring their systems to support pre-population or auto-population. http://hl7.org/fhir/us/sdcde/package.tgz http://hl7.org/fhir/us/sdcde/package.tgz HL7, Inc 3.0.1 IG Thu, 20 Oct 2022 12:00:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.meds#2.1.0 Package hl7.fhir.us.meds#2.1.0 http://hl7.org/fhir/us/meds/2020Sep/package.tgz http://hl7.org/fhir/us/meds/2020Sep/package.tgz HL7, Inc 4.0.1 IG Thu, 20 Oct 2022 11:49:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.davinci-alerts#0.1.0 Package hl7.fhir.us.davinci-alerts#0.1.0 http://hl7.org/fhir/us/davinci-alerts/2019Sep/package.tgz http://hl7.org/fhir/us/davinci-alerts/2019Sep/package.tgz HL7, Inc 4.0.0 IG Thu, 20 Oct 2022 11:21:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.us.dafresearch#1.0.0 Package hl7.fhir.us.dafresearch#1.0.0 http://hl7.org/fhir/us/daf-research/package.tgz http://hl7.org/fhir/us/daf-research/package.tgz HL7, Inc 3.0.1 IG Thu, 20 Oct 2022 11:20:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.r5.core#5.0.0-snapshot2 FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (built Sun, Dec 19, 2021 08:15+1100+11:00) http://hl7.org/fhir/5.0.0-snapshot2/hl7.fhir.r5.core.tgz http://hl7.org/fhir/5.0.0-snapshot2/hl7.fhir.r5.core.tgz HL7, Inc 5.0.0-snapshot2 IG Thu, 20 Oct 2022 10:20:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.r5.examples#5.0.0-snapshot2 Example resources in the R5 version of the FHIR standard http://hl7.org/fhir/5.0.0-snapshot2/hl7.fhir.r5.examples.tgz http://hl7.org/fhir/5.0.0-snapshot2/hl7.fhir.r5.examples.tgz HL7, Inc 5.0.0-snapshot2 IG Thu, 20 Oct 2022 10:20:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.r5.corexml#5.0.0-snapshot1 FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (XML) (built Sun, Dec 19, 2021 08:15+1100+11:00) http://hl7.org/fhir/5.0.0-snapshot1/hl7.fhir.r5.corexml.tgz http://hl7.org/fhir/5.0.0-snapshot1/hl7.fhir.r5.corexml.tgz HL7, Inc 3.0.1 IG Thu, 20 Oct 2022 10:19:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.r5.corexml#5.0.0-ballot FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (XML) (built Wed, Sep 7, 2022 10:58+1000+10:00) http://hl7.org/fhir/5.0.0-ballot/hl7.fhir.r5.corexml.tgz http://hl7.org/fhir/5.0.0-ballot/hl7.fhir.r5.corexml.tgz HL7, Inc 5.0.0-ballot IG Thu, 20 Oct 2022 10:14:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.r4b.expansions#4.3.0-snapshot1 Expansions for the 4.3.0-snapshot1 version of the FHIR standard (built Fri, Dec 17, 2021 22:54+1100+11:00) http://hl7.org/fhir/4.3.0-snapshot1/hl7.fhir.r4b.expansions.tgz http://hl7.org/fhir/4.3.0-snapshot1/hl7.fhir.r4b.expansions.tgz HL7, Inc 4.3.0-snapshot1 IG Thu, 20 Oct 2022 10:11:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.r4b.examples#4.3.0-snapshot1 FHIR Examples package - the NPM package that contains all the examples in the base FHIR specification (built Tue, Dec 21, 2021 15:26+1100+11:00) http://hl7.org/fhir/4.3.0-snapshot1/hl7.fhir.r4b.examples.tgz http://hl7.org/fhir/4.3.0-snapshot1/hl7.fhir.r4b.examples.tgz HL7, Inc 4.3.0-snapshot1 IG Thu, 20 Oct 2022 10:11:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.r4b.core#4.3.0-snapshot1 FHIR Core package - the NPM package that contains all the conformance resources in the base FHIR specification (built Tue, Dec 21, 2021 15:26+1100+11:00) http://hl7.org/fhir/4.3.0-snapshot1/hl7.fhir.r4b.core.tgz http://hl7.org/fhir/4.3.0-snapshot1/hl7.fhir.r4b.core.tgz HL7, Inc 4.3.0-snapshot1 IG Thu, 20 Oct 2022 10:11:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.r5.corexml#4.6.0 FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (XML) (built Thu, Apr 15, 2021 12:25+1000+10:00) http://hl7.org/fhir/2021May/hl7.fhir.r5.corexml.tgz http://hl7.org/fhir/2021May/hl7.fhir.r5.corexml.tgz HL7, Inc 4.6.0 IG Thu, 20 Oct 2022 10:04:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.r4b.corexml#4.1.0 FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (XML) (built Thu, Mar 11, 2021 17:06+1100+11:00) http://hl7.org/fhir/2021Mar/hl7.fhir.r4b.corexml.tgz http://hl7.org/fhir/2021Mar/hl7.fhir.r4b.corexml.tgz HL7, Inc 4.1.0 IG Thu, 20 Oct 2022 10:01:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.r5.corexml#4.5.0 FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (XML) (built Thu, Aug 20, 2020 17:41+1000+10:00) http://hl7.org/fhir/2020Sep/hl7.fhir.r5.corexml.tgz http://hl7.org/fhir/2020Sep/hl7.fhir.r5.corexml.tgz HL7, Inc 4.5.0 IG Thu, 20 Oct 2022 09:57:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.r5.corexml#4.4.0 FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (XML) (built Tue, May 12, 2020 23:09+1000+10:00) http://hl7.org/fhir/2020May/hl7.fhir.r5.corexml.tgz http://hl7.org/fhir/2020May/hl7.fhir.r5.corexml.tgz HL7, Inc 4.4.0 IG Thu, 20 Oct 2022 09:50:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.r5.examples#4.2.0 FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (built Tue, Dec 31, 2019 21:03+1100+11:00) http://hl7.org/fhir/2020Feb/hl7.fhir.r5.examples.tgz http://hl7.org/fhir/2020Feb/hl7.fhir.r5.examples.tgz HL7, Inc 4.2.0 IG Thu, 20 Oct 2022 09:42:00 +1100 Added from file system scan on 28/10/2025 hl7.fhir.r5.corexml#4.2.0 FHIR Core package - the NPM package that contains all the definitions for the base FHIR specification (XML) (built Tue, Dec 31, 2019 21:03+1100+11:00) http://hl7.org/fhir/2020Feb/hl7.fhir.r5.corexml.tgz http://hl7.org/fhir/2020Feb/hl7.fhir.r5.corexml.tgz HL7, Inc 4.2.0 IG Thu, 20 Oct 2022 09:42:00 +1100 Added from file system scan on 28/10/2025