This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Requirements-Context Binding"
Jump to navigation
Jump to search
(New page: Context binding is based on the concept of Concept Domains and Binding Realms. Initial model designs reference abstract conc...) |
|||
Line 1: | Line 1: | ||
+ | {{V3 Methodology Requirements}} | ||
+ | |||
Context binding is based on the concept of [[Requirement-Concept Domains|Concept Domains]] and [[Requirement-Binding Realms|Binding Realms]]. Initial model designs reference abstract concept domains that avoid referencing particular sets of codes. Specific sets of codes are then chosen within the context of a particular binding realm. For example, the set of codes used for diagnosis in the U.S. for human patients might be different than that chosen for veterinary patients in Canada. | Context binding is based on the concept of [[Requirement-Concept Domains|Concept Domains]] and [[Requirement-Binding Realms|Binding Realms]]. Initial model designs reference abstract concept domains that avoid referencing particular sets of codes. Specific sets of codes are then chosen within the context of a particular binding realm. For example, the set of codes used for diagnosis in the U.S. for human patients might be different than that chosen for veterinary patients in Canada. | ||
Revision as of 04:53, 18 June 2009
Context binding is based on the concept of Concept Domains and Binding Realms. Initial model designs reference abstract concept domains that avoid referencing particular sets of codes. Specific sets of codes are then chosen within the context of a particular binding realm. For example, the set of codes used for diagnosis in the U.S. for human patients might be different than that chosen for veterinary patients in Canada.
MIF Reference: mif-model-vocabulary.xsd/ContextBinding
Requirement | HL7 Standards must be able to be constructed with coded elements that are not constrained to a specific set of codes, while still constraining the 'types' of codes that are considered appropriate and ensuring that consistent codes are used for a given concept across parts of a specification. |
Rationale |
|
Methodology |
Requirement | Context Bindings may change over time |
Rationale |
|
Methodology | Each vocabulary binding has a start date and may have an end date. (Bindings should not change frequently enough to necessitate a time component) |
MIF |
|