HL7 CDA R2 AIS Implementation Guide

More documents

Recommendations

Info

HL7 Additional Information Specification Implementation GuideCDAR2AIS0000R0303.7.16.2.2 Event related administrationSome administrations are temporally related to daily events, such as meals, waking or sleeping.These are recorded using the EIVL data type, as shown below.The event code indicates which event the timing is based on, using one of the codes from Table3.7-3.codeACACDACMACVHSICICDICMICVPCPCDPCMPCVTable 3.7-3 Event Codes for EIVLdefinitionbefore meal (from lat. ante cibus)before lunch (from lat. ante cibus diurnus)before breakfast (from lat. ante cibus matutinus)before dinner (from lat. ante cibus vespertinus)the hour of sleepbetween meals (from lat. inter cibus)between lunch and dinnerbetween breakfast and lunchbetween dinner and the hour of sleepafter meal (from lat. post cibus)after lunch (from lat. post cibus diurnus)after breakfast (from lat. post cibus matutinus)after dinner (from lat. post cibus vespertinus)The element of the element indicates the time before or after the event at whichadministration starts. The element uses the PQ data type. The @value attribute must bepresent, and indicates the duration before (if negative) or after (if positive), and the @unitattribute is the unit of time. The @unit attribute must also be present, and contain one of the unitcodes shown in Table 3.7-2.If the administration is to occur for a specific duration, this shall be recorded in the element of the element. The element uses the PQ data type. The @valueattribute must be present, and indicates the duration, and the @unit attribute is the unit of time.The @unit attribute must also be present, and contain one of the unit codes shown in Table 3.7-2.In most cases the additional information specification will allow the timing and quantity answerpart to repeat, e.g., to express "two pills four times a day for 4 days then 1 pill four times a dayfor 4 days."Page 68March 2007Copyright © 1998-2007Health Level Seven, Inc. All rights reserved.Release 3.0 Draft Standard
HL7 Additional Information Specification Implementation GuideCDAR2AIS0000R0303.7.16.3 ExamplesFigure 3.7-1 shows some examples.twice a day, 30 daysHigh and low values(dates) represent theduration of 30 daysPeriod value indicatesevery 12 hours whichequates to twice a day1 unit of service eachmorning, unspecifieddurationUNK – represents theunspecified durationValue of ACM in the EIVLdata type = beforebreakfast to indicate eachmorning1 unit of service givenone timeHigh and low valuesrepresent single day andthe absence of the EIVLdata type would indicatethat this is a singleoccurrence.twice a day, on Monday,Wednesday and FridayMust be represented textually, cannot be represented in the form specified for GTS inthis implementation guide.Figure 3.7-1 Examples of the GTS data type, computer-decision variantCopyright © 1998-2007 Health Level Seven, Inc. All rights reserved.Release 3.0 Draft StandardPage 69March 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: 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?