To prepare for testing workflow profiles in RAD, CARD, LAB, and EYECARE domains, and also for the ITI PAM Profile, it is helpful for systems that send HL7 messages (eg patient registration and orders) and/or DICOM messages (modality worklist, storage) to work with a common set of codes. 

We ask ADT, Order Placer, Order Filler and Acquisistion Modality actors and PAM Patient Demographic & Encounter Supplier actors to load codes relevant to their system in advance of the Connectathon

These codes include, for example:

  • Administrative sex codes in PID-8
  • Dcotors sent in PV1
  • Facility codes sent in HL7 PV1-3
  • Universal Service ID (order codes) sent in OBR-4
  • Priority codes sent in OBR-27 or TQ1-9
  • Acquisition Modality code sent in OBR-24 and (0008,0060)
  • ...and more


The codes that you need depend on the profile/actors you support.  HL7 and DICOM codes used for Connectathon testing are the same set that is used in the Gazelle OrderManager tool. OrderManager contains simulators for some actors in workflow profiles.

** HL7 codes ** - are documented here:

Some of these codes are also mapped into DICOM messages.  Use the spy-glass icon in the right column to view the value set for each code.  (Note that the format of these files is compliant with the IHE SVS Sharing Value Sets profile.)

  • ADT, Order Placer, and Order Filler plus PAM Supplier systems should review the link above and load codes relevant to the HL7 messages it supports

** DICOM codes ** - Order Filler and Acquisition Modality actors need a mapping between Requested Procedure codes, Scheduled Procedure codes, and Protocol Codes. 

For RAD and CARD, that hierarchy is here:   
For EYECARE, that hierarchy is here: (Note that this is documented in excel form here.)

  • An Order Filler system should load codes relevant to the domain(s) it is testing. 
  • An Acquisition Modality system should load codes relevant to the acquisitions it can perform. 


There is no evaluation for this 'test'.   If you do not load the codes you need on your test system prior to the Connectathon, you may find yourself wasting valuable time on the first day of Connectathon syncing your codes with those of your test partners.