This wiki has undergone a migration to Confluence found Here

Difference between revisions of "FHIR Maturity Model"

From HL7Wiki
Jump to navigation Jump to search
Line 11: Line 11:
  
 
Tested across scope means:
 
Tested across scope means:
- The FMG has signed off on the list of "example contexts" defined for the artifact
+
:- The FMG has signed off on the list of "example contexts" defined for the artifact
- For each example context, the artifact has either been: reviewed and approved by a domain expert for that scope area, mapped to an existing implemented scope-area-specific standard or tested in an implementation
+
:- For each example context, the artifact has either been: reviewed and approved by a domain expert for that scope area, mapped to an existing implemented scope-area-specific standard or tested in an implementation

Revision as of 21:19, 5 August 2015

This page describes the 5 level FHIR maturity model for resources. It's based on the CMM (Capability Maturity Model) framework, and the intention is to give implementers a sense of how mature a resource is based on the level and types of review it has been subject to. These criteria may evolve over time.

  • FMM0 = the resource or profile (artifact) has been published on the current build
  • FMM1 = FMM0 + the artifact produces no warnings during the build process and the responsible WG has indicated that they consider the artifact substantially complete and ready for implementation
  • FMM2 = FMM1 + the artifact has been tested and successfully exchanged between at least three independently developed systems at a connectathon whose results have been reported to the FMG
  • FMM3 = FMM2 + the artifact has been verified by the work group as meeting the DSTU Quality Guidelines and has been subject to a round of formal balloting with at least 10 implementer comments drawn from at least 3 organizations resulting in at least one substantive change
  • FMM4 = FMM3 + the artifact has been tested across its scope (see below), published in a formal publication (e.g. DSTU), and implemented in multiple prototype projects. As well, the responsible work group agrees the resource is sufficiently stable to require implementer consensus for subsequent non-backward compatible changes.
  • FMM5 = FMM4 + the artifact has been published in two formal publication release cycles and has been implemented in at least 5 independent production systems in more than one country

Any of the criteria can be waived provided the sponsoring WG can convince the FMG that that criteria should not apply in the case of a specific artifact.

Tested across scope means:

- The FMG has signed off on the list of "example contexts" defined for the artifact
- For each example context, the artifact has either been: reviewed and approved by a domain expert for that scope area, mapped to an existing implemented scope-area-specific standard or tested in an implementation