HL7 Conformance - Intelerad

More documents

Recommendations

Info

3SendingReports toIntelePACSYour system can send inbound report and addendum information toIntelePACS with ORU messages.In this Chapter:Sending a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Sending an Addendum or Correction . . . . . . . . . . . . . . . . . 22Sending and Migrating Historical Reports . . . . . . . . . . . . . . 23Descriptions of Fields for Report Messages . . . . . . . . . . . . . 23
Sending Reports to IntelePACS 3Sending a ReportA report message informs IntelePACS of a report for an existing order.Physical TriggerReport is dictated, transcribed, thensigned.EffectIntelePACS displays report text in thereport viewers in InteleViewer andIntelePACS Browser.Below is an example of a report message with all required fields filled:MSH|^~\&|RIS|BCREEK|INTELEPACS|<strong>Intelerad</strong>|20080124164827||ORU^R01|||2.3PID|||1234||Brown^Roger^||19700203|MPV1||||||||MHIBROY^Hibroy^MORC||885|885||ZZOBR||885|885|||||||||||||||885|1|1||||||||||||48^Doe^John^^^20090116174405|||52^Lee^Hugh^^^20090117083405OBX|||||Original report.||||||FThe following table lists the required (R) and optional (O) fields for report andaddendum messages. Fields marked with an asterisk (*) might be required, dependingon the IntelePACS workflow. For detailed explanations of the fields for addenda, see“Descriptions of Fields for Report Messages” on page 23.Seg Field Length Opt DefinitionMSH 3 180 R Name of your sending application.4 180 R Name of your sending facility.5 180 R Name of receiving application (INTELEPACS).6 180 R Name of receiving facility (<strong>Intelerad</strong>).9 15 R Message type (ORU^R01).PID 3 20 R Patient ID/MRN.5 64 R Patient Name.7 26 R Patient Date of Birth (YYYYMMDD).8 1 R Patient Sex (M, F, O, or blank).PV1 8 60 * Referring Physician.ORC 2 16 R Placer Order Number. Can be the accessionnumber.3 16 R Filler Order Number. Can be the accessionnumber.5 2 R Order Status (ZZ for final reports and ZY forpreliminary reports. In most cases only finalreports are sent to IntelePACS.)17 8 O Entering Organization.21
Page 3 and 4: Table ofContents1 Getting Started 1
Page 5 and 6: 1GettingStartedMany healthcare mana
Page 7 and 8: Getting Started 1Specifying Patient
Page 9 and 10: Getting Started 1Working with DICOM
Page 11 and 12: 2Sending OrderMessagesYour system c
Page 13 and 14: Sending Order Messages 2Seg Field L
Page 19 and 20: Sending Order Messages 2• Automat
Page 23: Sending Order Messages 2If your RIS
Page 27 and 28: Sending Reports to IntelePACS 3Send
Page 29 and 30: Sending Reports to IntelePACS 3Orde
Page 31 and 32: 4SendingAdministrationMessagesYour
Page 33 and 34: Sending Administration Messages 4Af
Page 35 and 36: Sending Administration Messages 4Ac
Page 37 and 38: Receiving Orders from IntelePACS 5R
Page 39 and 40: Receiving Orders from IntelePACS 5T
Page 45 and 46: Receiving Orders from IntelePACS 54
Page 47 and 48: Receiving Reports from IntelePACS 6
Page 49 and 50: Receiving Reports from IntelePACS 6
Page 51 and 52: AHL7 Fields forModalityWorklistsThi
Page 53 and 54: HL7 Fields for Modality WorklistsAP
Page 55 and 56: HL7 Fields for Modality WorklistsAD
Page 57 and 58: HL7 Fields for RIS-Driven Prefetchi
Page 63 and 64: HL7 Fields in IntelePACSCHL7 Fields

HL7 Conformance - Intelerad

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

Delete template?

Save as template?