HL7 v3 Requirements
These are high-level HL7 requirements identified by HL7 for the v3 methodology, based on past experience, industry best practice or brought forward by the HL7 membership.
|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.|
|Requirement||HL7 v3 specifications must be published in a manner that ensure strict alignment between the "source of truth" and the form rendered to those reviewing and implementing the standards|
|Rationale||Failure for the source of truth to align with what is reviewed (to complete)|