HL7 Conformance - Intelerad

Merging Patient DemographicsUpdating Patient DemographicsYour system sends a patient update message to synchronize patient data in your systemwith the patient and image data in IntelePACS.Note: Update messages are important and necessary to keep patient dataconsistent between your system and IntelePACS.Physical TriggerA patient informs the front desk staff of anerror in her family name, date of birth, orsex.EffectIntelePACS updates all studies belongingto that patient.Below is an example of a patient update message:MSH|^~\&|RIS|BCREEK|INTELEPACS|Intelerad|20080110164521||ADT^A08|||2.3PID|||1234||Brown^Roger^||19700512|MThe following table lists the required (R) and optional (O) fields for a demographicupdate message. This message must contain at least one of the PID-5, PID-7, or PID-8 fields, which are marked with an asterisk (*).Seg Field Len Opt DefinitionMSH 3 180 R Name of your sending application4 180 R Name of your sending facility5 180 R Name of receiving application (INTELEPACS)6 180 R Name of receiving facility (Intelerad)9 15 R Message type. See “Accepted ADT Events” on page31.PID 3 20 R Patient ID/MRN5 64 * Updated Patient Name7 26 * Updated Patient Date of Birth (YYYYMMDD)8 1 * Updated Patient Sex (M, F, O, or blank)Patient ID (PID-3)IntelePACS only accepts the first field component, PID-3.1, for the patient ID. Onlyone patient ID may be specified in this component.Merging Patient DemographicsYour system sends a merge message to instruct IntelePACS to move the studies for onepatient to another patient.Warning: For every patient merge operation that your system performs on itsown data, it must also send a corresponding patient merge message toIntelePACS.28