This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR Maturity Model"
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
* FMM2 = FMM1 + the artifact has been tested at a connectathon | * FMM2 = FMM1 + the artifact has been tested at a connectathon | ||
* FMM3 = FMM2 + the artifact has been subject to a round of formal balloting with at least 10 implementer comments from at least 3 organizations resulting in substantive change | * FMM3 = FMM2 + the artifact has been subject to a round of formal balloting with at least 10 implementer comments from at least 3 organizations resulting in 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 | + | * 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 | + | * FMM5 = FMM4 + the artifact has been published in two formal publication release cycles and has been implemented in at least 3 independent production systems in more than one country |
Revision as of 15:44, 15 May 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
- 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 a connectathon
- FMM3 = FMM2 + the artifact has been subject to a round of formal balloting with at least 10 implementer comments from at least 3 organizations resulting in 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 3 independent production systems in more than one country
