HL7 CDA R2 AIS Implementation Guide
HL7 CDA R2 AIS Implementation Guide
HL7 CDA R2 AIS Implementation Guide
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>HL7</strong> Additional Information Specification <strong>Implementation</strong> <strong>Guide</strong><strong>CDA</strong><strong>R2</strong><strong>AIS</strong>0000R0302.5.1.15 (Optional)Added since this was in table. Need text.2.5.1.16 (Optional)This element identifies the person who has legally "signed" the document.John E Smith MD2.5.1.17 (Optional)This element identifies the person who has verified the content of the clinical document. Notethat the authenticator may not be the legal party, see .2.5.1.18 (Optional)Added since this was in table. Need text.2.5.1.19 (Optional)This element identifies the predecessor of the clinical document (a previous revision).2.5.1.20 (Attachment Control Number, ACN) (Required)This element identifies the orders associated with this document. At least one elementmust be present and contain the Attachment Control Number associated with the clinicaldocument. [mike: See MLB and DAF comments about matching 275]2.5.1.21 (Optional)This element identifies the services documented, and the performers of those services. Theprovider information must be obtained from the 275 transaction. A service event records theservices performed for a patient and described within the clinical document, e.g., anCopyright © 1998-2007 Health Level Seven, Inc. All rights reserved.Release 3.0 Draft StandardPage 21March 2007
Change language