Select Page

Job Automate Update Specifications

specID: 2102
title: HL7 FHIR® IG: SMART Application Launch Framework, v1.0.0
description: SMART App Launch defines a foundational patterns based on OAuth 2.0 for client applications to authorize, authenticate, and integrate with FHIR-based data systems (e.g., Electronic Health Record system, Patient Portal, or Beneficiary Portal).
pkgid: hl7.fhir.uv.smart-app-launch
object(Specification)#5058 (8) { ["id"]=> int(2102) ["title"]=> string(57) "HL7 FHIR® IG: SMART Application Launch Framework, v1.0.0" ["description"]=> string(242) "SMART App Launch defines a foundational patterns based on OAuth 2.0 for client applications to authorize, authenticate, and integrate with FHIR-based data systems (e.g., Electronic Health Record system, Patient Portal, or Beneficiary Portal)." ["verson"]=> NULL ["pkgid"]=> string(28) "hl7.fhir.uv.smart-app-launch" ["pkgpath"]=> string(36) "http://hl7.org/fhir/smart-app-launch" ["currentversion"]=> NULL ["version"]=> string(5) "1.0.0" }


specID: 2100
title: HL7 FHIR® Implementation Guide: Prior-Authorization Support (PAS), Edition 2 – US Realm
description: The goal of Prior Authorization Support is to define FHIR based services to enable a provider's system, at point of service, to request authorization (including all necessary clinical information to support the request) and receive immediate authorization.
pkgid:
object(Specification)#5070 (8) { ["id"]=> int(2100) ["title"]=> string(98) "HL7 FHIR® Implementation Guide: Prior-Authorization Support (PAS), Edition 2 – US Realm" ["description"]=> string(256) "The goal of Prior Authorization Support is to define FHIR based services to enable a provider's system, at point of service, to request authorization (including all necessary clinical information to support the request) and receive immediate authorization." ["verson"]=> NULL ["pkgid"]=> NULL ["pkgpath"]=> NULL ["currentversion"]=> NULL ["version"]=> string(5) "2.0.1" }


specID: 2098
title: HL7 FHIR® Implementation Guide: Documentation Templates and Rules (DTR), Edition 2 – US Realm
description: The Documentation Templates and Rules (DTR) Implementation Guide (IG) specifies how payer rules can be executed in a provider context to ensure that documentation requirements are met.
pkgid:
object(Specification)#5189 (8) { ["id"]=> int(2098) ["title"]=> string(104) "HL7 FHIR® Implementation Guide: Documentation Templates and Rules (DTR), Edition 2 – US Realm" ["description"]=> string(184) "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." ["verson"]=> NULL ["pkgid"]=> NULL ["pkgpath"]=> NULL ["currentversion"]=> NULL ["version"]=> string(5) "2.0.1" }


specID: 2096
title: HL7 FHIR® Implementation Guide: Payer Data Exchange (PDex) Payer Network, Release 1.1 – US Realm
description: This implementation guide defines a FHIR interface to a health insurer’s insurance plans, their associated networks, and the organizations and providers that participate in these networks. Publication of this data through a standard FHIR-based API will enable third parties to develop applications through which consumers and providers can query the participants in a payer’s network that may provide services that address their health care needs. Although there are multiple types and sources of providers’ directories, including provider organizations (i.e., a hospital listing all its physicians), government (i.e., listing of providers in Medicare), payers (i.e., a health plan’s provider network), and third-party entities (such as vendors that maintain provider directories), the focus of this implementation guide is on Payer Provider Directories.
pkgid:
object(Specification)#5096 (8) { ["id"]=> int(2096) ["title"]=> string(107) "HL7 FHIR® Implementation Guide: Payer Data Exchange (PDex) Payer Network, Release 1.1 – US Realm" ["description"]=> string(862) "This implementation guide defines a FHIR interface to a health insurer’s insurance plans, their associated networks, and the organizations and providers that participate in these networks. Publication of this data through a standard FHIR-based API will enable third parties to develop applications through which consumers and providers can query the participants in a payer’s network that may provide services that address their health care needs. Although there are multiple types and sources of providers’ directories, including provider organizations (i.e., a hospital listing all its physicians), government (i.e., listing of providers in Medicare), payers (i.e., a health plan’s provider network), and third-party entities (such as vendors that maintain provider directories), the focus of this implementation guide is on Payer Provider Directories." ["verson"]=> NULL ["pkgid"]=> NULL ["pkgpath"]=> NULL ["currentversion"]=> NULL ["version"]=> string(5) "1.1.0" }


specID: 2094
title: HL7 FHIR® Implementation Guide: DaVinci Payer Data Exchange US Drug Formulary, Release 1 STU2 – US Realm
description: This project defines a FHIR interface to a health insurer's drug formulary information for patients/consumers. A drug formulary is a list of brand-name and generic prescription drugs a health insurer agrees to pay for, at least partially, as part of health insurance coverage. Drug formularies are developed based on the efficacy, safety and cost of drugs. The primary use cases for this FHIR interface enable consumers/members/patients to understand the costs and alternatives for drugs that have been prescribed, and to compare their drug costs across different insurance plans.
pkgid:
object(Specification)#5186 (8) { ["id"]=> int(2094) ["title"]=> string(115) "HL7 FHIR® Implementation Guide: DaVinci Payer Data Exchange US Drug Formulary, Release 1 STU2 – US Realm" ["description"]=> string(580) "This project defines a FHIR interface to a health insurer's drug formulary information for patients/consumers. A drug formulary is a list of brand-name and generic prescription drugs a health insurer agrees to pay for, at least partially, as part of health insurance coverage. Drug formularies are developed based on the efficacy, safety and cost of drugs. The primary use cases for this FHIR interface enable consumers/members/patients to understand the costs and alternatives for drugs that have been prescribed, and to compare their drug costs across different insurance plans." ["verson"]=> NULL ["pkgid"]=> NULL ["pkgpath"]=> NULL ["currentversion"]=> NULL ["version"]=> string(5) "2.0.1" }


specID: 2092
title: HL7 FHIR® Implementation Guide: Payer Data Exchange (PDex), Release 2 – US Realm
description: Using Payer Data Exchange enables payers to publish Financial and clinical data to Consumers and other payers using US Core clinical resources and additional profiles that are specific to the payer community and not available in US Core.
pkgid:
object(Specification)#5095 (8) { ["id"]=> int(2092) ["title"]=> string(91) "HL7 FHIR® Implementation Guide: Payer Data Exchange (PDex), Release 2 – US Realm" ["description"]=> string(237) "Using Payer Data Exchange enables payers to publish Financial and clinical data to Consumers and other payers using US Core clinical resources and additional profiles that are specific to the payer community and not available in US Core." ["verson"]=> NULL ["pkgid"]=> NULL ["pkgpath"]=> NULL ["currentversion"]=> NULL ["version"]=> string(5) "2.0.0" }


specID: 2089
title: HL7 FHIR® Implementation Guide: Bulk Data Access IG 1.0.0
description: Bulk Data is a FHIR based approach for exporting large data sets from a FHIR server to a client application
pkgid:
object(Specification)#5062 (8) { ["id"]=> int(2089) ["title"]=> string(58) "HL7 FHIR® Implementation Guide: Bulk Data Access IG 1.0.0" ["description"]=> string(107) "Bulk Data is a FHIR based approach for exporting large data sets from a FHIR server to a client application" ["verson"]=> NULL ["pkgid"]=> NULL ["pkgpath"]=> NULL ["currentversion"]=> NULL ["version"]=> string(5) "1.0.0" }


specID: 2083
title: HL7 CDA® R2 Implementation Guide: Reportability Response, Release 1, STU Release 1.1
description: The purpose of this implementation guide (IG) is to specify a standard for a response document for a public health electronic Initial Case Report (HL7 eICR v1.1) using HL7 Version 3 Clinical Document Architecture (CDA), Release 2 format. Through the Reportability Response, public health seeks to support bidirectional communication with clinical care for reportable conditions in CDA format—an interoperable, industry-standard format.
pkgid:
object(Specification)#5083 (8) { ["id"]=> int(2083) ["title"]=> string(85) "HL7 CDA® R2 Implementation Guide: Reportability Response, Release 1, STU Release 1.1" ["description"]=> string(437) "The purpose of this implementation guide (IG) is to specify a standard for a response document for a public health electronic Initial Case Report (HL7 eICR v1.1) using HL7 Version 3 Clinical Document Architecture (CDA), Release 2 format. Through the Reportability Response, public health seeks to support bidirectional communication with clinical care for reportable conditions in CDA format—an interoperable, industry-standard format." ["verson"]=> NULL ["pkgid"]=> NULL ["pkgpath"]=> NULL ["currentversion"]=> NULL ["version"]=> string(3) "1.1" }


specID: 2081
title: HL7 CDA® R2 Implementation Guide: Public Health Case Report – the Electronic Initial Case Report (eICR) Release 2, STU Release 3.1
description: The purpose of this implementation guide (IG) is to specify a standard for electronic submission of electronic initial public health case reports using HL7 Version 3 Clinical Document Architecture (CDA), Release 2 format. This implementation guide will allow healthcare providers to electronically communicate the specific data needed in initial public health case reports (required by state laws/regulations) to jurisdictional public health agencies in CDA format—an interoperable, industry-standard format.
pkgid:
object(Specification)#5101 (8) { ["id"]=> int(2081) ["title"]=> string(141) "HL7 CDA® R2 Implementation Guide: Public Health Case Report – the Electronic Initial Case Report (eICR) Release 2, STU Release 3.1" ["description"]=> string(510) "The purpose of this implementation guide (IG) is to specify a standard for electronic submission of electronic initial public health case reports using HL7 Version 3 Clinical Document Architecture (CDA), Release 2 format. This implementation guide will allow healthcare providers to electronically communicate the specific data needed in initial public health case reports (required by state laws/regulations) to jurisdictional public health agencies in CDA format—an interoperable, industry-standard format." ["verson"]=> NULL ["pkgid"]=> NULL ["pkgpath"]=> NULL ["currentversion"]=> NULL ["version"]=> string(3) "3.1" }


specID: 1865
title: HL7 CDA® R2 IG: C-CDA Templates for Clinical Notes STU Companion Guide Release 4.1
description: The Office of the National Coordinator (ONC) releases periodic proposed rules, and final rules, which reference the use of Consolidated CDA (C-CDA). The Companion Guide to Consolidated Clinical Document Architecture (C-CDA) provides supplemental guidance.
pkgid:
Specification updated from Jira.
object(Specification)#5094 (8) { ["id"]=> int(1865) ["title"]=> string(83) "HL7 CDA® R2 IG: C-CDA Templates for Clinical Notes STU Companion Guide Release 4.1" ["description"]=> string(255) "The Office of the National Coordinator (ONC) releases periodic proposed rules, and final rules, which reference the use of Consolidated CDA (C-CDA). The Companion Guide to Consolidated Clinical Document Architecture (C-CDA) provides supplemental guidance." ["verson"]=> NULL ["pkgid"]=> NULL ["pkgpath"]=> NULL ["currentversion"]=> NULL ["version"]=> string(5) "4.1.0" }


specID: 1859
title: HL7 FHIR® Profile: Quality, Release 1, 6.0.0
description: The implementation guide (IG) defines a set of FHIR 4.0.1 profiles to create interoperable, quality-focused applications. The profiles derive from and extend the US Core profiles to provide a common foundation for building, sharing, and evaluating knowledge artifacts across quality improvement efforts in the US Realm
pkgid: hl7.fhir.us.qicore
object(Specification)#5104 (8) { ["id"]=> int(1859) ["title"]=> string(45) "HL7 FHIR® Profile: Quality, Release 1, 6.0.0" ["description"]=> string(318) "The implementation guide (IG) defines a set of FHIR 4.0.1 profiles to create interoperable, quality-focused applications. The profiles derive from and extend the US Core profiles to provide a common foundation for building, sharing, and evaluating knowledge artifacts across quality improvement efforts in the US Realm" ["verson"]=> NULL ["pkgid"]=> string(18) "hl7.fhir.us.qicore" ["pkgpath"]=> string(29) "http://hl7.org/fhir/us/qicore" ["currentversion"]=> NULL ["version"]=> string(12) "6.0.0-ballot" }


specID: 1856
title: HL7 FHIR® US Core Implementation Guide, v6.1.0 – STU6
description: The US Core Implementation Guide is based on FHIR Version R4 and defines the minimum set of constraints on the FHIR resources to create the US Core Profiles. It also defines the minimum set of FHIR RESTful interactions for each of the US Core Profiles to access patient data.
pkgid: hl7.fhir.us.core
Specification updated from Jira.
object(Specification)#5253 (8) { ["id"]=> int(1856) ["title"]=> string(64) "HL7 FHIR® US Core Implementation Guide, v6.1.0 – STU6" ["description"]=> string(277) "The US Core Implementation Guide is based on FHIR Version R4 and defines the minimum set of constraints on the FHIR resources to create the US Core Profiles. It also defines the minimum set of FHIR RESTful interactions for each of the US Core Profiles to access patient data." ["verson"]=> NULL ["pkgid"]=> string(16) "hl7.fhir.us.core" ["pkgpath"]=> string(27) "http://hl7.org/fhir/us/core" ["currentversion"]=> NULL ["version"]=> string(5) "6.1.0" }


specID: 1795
title: HL7 FHIR® IG: SMART Application Launch Framework, v2.1.0
description: SMART App Launch 2.1.0 defines a foundational patterns based on OAuth 2.0 for client applications to authorize, authenticate, and integrate with FHIR-based data systems (e.g., Electronic Health Record system, Patient Portal, or Beneficiary Portal).
pkgid: hl7.fhir.uv.smart-app-launch
object(Specification)#5140 (8) { ["id"]=> int(1795) ["title"]=> string(57) "HL7 FHIR® IG: SMART Application Launch Framework, v2.1.0" ["description"]=> string(248) "SMART App Launch 2.1.0 defines a foundational patterns based on OAuth 2.0 for client applications to authorize, authenticate, and integrate with FHIR-based data systems (e.g., Electronic Health Record system, Patient Portal, or Beneficiary Portal)." ["verson"]=> NULL ["pkgid"]=> string(28) "hl7.fhir.uv.smart-app-launch" ["pkgpath"]=> string(36) "http://hl7.org/fhir/smart-app-launch" ["currentversion"]=> NULL ["version"]=> string(5) "2.1.0" }


specID: 1791
title: HL7 FHIR® US Core Implementation Guide, v6.0.0 – STU6
description: The US Core Implementation Guide is based on FHIR Version R4 and defines the minimum set of constraints on the FHIR resources to create the US Core Profiles. It also defines the minimum set of FHIR RESTful interactions for each of the US Core Profiles to access patient data.
pkgid: hl7.fhir.us.core
Specification updated from Jira.
object(Specification)#5070 (8) { ["id"]=> int(1791) ["title"]=> string(64) "HL7 FHIR® US Core Implementation Guide, v6.0.0 – STU6" ["description"]=> string(277) "The US Core Implementation Guide is based on FHIR Version R4 and defines the minimum set of constraints on the FHIR resources to create the US Core Profiles. It also defines the minimum set of FHIR RESTful interactions for each of the US Core Profiles to access patient data." ["verson"]=> NULL ["pkgid"]=> string(16) "hl7.fhir.us.core" ["pkgpath"]=> string(27) "http://hl7.org/fhir/us/core" ["currentversion"]=> NULL ["version"]=> string(5) "6.0.0" }


specID: 1788
title: HL7 CDA® R2 IG: C-CDA Templates for Clinical Notes STU Companion Guide Release 4
description: The Office of the National Coordinator (ONC) releases periodic proposed rules, and final rules, which reference the use of Consolidated CDA (C-CDA). The Companion Guide to Consolidated Clinical Document Architecture (C-CDA) provides supplemental guidance.
pkgid:
object(Specification)#5061 (8) { ["id"]=> int(1788) ["title"]=> string(81) "HL7 CDA® R2 IG: C-CDA Templates for Clinical Notes STU Companion Guide Release 4" ["description"]=> string(255) "The Office of the National Coordinator (ONC) releases periodic proposed rules, and final rules, which reference the use of Consolidated CDA (C-CDA). The Companion Guide to Consolidated Clinical Document Architecture (C-CDA) provides supplemental guidance." ["verson"]=> NULL ["pkgid"]=> NULL ["pkgpath"]=> NULL ["currentversion"]=> NULL ["version"]=> string(5) "4.0.0" }


specID: 1476
title: HL7 FHIR® Implementation Guide: Bulk Data Access IG 2.0.0
description: Bulk Data is a FHIR based approach for exporting large data sets from a FHIR server to a client application
pkgid:
object(Specification)#5262 (8) { ["id"]=> int(1476) ["title"]=> string(58) "HL7 FHIR® Implementation Guide: Bulk Data Access IG 2.0.0" ["description"]=> string(107) "Bulk Data is a FHIR based approach for exporting large data sets from a FHIR server to a client application" ["verson"]=> NULL ["pkgid"]=> NULL ["pkgpath"]=> NULL ["currentversion"]=> NULL ["version"]=> string(5) "2.0.0" }


specID: 1431
title: HL7 FHIR® Profile: Quality, Release 1, 4.1.1
description: The implementation guide (IG) defines a set of FHIR 4.0.1 profiles to create interoperable, quality-focused applications. The profiles derive from and extend the US Core profiles to provide a common foundation for building, sharing, and evaluating knowledge artifacts across quality improvement efforts in the US Realm
pkgid: hl7.fhir.us.qicore
object(Specification)#5145 (8) { ["id"]=> int(1431) ["title"]=> string(45) "HL7 FHIR® Profile: Quality, Release 1, 4.1.1" ["description"]=> string(318) "The implementation guide (IG) defines a set of FHIR 4.0.1 profiles to create interoperable, quality-focused applications. The profiles derive from and extend the US Core profiles to provide a common foundation for building, sharing, and evaluating knowledge artifacts across quality improvement efforts in the US Realm" ["verson"]=> NULL ["pkgid"]=> string(18) "hl7.fhir.us.qicore" ["pkgpath"]=> string(29) "http://hl7.org/fhir/us/qicore" ["currentversion"]=> NULL ["version"]=> string(5) "4.1.1" }


specID: 1415
title: HL7 FHIR® Profile: Quality, Release 1, 5.0.0
description: The implementation guide (IG) defines a set of FHIR 4.0.1 profiles to create interoperable, quality-focused applications. The profiles derive from and extend the US Core profiles to provide a common foundation for building, sharing, and evaluating knowledge artifacts across quality improvement efforts in the US Realm
pkgid: hl7.fhir.us.qicore
object(Specification)#5073 (8) { ["id"]=> int(1415) ["title"]=> string(45) "HL7 FHIR® Profile: Quality, Release 1, 5.0.0" ["description"]=> string(318) "The implementation guide (IG) defines a set of FHIR 4.0.1 profiles to create interoperable, quality-focused applications. The profiles derive from and extend the US Core profiles to provide a common foundation for building, sharing, and evaluating knowledge artifacts across quality improvement efforts in the US Realm" ["verson"]=> NULL ["pkgid"]=> string(18) "hl7.fhir.us.qicore" ["pkgpath"]=> string(29) "http://hl7.org/fhir/us/qicore" ["currentversion"]=> NULL ["version"]=> string(5) "5.0.0" }


specID: 1428
title: HL7 FHIR® US Core Implementation Guide, v4.0.0 – STU4
description: The US Core Implementation Guide is based on FHIR Version R4 and defines the minimum set of constraints on the FHIR resources to create the US Core Profiles. It also defines the minimum set of FHIR RESTful interactions for each of the US Core Profiles to access patient data.
pkgid: hl7.fhir.us.core
Specification updated from Jira.
object(Specification)#5164 (8) { ["id"]=> int(1428) ["title"]=> string(64) "HL7 FHIR® US Core Implementation Guide, v4.0.0 – STU4" ["description"]=> string(277) "The US Core Implementation Guide is based on FHIR Version R4 and defines the minimum set of constraints on the FHIR resources to create the US Core Profiles. It also defines the minimum set of FHIR RESTful interactions for each of the US Core Profiles to access patient data." ["verson"]=> NULL ["pkgid"]=> string(16) "hl7.fhir.us.core" ["pkgpath"]=> string(27) "http://hl7.org/fhir/us/core" ["currentversion"]=> NULL ["version"]=> string(5) "4.0.0" }


specID: 1424
title: HL7 CDA® R2 Implementation Guide: Quality Reporting Document Architecture I (QRDA I) Release 1, STU Release 5.2
description: This implementation guide (IG) describes constraints on the Clinical Document Architecture Release 2 (CDA R2) header and body elements for patient level quality reporting.
pkgid:
object(Specification)#5229 (8) { ["id"]=> int(1424) ["title"]=> string(112) "HL7 CDA® R2 Implementation Guide: Quality Reporting Document Architecture I (QRDA I) Release 1, STU Release 5.2" ["description"]=> string(171) "This implementation guide (IG) describes constraints on the Clinical Document Architecture Release 2 (CDA R2) header and body elements for patient level quality reporting." ["verson"]=> NULL ["pkgid"]=> NULL ["pkgpath"]=> NULL ["currentversion"]=> NULL ["version"]=> string(3) "5.2" }


specID: 1421
title: HL7 CDA® R2 Implementation Guide: Quality Reporting Document Architecture (QRDA III), Release 1, STU Release 2.1
description: This implementation guide (IG) describes constraints on the Clinical Document Architecture Release 2 (CDA R2) header and body elements for aggregate quality reporting.
pkgid:
object(Specification)#5202 (8) { ["id"]=> int(1421) ["title"]=> string(113) "HL7 CDA® R2 Implementation Guide: Quality Reporting Document Architecture (QRDA III), Release 1, STU Release 2.1" ["description"]=> string(167) "This implementation guide (IG) describes constraints on the Clinical Document Architecture Release 2 (CDA R2) header and body elements for aggregate quality reporting." ["verson"]=> NULL ["pkgid"]=> NULL ["pkgpath"]=> NULL ["currentversion"]=> NULL ["version"]=> string(3) "2.1" }


specID: 1411
title: HL7 CDA® R2 Implementation Guide: Quality Reporting Document Architecture (QRDA III), Category III, Release 1
description: This implementation guide (IG) describes constraints on the Clinical Document Architecture Release 2 (CDA R2) header and body elements for aggregate quality reporting.
pkgid:
object(Specification)#5156 (8) { ["id"]=> int(1411) ["title"]=> string(110) "HL7 CDA® R2 Implementation Guide: Quality Reporting Document Architecture (QRDA III), Category III, Release 1" ["description"]=> string(167) "This implementation guide (IG) describes constraints on the Clinical Document Architecture Release 2 (CDA R2) header and body elements for aggregate quality reporting." ["verson"]=> NULL ["pkgid"]=> NULL ["pkgpath"]=> NULL ["currentversion"]=> NULL ["version"]=> string(2) "R1" }


specID: 1413
title: HL7 CDA® R2 Implementation Guide: Quality Reporting Document Architecture I (QRDA I) Release 1, STU Release 5.3
description: This implementation guide (IG) describes constraints on the Clinical Document Architecture Release 2 (CDA R2) header and body elements for patient level quality reporting.
pkgid:
object(Specification)#5164 (8) { ["id"]=> int(1413) ["title"]=> string(112) "HL7 CDA® R2 Implementation Guide: Quality Reporting Document Architecture I (QRDA I) Release 1, STU Release 5.3" ["description"]=> string(171) "This implementation guide (IG) describes constraints on the Clinical Document Architecture Release 2 (CDA R2) header and body elements for patient level quality reporting." ["verson"]=> NULL ["pkgid"]=> NULL ["pkgpath"]=> NULL ["currentversion"]=> NULL ["version"]=> string(3) "5.3" }


specID: 1398
title: HL7 CDA® R2 Implementation Guide: Healthcare Associated Infection (HAI) Reports, Release 3
description: This project developed an implementation guide constraining CDA Release 2. The implementation guide supports electronic submission of HAI data to the National Healthcare Safety Network. CDC provided NHSN developers, vocabulary experts and CDA experts to support this project.
pkgid:
object(Specification)#5159 (8) { ["id"]=> int(1398) ["title"]=> string(91) "HL7 CDA® R2 Implementation Guide: Healthcare Associated Infection (HAI) Reports, Release 3" ["description"]=> string(275) "This project developed an implementation guide constraining CDA Release 2. The implementation guide supports electronic submission of HAI data to the National Healthcare Safety Network. CDC provided NHSN developers, vocabulary experts and CDA experts to support this project." ["verson"]=> NULL ["pkgid"]=> NULL ["pkgpath"]=> NULL ["currentversion"]=> NULL ["version"]=> string(1) "3" }


specID: 1259
title: HL7 CDA® R2 Implementation Guide: Consolidated CDA Templates for Clinical Notes, Release 2.1
description: The C-CDA R2.1 Implementation Guide (IG) provides an overview of the Clinical Document Architecture (CDA) base standard and provides information on how to understand and use CDA templates CDA templates for representing common clinical document types are defined in the IG at the document, section, entry level, and other supporting templates.
pkgid:
object(Specification)#5058 (8) { ["id"]=> int(1259) ["title"]=> string(93) "HL7 CDA® R2 Implementation Guide: Consolidated CDA Templates for Clinical Notes, Release 2.1" ["description"]=> string(343) "The C-CDA R2.1 Implementation Guide (IG) provides an overview of the Clinical Document Architecture (CDA) base standard and provides information on how to understand and use CDA templates CDA templates for representing common clinical document types are defined in the IG at the document, section, entry level, and other supporting templates. " ["verson"]=> NULL ["pkgid"]=> NULL ["pkgpath"]=> NULL ["currentversion"]=> NULL ["version"]=> string(3) "2.1" }


specID: 1167
title: HL7 FHIR® Implementation Guide: At-Home Point of Care Test Report
description: This draft guide constrains the US Core Diagnostic Report for Laboratory Results and the US Core Laboratory Observation Profile for use for transmitting home-covid test results to local, state, territorial and federal health agencies. It is an experimental basic guide to be used in real world testing.
pkgid: hl7.fhir.us.home-lab-report
object(Specification)#5148 (8) { ["id"]=> int(1167) ["title"]=> string(66) "HL7 FHIR® Implementation Guide: At-Home Point of Care Test Report" ["description"]=> string(302) "This draft guide constrains the US Core Diagnostic Report for Laboratory Results and the US Core Laboratory Observation Profile for use for transmitting home-covid test results to local, state, territorial and federal health agencies. It is an experimental basic guide to be used in real world testing." ["verson"]=> NULL ["pkgid"]=> string(27) "hl7.fhir.us.home-lab-report" ["pkgpath"]=> string(38) "http://hl7.org/fhir/us/home-lab-report" ["currentversion"]=> NULL ["version"]=> string(12) "1.0.0-ballot" }


specID: 1065
title: HL7 FHIR® US Core Implementation Guide, v3.1.1 – STU3
description: The US Core Implementation Guide is based on FHIR Version R4 and defines the minimum set of constraints on the FHIR resources to create the US Core Profiles. It also defines the minimum set of FHIR RESTful interactions for each of the US Core Profiles to access patient data.
pkgid: hl7.fhir.us.core
Specification updated from Jira.
object(Specification)#5142 (8) { ["id"]=> int(1065) ["title"]=> string(64) "HL7 FHIR® US Core Implementation Guide, v3.1.1 – STU3" ["description"]=> string(277) "The US Core Implementation Guide is based on FHIR Version R4 and defines the minimum set of constraints on the FHIR resources to create the US Core Profiles. It also defines the minimum set of FHIR RESTful interactions for each of the US Core Profiles to access patient data." ["verson"]=> NULL ["pkgid"]=> string(16) "hl7.fhir.us.core" ["pkgpath"]=> string(27) "http://hl7.org/fhir/us/core" ["currentversion"]=> NULL ["version"]=> string(5) "3.1.1" }


specID: 430
title: HL7 FHIR® Implementation Guide: Coverage Requirements Discovery, Release 2.0.1
description: This specification provides a mechanism for healthcare providers to discover guidelines, pre-authorization requirements and other expectations from payor organizations related to a proposed medication, procedure or other service associated with a patient's insurance coverage. It supports both patient-specific and patient-independent information retrieval.
pkgid: hl7.fhir.us.davinci-crd
object(Specification)#5171 (8) { ["id"]=> int(430) ["title"]=> string(79) "HL7 FHIR® Implementation Guide: Coverage Requirements Discovery, Release 2.0.1" ["description"]=> string(357) "This specification provides a mechanism for healthcare providers to discover guidelines, pre-authorization requirements and other expectations from payor organizations related to a proposed medication, procedure or other service associated with a patient's insurance coverage. It supports both patient-specific and patient-independent information retrieval." ["verson"]=> NULL ["pkgid"]=> string(23) "hl7.fhir.us.davinci-crd" ["pkgpath"]=> string(34) "http://hl7.org/fhir/us/davinci-crd" ["currentversion"]=> NULL ["version"]=> string(5) "2.0.1" }


specID: 427
title: HL7 FHIR® IG: SMART Application Launch Framework, v2.0.0
description: SMART App Launch 2.0.0 defines a foundational patterns based on OAuth 2.0 for client applications to authorize, authenticate, and integrate with FHIR-based data systems (e.g., Electronic Health Record system, Patient Portal, or Beneficiary Portal).
pkgid: hl7.fhir.uv.smart-app-launch
object(Specification)#5271 (8) { ["id"]=> int(427) ["title"]=> string(57) "HL7 FHIR® IG: SMART Application Launch Framework, v2.0.0" ["description"]=> string(248) "SMART App Launch 2.0.0 defines a foundational patterns based on OAuth 2.0 for client applications to authorize, authenticate, and integrate with FHIR-based data systems (e.g., Electronic Health Record system, Patient Portal, or Beneficiary Portal)." ["verson"]=> NULL ["pkgid"]=> string(28) "hl7.fhir.uv.smart-app-launch" ["pkgpath"]=> string(36) "http://hl7.org/fhir/smart-app-launch" ["currentversion"]=> NULL ["version"]=> string(5) "2.0.0" }


specID: 425
title: HL7 CDA® R2 IG: C-CDA Templates for Clinical Notes STU Companion Guide Release 3
description: The Office of the National Coordinator (ONC) releases periodic proposed rules, and final rules, which reference the use of Consolidated CDA (C-CDA). The Companion Guide to Consolidated Clinical Document Architecture (C-CDA) provides supplemental guidance.
pkgid:
object(Specification)#5139 (8) { ["id"]=> int(425) ["title"]=> string(81) "HL7 CDA® R2 IG: C-CDA Templates for Clinical Notes STU Companion Guide Release 3" ["description"]=> string(255) "The Office of the National Coordinator (ONC) releases periodic proposed rules, and final rules, which reference the use of Consolidated CDA (C-CDA). The Companion Guide to Consolidated Clinical Document Architecture (C-CDA) provides supplemental guidance." ["verson"]=> NULL ["pkgid"]=> NULL ["pkgpath"]=> NULL ["currentversion"]=> NULL ["version"]=> string(5) "3.0.0" }


specID: 422
title: HL7 FHIR® Implementation Guide: SMART Health Cards Vaccination and Testing, STU 1 Ballot
description: As part of the response to COVID-19, a coalition of health and technology leaders has created the Vaccination Credential Initiative (VCI). VCI is committed to empowering individuals access to a trustworthy and verifiable copy of their vaccination records in digital or paper form using open, interoperable standards
pkgid: hl7.fhir.uv.shc-vaccination
object(Specification)#5270 (8) { ["id"]=> int(422) ["title"]=> string(89) "HL7 FHIR® Implementation Guide: SMART Health Cards Vaccination and Testing, STU 1 Ballot" ["description"]=> string(315) "As part of the response to COVID-19, a coalition of health and technology leaders has created the Vaccination Credential Initiative (VCI). VCI is committed to empowering individuals access to a trustworthy and verifiable copy of their vaccination records in digital or paper form using open, interoperable standards" ["verson"]=> NULL ["pkgid"]=> string(27) "hl7.fhir.uv.shc-vaccination" ["pkgpath"]=> string(38) "http://hl7.org/fhir/uv/shc-vaccination" ["currentversion"]=> NULL ["version"]=> string(5) "0.6.2" }


specID: 72
title: HL7 FHIR® US Core Implementation Guide, v5.0.1 – STU5
description: The US Core Implementation Guide is based on FHIR Version R4 and defines the minimum set of constraints on the FHIR resources to create the US Core Profiles. It also defines the minimum set of FHIR RESTful interactions for each of the US Core Profiles to access patient data.
pkgid: hl7.fhir.us.core
Specification updated from Jira.
object(Specification)#5159 (8) { ["id"]=> int(72) ["title"]=> string(64) "HL7 FHIR® US Core Implementation Guide, v5.0.1 – STU5" ["description"]=> string(277) "The US Core Implementation Guide is based on FHIR Version R4 and defines the minimum set of constraints on the FHIR resources to create the US Core Profiles. It also defines the minimum set of FHIR RESTful interactions for each of the US Core Profiles to access patient data." ["verson"]=> NULL ["pkgid"]=> string(16) "hl7.fhir.us.core" ["pkgpath"]=> string(27) "http://hl7.org/fhir/us/core" ["currentversion"]=> NULL ["version"]=> string(5) "5.0.1" }