This wiki has undergone a migration to Confluence found Here

Asserting Conformance to this Implementation Guide

From HL7Wiki
Revision as of 13:44, 18 July 2012 by Rhausam (talk | contribs) (Created page with "<div class="subSubSection"> <div class="header"> 1.9 </div> <div class="body"> This specification defines constraints on the use of SNOMED CT in an HL7 V3 instance. HL7 V3 ...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
1.9

This specification defines constraints on the use of SNOMED CT in an HL7 V3 instance. HL7 V3 provides a mechanism to reference a template or implementation guide that has been assigned a unique identifier, by referencing the guide's identifier in the InfrastructureRoot.templateId field. The formal identifier for this guide is '2.16.840.1.113883.10.5'.


We probably need to make some adjustments to this? Presumably the templateId can still be used? Need to check. RH

The following example shows how to formally assert the use of this implementation guide. Use of the templateId indicates that the HL7 V3 instance not only conforms to the base specification, but in addition, conforms to constraints specified in this implementation guide.


1.9.1
<V3Instance>
  <templateId root='2.16.840.1.113883.10.5'/>
  ...
</V3Instance>

NOTE: The normative constraints in this guide are expressed in a technology-neutral formalism. The key words "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", and "NEED NOT" in this document are to be interpreted as described in the HL7 Version 3 Publishing Facilitator's Guide. Various options for computable representations are under consideration and non-normative example implementations may be provided in the future.