You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

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.

Purpose: Through a collaborative effort, the taskforce aims to address ecosystem barriers and accelerate adoption of FIHR for production exchange of clinical information between providers and payers.  

Scope Statement:  The Testing and Certification Tiger Team will focus on process and specifications for testing and certification of the requirements defined to meet the core competencies of identity, security, Endpoint discovery, scaling and exchange process.


Assumptions:

Certificates Required?

Federation Agreement?

The P2FHIR Testing and Certification Tiger Team will collaborate with the other P2FHIR tiger teams in order to ensure a practical approach for their use cases.


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.

  • How to include scale of review into specifications

  • Frequency of re-certification of API if applicable i.e., annually, every 2 years 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.

  • Which use cases include testing for scale and conformance and to what degree?


Work will be completed by two workgroups:

Use Case Review

Requirements & Scenario Development



Project Plan with Timeline

  • No labels