Difference between revisions of "TermInfo Principles"
Jump to navigation Jump to search
Revision as of 23:30, 23 January 2013
- Recommendations will provide guidance on overlap between the terminology and information models
- Include when (and when not) to post-coordinate
- Recommendations will be driven by use cases
- Guide will include specific and consistent examples of clinical information
- Use cases will include not only clinical information but also technical constraints
- Recommendations will align with the goals of terminology development organizations (including HL7 and others)
- Recommendations must be implementable by stakeholder user communities
- This may mean that recommendations must support more than one approach
- Recommendations will support consistent precision of representation between the terminology and the information model. [I’m still not sure I understand this one. Original text: “Evaluate consistency and precision of representation between the terminology and the information model ”]
- Semantics must be explicit, even in tools that do not easily support explicit semantics (e.g., class diagrams, RDBMS).
- When recommendations provide options, they will specify patterns for semantically rigorous transformations among options. (Last two may overlap a bit)
Draft Audience Segments
- Clearly and explicitly guide standards modelers in incorporating SCT and LOINC values into HL7 V2 and V3 artifacts in ways that fulfill the semantic constraints of both information model and terminology.
- Provide implementers (e.g., software developers) with clear guidance on their options for representing data in instances.
- Provide information consumers (e.g., report writers or researchers) with clear descriptions of the semantics of conforming artifacts.
- Provide terminology developers with clear feedback on the uses to which terminologies are put.