develops standards for the exchange of health related data. Most new glossary-ref
standards developed over the last few years have been based on glossary-ref
. The key features of glossary-ref
A glossary-ref (RIM):
- This provides a framework for the structure of communicated information.
- A formal development method:
- This described the various steps to turn a set of requirements into appropriate models and specifications that support communication of the necessary information.
- Separation between logical models and implementation technologies:
- Many implementations use XML but other technical approaches can be applied to implement the same models.
- Use of external codes systems and terminologies to represent concepts:
- Model specifications include coding constraints expressed in abstract terms as Concept Domains which are implemented as glossary-ref drawn from one or more code systems.
models use glossary-ref
and this has led to growing demand for guidance on consistent patterns of use. In 2004, the glossary-ref
Vocabulary Technical Committee launched the glossary-ref
to address this requirement. The project was initially conceived as having two work packages:
- Specification of a general approach to resolving issues related to the interface between glossary-ref information models and terminologies or code systems;
- A guide to use of glossary-ref in glossary-ref communication standards.
specific package was actively supported by glossary-ref
as part of a charter agreement with glossary-ref
. After several rounds of revision and review, the 'Guide to Use of glossary-ref
' was accepted by glossary-ref
as a glossary-ref
The guide itself contains both normative and informative sections. The normative sections cover:
- Guidance on dealing with specific overlaps between RIM and glossary-ref semantics and recommendations for use of glossary-ref in relevant glossary-ref of various RIM classes;
- Constraints on glossary-ref applicable to relevant glossary-ref in each of the major classes in the Clinical Statement pattern.
- Examples and patterns for representing common clinical statements;
- A general discussion of the potential overlaps between an information model and a glossary-ref and the pros and cons of various possible approaches to their management;
- References to relevant documents and known open issues.
Following adoption the glossary-ref
group have encouraged in-use testing and have elicited and addressed comments on the 'Guide to Use of glossary-ref
. Implementer feedback has further contributed to growing understanding of the issues and resulted in refinement of the guidance. Many of the recommendations included in the 'Guide to Use of glossary-ref
' have been incorporated into domain specific glossary-ref
Standards and national implementations.
One of the conclusions from the glossary-ref
group is a recognition that terminology and information models are co-dependent. They need to evolve collaboratively to meet requirements for unambiguous processable representations of information. Work with other Information Models (including glossary-ref
) indicates that the issues raised by glossary-ref
are not specific to glossary-ref
( Representing clinical information using SNOMED Clinical Terms with different structural information models
). Harmonization efforts involving the glossary-refIHTSDO
and other standards bodies continue to address these issues.
As part of the ongoing harmonization work the copyright of the ' Guide to use of SNOMED CT in HL7 Version 3 ' is jointly held by glossary-ref
. In line with glossary-ref
policies, the document expired as a formal glossary-ref
DSTU after two years but it is included here in full as it continues to serve two glossary-ref
- A glossary-ref of the challenges of integrating an expressive terminology, such as glossary-ref , with a rich information model;
- A pragmatic interim approach to these challenges, which allows for and anticipates the evolution of a more integrated solution.
In practice the relationship scg-expressionShowParts
is represented via intermediate supertype and is also represented by the following defining characteristics scg-expressionShowParts
This is not the case in the first release as the appropriate defining characteristics are not in the release set.