IHE Cardiology Technical Framework Supplement Cardiac Imaging ...

More documents

Recommendations

Info

IHE Cardiology Technical Framework Supplement – Cardiac Imaging Report Content (CIRC)______________________________________________________________________________1045CONF-DIR-73: An assignedPerson/name element SHOULD be present containing thename of the physician of record.Copied from Diagnostic Imaging Report Implementation Guide105010556.2.3.2 OrderThe CDA Header SHOULD include an inFulfillmentOf Act Relationship to an order Act.Conformance to the requirements of this section SHALL be indicated by a templateID OID =1.3.6.1.4.1.19376.1.4.1.3.2.order / priorityCode SHALL be present, with values from coding system HL7 ActPriority(OID = 2.16.840.1.113883.5.7).One value within the set of order / id values SHALL be the Accession Number used in theDICOM imaging data, with the root representing the Assigning Authority (Issuer of AccessionNumber).10601065< inFulfillmentOf>Figure 6.2.3.2-1 Order107010756.2.3.3 Patient DemographicsThe CDA Header Patient Entity SHOULD include the elements birthTime,administrativeGenderCode, raceCode and ethnicGroupCode. For the US, raceCodevalue SHALL be drawn from level 0 codes of the HL7 Race coding system (OID =2.16.840.1.113883.5.104), and ethnicGroupCode value SHALL be drawn from level 0 codesof the HL7 Ethnicity coding system (OID = 2.16.840.1.113883.5.50). Note that these elementsmay be encoded with a “flavor of null” if the information is unknown or collection is prohibitedby local regulation.__________________________________________________________________________54Rev. 1.0 – 2011-04-22Copyright © 2011: IHE International, Inc.
IHE Cardiology Technical Framework Supplement – Cardiac Imaging Report Content (CIRC)______________________________________________________________________________1080108510901095Charles David Anderson IIMaui HealthcarePukalani, Maui, HIFigure 6.2.3.3-1 Demographics110011051110111511206.2.3.4 Service Event and PerformerConformance requirements for encoding of information about the Service Event and Performerare provided in the Procedure Note Implementation Guide, and are reproduced here forreference:CONF-PN-31: A Procedure Note SHALL contain one or more documentationOf/serviceEvent elements.CONF-PN-32: The value for serviceEvent/code SHOULD be selected from code system2.16.840.1.113883.6.96 SNOMED CT and MAY be selected from a localized procedurecoding system for a given country such as 2.16.840.1.113883.6.104 ICD9 CM Procedures or2.16.840.1.113883.6.12 CPT-4 in the U.S.CONF-PN-21: A Procedure Note MAY containinformation about the referring provider.CONF-PN-33: The serviceEvent/effectiveTime SHALL be present witheffectiveTime/low and SHALL include effectiveTime/high ifeffectiveTime/width is not present. The serviceEvent/effectiveTime SHALLbe accurate to the day, and MAY be accurate to the second.CONF-PN-34: If the date and only the general length of the procedure are known, theserviceEvent/effectiveTime/low SHALL be present with aneffectiveTime/width element. The serviceEvent/effectiveTime/low SHALLbe accurate to the day, and MAY be accurate to the second.CONF-PN-35: If only the date is known and the duration of the procedure is unknown, theserviceEvent/effectiveTime/width element SHALL contain the appropriate HL7 nullvalue.CONF-PN-36: The primary performers (PPRF) SHALL be identified.__________________________________________________________________________55Rev. 1.0 – 2011-04-22Copyright © 2011: IHE International, Inc.
Page 2 and 3:
IHE Cardiology Technical Framework
Page 4 and 5: IHE Cardiology Technical Framework
Page 76 and 77: ACC Key Data ElementsThe following
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
show all

IHE Cardiology Technical Framework Supplement Cardiac Imaging ...

Create successful ePaper yourself

Delete template?

Save as template?