This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR Maturity Model"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | This page describes the 5 level FHIR maturity model for resources. It's based on the CMM framework, and the intention is to give implementers a sense of how mature a resource is | + | This page describes the 5 level FHIR maturity model for resources. It's based on the CMM 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 | * FMM0 = the resource or profile (artifact) has been published on the current build | ||
Revision as of 21:40, 3 June 2015
This page describes the 5 level FHIR maturity model for resources. It's based on the CMM 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 at an HL7 International connectathon
- FMM3 = FMM2 + the artifact 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, published in a formal publication (e.g. DSTU), and implemented in multiple prototype projects
- 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.
