HL7 v3 Requirements
This page and its descendant links are an attempt to define the functional and non-functional requirements HL7 has for its standards development methodology, as well as how the methodology meets those requirements and how the requirements are manifested in HL7's metamodel, the MIF.
The requirements are broken into several sections. The first describes the requirement. Following each requirement is a list of supporting rationale. I.e. "Why is this a requirement". Finally, there's up to two additional sections:
- a list of how the requirement is implemented in the methodology. The methodology section explains the mechanism(s) that support that requirement within the HL7 v3 standards development methodology. Each methodology reference is a link to a separate tab that describes the methodology. Each methodological approach may have its own set of requirements that are driven by the methodological approach
- a list of MIF data elements that 'implement' the requirement in HL7's v3 metamodel
High-level HL7 V3 requirements
|Requirement||HL7 standards must be usable in diverse healthcare environments communities throughout the world in circumstances where global consensus down to the detailed 'implementable' level is not (yet) feasible.|
|Requirement||HL7 v3 standards must provide both functional and semantic and interoperability.
I.e. HL7 v3 specifications must standardize both the data structures and mechanics of information exchange as well as the understanding of what that data means and how it is to be used.
|Requirement||HL7 v3 standards should, as much as possible, be independent of an particular implementation technology and should be capable of making use of particular implementation technologies in a standardized way.|
|Rationale||With HL7 v2, the organization experienced the challenges associated with a specification that was too tightly bound to a particular implementation technology. One of the objectives for HL7 v3 was to be technology independent.|