This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Reference - Informational"
Jump to navigation
Jump to search
| Line 29: | Line 29: | ||
=Candidate Artifacts= | =Candidate Artifacts= | ||
| − | + | * HL7 Reference Information Model (RIM) | |
| − | + | * HL7 Abstract Data Types (ADT) | |
| − | + | * HL7 Vocabulary References | |
| − | + | * TermInfo Guides | |
| − | + | * Clinical Document Architecture Model (CDA) | |
| − | + | * Clinical Statement Model | |
| − | + | * Orders and Requests Pattern Model | |
| − | + | * Implementable Tech Specification (ITS) | |
| − | + | * HL7 Foundation and Core Principles | |
| − | + | * HL7 Development Framework (belong here or elsewhere)? | |
| − | + | * WC3 (for ITS) | |
| − | + | * OMG (for ITS?) | |
=Examples= | =Examples= | ||
Revision as of 03:18, 10 May 2009
Reference - Informational Owner PEL will do, ?? will review
Summary
- Artifacts that can be used as reference for information viewpoint artifacts in subsequent conformance levels.
Detail - Reference Semantics at the Informational Level TODO
Contents
Traceability to Reference Material
TODO
Best Practices / Templates
TODO
Quality Criteria
TODO
Conformance Statement
TODO
Guidance on format of Conformance Statement
TODO
Relationship to and Consistency with other Viewpoints
TODO
Candidate Artifacts
- HL7 Reference Information Model (RIM)
- HL7 Abstract Data Types (ADT)
- HL7 Vocabulary References
- TermInfo Guides
- Clinical Document Architecture Model (CDA)
- Clinical Statement Model
- Orders and Requests Pattern Model
- Implementable Tech Specification (ITS)
- HL7 Foundation and Core Principles
- HL7 Development Framework (belong here or elsewhere)?
- WC3 (for ITS)
- OMG (for ITS?)
Examples
The following examples are full specifications. Following the link, the appropriate sections of the specifications that support the Computational Viewpoints are in brackets.
- Example 1 - TODO
- Example 2 - TODO
- Example 3 - TODO
Back to SAEAF Specification Stack
