This wiki has undergone a migration to Confluence found Here
Difference between revisions of "TermInfo Principles"
Jump to navigation
Jump to search
(Created page with "Draft Terminfo principles: #Provide guidance on overlap between the terminology and information models ##Include when (and when not) to post-coordinate ##Evaluate consistency an...") |
|||
Line 1: | Line 1: | ||
Draft Terminfo principles: | Draft Terminfo principles: | ||
− | # | + | #Recommendations will provide guidance on overlap between the terminology and information models |
##Include when (and when not) to post-coordinate | ##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 | #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) |
Revision as of 17:40, 15 February 2012
Draft Terminfo principles:
- 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)