Requirements-Binding Realms

Binding Realms provide "bounded areas of interoperability" in which a concepts can be expected to be communicated with a common set of codes. They exist because of the recognition that there can be variations in terminologies required across geographies, cultures, types of patient (human vs. veterinary; pediatric vs. geriatric) and even type of medicine.

MIF Reference: mif-model-vocabulary.xsd/BindingRealm

Requirement	Each binding realm must have a unique name
Rationale	The binding realm must be able to be precisely referenced when creating context bindings. It also needs to be referenced within instances or profiles to declare what "context" applies for that instance.
MIF	mif-model-vocabulary.xsd/BindingRealm/@name
OMG Mapping	Add stereotype bounded to capture information and use relationships to identify bounded elements

Requirement	Each binding realm must have a description
Rationale	In order to know what binding realm to use when referencing a particular context, you need to know what that context is
MIF	mif-model-vocabulary.xsd/BindingRealm/description
OMG Mapping	Use UML Note

Requirement	Each binding realm must have a responsible affiliate
Rationale	Because realm bindings are so essential to interoperability, the ability to construct new ones is limited to HL7.org and to HL7 affiliates. That prevents the proliferation of new "contexts" by any organization that doesn't want to follow the vocabularies chosen at a higher level.
MIF	mif-model-vocabulary.xsd/BindingRealm/@owningAffiliate
OMG Mapping	Add stereotype affiliate for packages to capture information/contexts

Requirement	The set of binding realms must be tightly constrained
Rationale	Binding realms are a key part of interoperability. If you don't know the binding realm, you don't know what terminologies are allowed. In addition, names must be maintained unique within a single universal namespace. Therefore there needs to be a consistent source for what binding realms exist and may be used
Methodology	HL7.org maintains the sole list of binding realms that may be used. Affiliates are allowed to create binding realms beneath their own HL7-assigned binding realm, but these "sub-binding realms" must be registered with HL7.org

Requirement	Binding realms need to be able to track statuses over time.
Rationale	Like other vocabulary objects, Binding realms can be draft, active, deprecated or even retired. In some cases, they even get resurrected. Users need to know what the status of a binding realm is right now as well as what it was at times in the past.
MIF	mif-vocabulary-model.xsd/BindingRealm/statusInfo