This wiki has undergone a migration to Confluence found Here
Difference between revisions of "CDA Implementation Guide Quality Criteria"
Jump to navigation
Jump to search
| Line 13: | Line 13: | ||
** Date is specified | ** Date is specified | ||
** HL7 logo is present | ** HL7 logo is present | ||
| − | |||
* Templates | * Templates | ||
** Each template has a narrative description | ** Each template has a narrative description | ||
** Constraints are ordered per the CDA schema | ** Constraints are ordered per the CDA schema | ||
| − | |||
* Value sets | * Value sets | ||
| Line 24: | Line 22: | ||
** Each value set is referenced via a value set OID | ** Each value set is referenced via a value set OID | ||
** Each code in a value set has a specified code system OID | ** Each code in a value set has a specified code system OID | ||
| − | |||
* Examples | * Examples | ||
** Inline examples are present for all templates | ** Inline examples are present for all templates | ||
** A stand alone complete sample file is present | ** A stand alone complete sample file is present | ||
Revision as of 21:27, 29 August 2012
Return to SDWG page.
NOTE: This is a draft starter set of CDA Implementation Guide Quality Criteria. HL7 Structured Documents WG is putting together a Project Scope Statement to flesh these out in more detail. For now, think of this page more as a scratch pad where anyone can list their suggestions.
Suggested CDA Implementation Guide Quality Criteria
- Title page
- Title is specified
- Realm is specified
- Ballot type (e.g. DSTU vs. ??) is specified
- Date is specified
- HL7 logo is present
- Templates
- Each template has a narrative description
- Constraints are ordered per the CDA schema
- Value sets
- Are linked to templates using normative binding syntax
- Each value set is referenced via a value set OID
- Each code in a value set has a specified code system OID
- Examples
- Inline examples are present for all templates
- A stand alone complete sample file is present
