Difference between revisions of "Requirements-Terminology Model"
|Line 41:||Line 41:|
| terminology be . to a of the artifacts that a the "" .
Revision as of 19:14, 7 October 2009
A terminology model is a collection of terminology artifacts that, together, support defining the terminology constraints that can apply in standard specifications. The specific types of artifacts that a terminology model may contain include:
- Concept Domains
- Code Systems
- Value Sets
- Binding Realms
- Context Bindings
- Code Translations
- Code System Supplements
Note: The requirements for why each of the above artifacts are necessary are covered either elsewhere within this specification or in the requirements listed below.
|Requirement||Terminology Models need to be able to be packaged and identified as a single artifact|
|Rationale||While made up of multiple distinct parts, there are significant dependencies between all of the aspects of a set of terminology artifacts. Specifications need to be able to easily reference the set of terminology artifacts that apply to them. The easiest way to do that is to define a single "package" containing all of the terminology artifacts that can be updated from time to time and which can be referenced either as a specific version of the package or as "the current package".|
|Requirement||Terminology models must identify any other terminology models they are dependent on|
|Rationale||Because of the vast number of code systems, value sets, mappings and other terminology artifacts that will exist and the wide variety of organizations that create and maintain those artifacts, it is unrealistic to expect that all terminology artifacts could possibly be encompassed or published within a single model. Multiple models are inevitable. However, most models will have dependencies on contents that are in turn defined within other models. (In some cases, the dependencies may be circular). Understanding the models a given terminology model depends on is therefore essential to being able to use that model.|
|Requirement||When persisting or exchanging a representation of a terminology model, there are various degrees of detail that may need to be exposed and the persisted artifact needs to indicate what level of representation is present.|
|Rationale||Some terminology models may be intended for "publication" and therefore provide a more limited view. Others will have been constrained to only show a subset of the artifacts that exist within the model. It's important when looking at a given model representation whether you're looking at the "whole thing" or only a subset.|
|Methodology||Possible levels are:
|Requirement||Terminology Models may have a number of different types of annotations|
|Rationale||See rationales for individual annotations types|