Reminder: Do not include any PHI or PII in Confluence. If you require 508 accessibility assistance or any other support for this system, then please send an email to onc-jira-questions@healthit.gov
We will be performing scheduled maintenance on Saturday July 6th, from 8am to 1pm. During this time, users can expect interruptions in services. We thank you for your patience.
FHIR at Scale Taskforce
Testing and Certification Tiger Team Charter
July 19, 2018
Opportunity Statement (Problem)Problem: There are ecosystem and infrastructure barriers that prevent the wide-scale adoption and deployment of FHIR for payers and providers.
...
A prerequisite to using FHIR at Scale is the ability to demonstrate basic FHIR Conformance. Systems can only claim FHIR Conformance for functionality described in the applicable CapabilityStatement. To provide details about specific usage of the frameworks and resource contents, FHIR provides a conformance layer that implementers, national/regional programs, and other profiling organizations such as IHE, can use to provide a computable statement about how the resources and their exchange paradigms are used to solve particular use cases. The conformance layer itself is implemented using the following key resources:
Defines a set of coded values (see "Using Codes" for more details) | |
Makes rules about how a resource (or type) and its data elements are used in a particular context, including defining how extensions are used. A structure definition references value sets for the coded elements in a resource | |
A statement of the kinds of resources and operations provided and/or consumed by an application. The Capability Statement references profiles to describe specific use of resources by the application | |
A single coherent collection of capability statements, profiles, extensions, value sets, and documentation describing a set of interoperable applications |
FHIR at Scale:
In order to assure scalability, the FHIR at Scale Task Force (FAST) will develop requirements around core competencies in each of the following areas: ecosystem, identity, directory, security, and exchange process.
...
Project Deliverables
Describe the minimum level of conformance required to participate in a scaled FHIR ecosystem.
Scope conformance requirements
Are there other levels that we also may want to scope requirements for?
Need to work with other appropriate Tiger Teams to determine what constitutes a scaled FHIR ecosystem
Testing specifications that can be used by a certification organization or individual organization to assure compliance with the work of the FHIR Ecosystem Task Force.
...
Determine a common set of specifications to be used including privacy/security, interoperability, performance considerations etc.
...
Extending current FHIR work to proofs of concepts that test for scale and conformance testing across multiple stakeholders using multiple FHIR artifacts that are at various stages of maturity.
...
Identification of current beta/proofs of concept including understanding of business use case, objectives etc.
...
Project Plan with Timeline