×

To enhance security, Multi-Factor Authentication (MFA) is mandatory for all HL7 users. More information

 
Return to Search

Conformance, Guidance and Best Practices for FHIR Implementation Guides (PSS in Confluence)

Return to Search

Basics

Conformance, Guidance and Best Practices for FHIR Implementation Guides (PSS in Confluence)

1544
Ballot - Informative



Supplement to a Current Standard, Implementation Guide

Details

- This specification provides guidance related to conformance testing of FHIR-based APIs.

- Where appropriate, this specification clarifies how extensions and "must support" data elements should be used improve patient outcomes and safety. Test cases may also be produced by this project, if needed.

- This specification will provide testing guidance across US-Realm specifications (implementation guides -see "Project Dependencies) such that provider, payers, public health, and research organization can make effective use of FHIR APIs to meet national policy objectives (see "External Drivers").

- This project will leverage successful testing approaches developed by implementers using other APIs (e.g. SOAP, ebXML) and HL7 standards (e.g. HL7 V2, CDA). It includes best-practices for data quality, first principles for effective testing, and testing guidance.

- The purpose of this project is to enable effective use of FHIR conformance constructs to test both application/clients and FHR server that use FHIR resources and FHIR-related specifications (e.g. SMART, CDS Hooks, etc.). This project is intended to bridge the gap between implementation guides and test case development and assist early adopters of FHIR APIs in the US.

- Even though the guidance is intended to assist US early adopters in the short term, it will be applicable worldwide.


FHIR-based APIs are a new paradigm in health IT that will require expanded conformance and testing capabilities. Other industries have had a great of experience with APIs but healthcare is new to this approach.

Until now, vendors have been using self-attestation to claim conformance to FHIR and FHIR-related specifications. As FHR-related APIs become ubiquitous, the importance of consistency across implementations will be crucial. Rather than conforming with a specific FHIR implementation, systems will have to conform to a common set of data and service specifications. The future success of such an environment depends on using best-practices to test and validate implementation against national specifications and local enterprise needs.



nformative Ballot - Target: May 2020 Ballot Reconciliation - Target: June 2020 WGM Publication - Target: July 2020


https://confluence.hl7.org/display/CONF/Conformance+Testing+and+Validation+of+FHIR+Implementation+PSS https://github.com/HL7/conformance


US-realm IGs including: - US Core R4 IG - Coverage Requirements Discovery (CRD) - Documentation Templates and Rules ( DTR)

Healthcare Institutions (hospitals, long term care, home care, mental health),EHR, PHR; Health Care IT; HIS; Other (specify in Misc. Notes below)

Department of Veterans Affairs, MITRE/Inferno Project (?) Sequoia Project (?) AEGIS (?)

Notice of Proposed Rulemaking to Improve the Interoperability of Health Information https://www.healthit.gov/topic/laws-regulation-and-policy/notice-proposed-rulemaking-improve-interoperability-health



N/A


No

Other Vendors: Payers
Organization & Realm

Realm Specific - Enter "U.S." or name of HL7 Affiliate below

U.S.
People

Ioana Singureanu



Conformance Work Group

Architectural Review Work Group

Status & Dates

Active

Active Project (Resources assigned to pjt)

05/21/2019

01/01/2024

2024 Jan WGM/Ballot

09/01/2023

2023 Sept WGM/Ballot

Approvals



Received


Pending




System Info



View Ballot Items (with NIBs)




Return to Search