Guides

Patient Demographics

IMS/Patient Demographics Interface

The IMS/Patient Demographics interface can be used to create identities for a healthcare facility or for a specific healthcare professional. These created identities are then available for healthcare professionals:

  • In Rofim, to be used in medical acts (MultiDisciplinary Meetings, Teleconsultation or Assisted Teleconsultation, Teleexpertise, Referral)
  • In the interoperability use cases detailed in the following sections.

IMS/Patient Demographics Interface

DataValue
Supported FormatIHE PAM 2.5 to 2.7
Supported Messages (input)
  • ADT 01 or ADT 04or ADT 05 for creating patient data (with admission/venue).
  • ADT 28 for creating patient data (without admission/venue), mainly used if all patients from the facility are sent to Rofim.
  • ADT 31 for modifying patient data.
  • ADT 40 for updating IPP/Patient ID following a merge
Message TypePOST
API Linkbase_url/ims

Important Data

Rofim relies on standard messages and retrieves information from fields standardized by IHE. However, certain rules and format requirements must be respected. These are described below.

Patient Demographics Data

Patient identity data is retrieved from the PID segment and ADT messages. The table below details the important data.

DataFieldFormatRequiredComment
Patient ID / IPPPID.3.1StringYesPID.3.1 when PID.3.5='PI'
Patient SSNPID.19StringNoSocial Security Number
Patient INSPID.3.1StringNoPID.3.1 when PID.3.4 contains 'ASIP-SANTE-INS'
Country specific : 🇫🇷
Patient First NamePID.5.2StringYesPID.5.2 when PID.5.7='D'
Patient Birth NamePID.5.1StringYesPID.5.1 when PID.5.7='L'
Patient Usual NamePID.5.1StringNoPID.5.1 when PID.5.7='D'
Patient GenderPID.8.1StringYesM or F expected
Patient Date of BirthPID.7.1DateYesBirth date/time in HL7 Time Stamp format, for example: 19730416
Patient Phone NumberPID.13.1StringNoUses number of type PID.13.3='CP', or if absent, the one of type PID.13.3='PH' Number must be in format +33601010101, according to E.164 standard
Patient Email AddressPID.13.4StringNoWhen PID.13.2='NET'
Patient Postal Address StreetPID.11.1StringConditionalAddress must be complete or completely absent, meaning presence of all PID.11.* fields or none
Patient Postal Address Zip CodePID.11.5StringConditional
Patient Postal Address CityPID.11.3StringConditional
Patient Postal Address CountryPID.11.6StringConditional
❗️

In case of incompatible format for email address or phone number, patient creation will be rejected and the patient will not be created.

Visit Data

The patient, when created, must be attached to a doctor or a network. This data must be indicated in ADT 01, ADT 04, ADT 05or ADT 28 messages in the PV1 segment.

DataFieldFormatRequiredComment
Doctor ID (RPPS)PV1.7.1StringConditionalValue of PV1.7.1 if field PV1.7.13='RPPS'.
This field is required if PV1.10 is absent
Department or ServicePV1.10StringConditionalThis data must correspond to a Rofim network ID. If this data is populated, the patient will be created on the corresponding network. In case of an ADT 28 message, this segment must be added to the standard message.
Patient IEP / Admission IDPV1.19.1StringConditionalPatient admission ID. This field is not required for patient creation but may be necessary for report and billing flows. This data can be updated later when creating acts (MDM, TE, TC, TCA...).
Functional UnitPV1.3.1StringConditionalThis field is not required for patient creation but may be necessary for report and billing flows. This data can be updated later when creating acts (MDM, TE, TC, TCA...)
📘

In case of simultaneous presence of Doctor ID (RPPS) and Department or Service data, the patient will be created on the Department or Service

Other ADT Message Data

Other data in ADT messages must comply with HL7 and IHE PAM 2.5 to 2.7 standards.

DataFieldFormatRequiredComment
Referring Doctor ID (RPPS)ROL.4.1StringConditionalValue of ROL.4.1 if field ROL.4.13='RPPS'and ROL.3.1='ODRP'

Expected Message Examples

TODO
MSH|^~\&|1.2.250.1.211.7.1.200.1.2|MCK|EAI|EAI|20250326095554||ADT^A04^ADT_A01|131194658|P|2.5^FRA^2.5|50587254||||FRA|8859/1|||A03^IPG~ADD_ENTREE_HOPITAL^INTEG
EVN||20250326095532|||BRICEVA
PID|||231067^^^MCK&1.2.250.1.211.10.200.1&ISO^PI~198765678765^^^ASIP-SANTE-INS-NIR&1.2.250.1.213.1.4.8&ISO^INS||XXXXX^XXXXXXXX^XXXXXXXXXX^^^^L||19000101000000|M|||XXXXXXXXI^XXXXXX^XXXXXXXXXXXX^^130000^FRA^H~^^^^^UNK^C~^^MARSEILLE^^13000^FRA^BDL^^13000||0600000000^PRN^PH~0600000000^PRN^PH~0600000000^PRN^[email protected]^NET^internet|||W||12345678765^^^MCK|||||MARSEILLE|||FRA||||N||VALI
PV1||O||||||234567SDF^DR^DR^^^^^^^ASIP-SANTE-PS&1.2.250.1.71.4.2.1&ISO^^^ADELI||||||||N|||562062153^^^MCK&1.2.250.1.211.12.1.1&ISO^AN|C|07|N|||||||||||||||||||N|||20250328070000|20250328235900
PV2|||||||TO
ZBE|EH_11502436_1^MCK|20250328070000||INSERT|N||^^^^^^UF^^CO3849^3849|^^^^^^UF^^^6568a83b8cc13bbb05b0d76f|M
ZFP| | 
ZFV| 
ZFM| 
IN1|1|972|||||||||||47121231|||XXXXXX^XXXXXXX|||||||||||||||||||||||||||||||||12345678765432345
IN2||||||||||||||||||||||||||||^C
TODO
MSH|^~\&|HM_HFAC|HM_HFAC|OXYGENE|HFAC|20251021143421||ADT^A31^ADT_A05|504333293|P|2.5^FRA^2.5||||AL|FRA|8859/1|FR
EVN||20251021143414|||I10249^Name FirstName^^^^^^^I_MONACO^D^^^EI
PID|1||999888777^^^I_HFAC^PI||ROFIM UN MAJ^Prenom Maj^Prenom^^MR^^L||20251021000000|M|||Adresse 1 MAJ^Adresse 2\S\Adresse 3^PARIS^^75000^100^H~^^PARIS^^75000^100^BDL^^99138||^PRN^PH^^^^^^06.06.06.06.06^^^0606060606~^NET^Internet^[email protected]||||||||||75000 PARIS||1|138^PARIS||||N||PROV
PV1|1|N||||||||
TODO