This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "CDA Implementation Guide Quality Criteria"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "Return to SDWG page. NOTE: This is a draft starter set of CDA Implementation Guide Quality Criteria. HL7 Structured Documents WG is putting together...")
 
Line 8: Line 8:
  
 
* Title page
 
* Title page
** Title
+
** Title is specified
** Realm
+
** Realm is specified
** DSTU vs. ??
+
** Ballot type (e.g. DSTU vs. ??) is specified
** Date
+
** Date is specified
** HL7 logo
+
** HL7 logo is present
 +
 
  
 
* Templates
 
* Templates
** 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
** Use of normative binding syntax
+
** Are linked to templates using normative binding syntax
** Value set OID
+
** Each value set is referenced via a value set OID
** CodeSystem OID for each code in value set
+
** Each code in a value set has a specified code system OID
 +
 
  
 
* Examples
 
* Examples
** Inline examples  
+
** Inline examples are present for all templates
** Stand alone complete sample file
+
** 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