IHE Cardiology Technical Framework Supplement Cardiac Imaging ...

More documents

Recommendations

Info

IHE Cardiology Technical Framework Supplement – Cardiac Imaging Report Content (CIRC)______________________________________________________________________________980985990995100010056.2.3.1.1 Responsible PartyThe responsible party element represents only the party responsible for the encounter, notnecessarily the entire episode of care.The responsibleParty element MAY be present. If present, responsibleParty/assignedEntity SHALL have at least one assignedPerson orrepresentedOrganization element present.Note:This is identical to CDTDIR CONF-DIR-67responsibleParty assignedEntity id SHALL be present with the responsiblephysician’s identifier.assignedEntity code SHOULD be present with the responsible physician’s specialty.assignedEntity MAY include an accreditation element from the urn:ihe:cardnamespace to provide physician accreditation status.The accreditation element SHALL use the character string (ST) data type.The accreditation element SHALL appear after the defined elements of the Role class, andbefore any scoper or player entity elements.assignedEntity assignedPerson name SHALL be present with the responsiblephysician’s name.6.2.3.1.2 Health Care FacilityConformance requirements for encoding of information about the Health Care Facility areprovided in the Procedure Note Implementation Guide, and are reproduced here for reference:CONF-PN-18: A Procedure Note SHOULD contain information about where the procedurewas performed.CONF-PN-19: If present, the physical location of the procedure SHALL be represented withcomponentOf/encompassingEncounter/location/ healthCareFacility/idelement.CONF-PN-20: If present, the location/healthCareFacility element SHALL contain acode element representing the type of location.location/ healthCareFacility/ serviceProviderOrganization SHOULD bepresent with name, addr and telecom elements.location/ healthCareFacility/ location (Place Entity) MAY be present with nameand/or addr elements identifying the place of the encounter.healthCareFacility MAY include an accreditation element from the urn:ihe:cardnamespace to provide facility accreditation status.The accreditation element SHALL use the character string (ST) data type.__________________________________________________________________________52Rev. 1.0 – 2011-04-22Copyright © 2011: IHE International, Inc.
IHE Cardiology Technical Framework Supplement – Cardiac Imaging Report Content (CIRC)______________________________________________________________________________1010101510201025103010351040The accreditation element SHALL appear after the defined elements of the Role class, andbefore any scoper or player entity elements.6.2.3.1.3 Referring ProviderConformance requirements for encoding of information about the referring provider are providedin the Procedure Note Implementation Guide, and are reproduced here for reference:CONF-PN-21: A Procedure Note MAY contain information about the referring provider.CONF-PN-22: If present, the referring provider SHALL be represented with acomponentOf/encompassingEncounter/encounterParticipant element.CONF-PN-23: When an encompassingEncounter/encounterParticipantrepresenting the referring provider is present, the encounterParticipant/@typeCodeSHALL be REF (referrer) and an assignedEntity SHALL be present.CONF-PN-24: If elements required in componentOf/encompassingEncounter/encounterParticipant are unknown, these elements SHALL be represented with theappropriate HL7 null value.If present, the referring provider assignedEntity id SHALL be present with one value of theset being the Performer’s National Provider Identifier (root OID = 2.16.840.1.113883.4.6) (in theUS) or the equivalent.The referring provider assignedEntity code SHOULD be present with the referringprovider’s specialty.6.2.3.1.4 Physician of RecordFor procedures performed in an in-patient context, conformance requirements for encoding ofinformation about the Physician of Record are taken from the Diagnostic Imaging ReportImplementation Guide.CONF-DIR-68: A Physician of Record Participant (templateId2.16.840.1.113883.10.20.6.2.2) SHOULD be present.CONF-DIR-69: The templateId for a Physician of Record Participant SHALL be2.16.840.1.113883.10.20.6.2.2.CONF-DIR-70: A Physician of Record Participant SHALL be represented with anencounterParticipant element where @typeCode is ATND.CONF-DIR-71: An encounterParticipant/assignedEntity/id element SHALL bepresent containing the ID of the physician of record.CONF-DIR-72: A encounterParticipant/assignedEntity/code element SHALLbe present and SHALL contain … an appropriate national health care provider coding system(e.g., NUCC in the U.S., where @codeSystem is 2.16.840.1.113883.11.19465).__________________________________________________________________________53Rev. 1.0 – 2011-04-22Copyright © 2011: IHE International, Inc.
Page 2 and 3: IHE Cardiology Technical Framework
Page 76 and 77: ACC Key Data ElementsThe following
Page 102 and 103:
IHE Cardiology Technical Framework
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 ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?