HL7 CDA R2 AIS Implementation Guide

More documents

Recommendations

Info

HL7 Additional Information Specification Implementation GuideCDAR2AIS0000R0303.7.17 "No Information" IndicatorIn any attachment component answer part it may sometimes be impossible to send a requiredanswer and necessary to send, instead, a reason why the information is not available. In thecomputer decision variant the sender shall supplement the natural language explanation of whythe information is not available with appropriate use of the @nullFlavor attribute, as shown inthis example.Body WeightInformation asked but unknownThe possible values within the @nullFlavor attribute are shown in Table 3.7-4.ValueNIOTHUNKASKUNAVNASKTRCNATable 3.7-4 Types of "no information" indicators.InterpretationNo information whatsoever can be inferred from this exceptional value.The actual value is not an element in the value domain of a variable. (e.g., concept notprovided by required code system).A proper value is applicable, but not known.Information was sought but not found (e.g., patient was asked but didn't know)Information is not available at this time but it is expected that it will be available later.This information has not been sought (e.g., patient was not asked)The content is greater than zero, but too small to be quantified.Known to have no proper value (e.g., last menstrual period for a male).The "No information" indicator is not a data type that will be specified in a value table. Instead, itis a value that can be substituted for a value of any data type.3.8 PackageWhen CDA attachments are transmitted with adjunct files in an ASC X12 transaction (such as the275) the CDA document and the adjunct files shall be combined in a single MIME package. TheCDA document shall be the first of the parts of the package. For greater discussion of MIME,refer to section 2.4 MIME Multipart/Related Messages.Page 70March 2007Copyright © 1998-2007Health Level Seven, Inc. All rights reserved.Release 3.0 Draft Standard
HL7 Additional Information Specification Implementation GuideCDAR2AIS0000R0303.9 Attachment-Specific CDA ExtensionsAs described in Clinical Document Architecture Framework, Release 2.0, CDA provides amechanism for extensions to the CDA. At this time, no extensions to the AIS specific attachmentsare defined. Extensions may be defined in the future if needed for new AttachmentImplementation specifications.Senders of a CDA document in a claim attachment transaction should not use extensions notdescribed by this guide. Receivers of a CDA document in a claim attachment transaction must beprepared to receive documents that contain extensions to the CDA.Copyright © 1998-2007 Health Level Seven, Inc. All rights reserved.Release 3.0 Draft StandardPage 71March 2007
Page 1 and 2:
CDAR2AIS0000R030HL7 Additional Info
Page 4 and 5:
HL7 Additional Information Specific
Page 6 and 7:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28: HL7 Additional Information Specific
Page 84: HL7 Additional Information Specific
show all

HL7 CDA R2 AIS Implementation Guide

Create successful ePaper yourself

Delete template?

Save as template?