The PatientManager is able to act as a Patient Demographics Supplier for the Patient Demographic Query integration profile. Both the Pediatric Demographics and Patient Demographic and Visit Query options are implemented. As a consequence, the simulator can be used as a responder for the following transactions:
The table below gathers the parameters the simulator is able to map to its database to perform the query and send back the batch of corresponding patients. Note that when several parameters are provided, the AND operator is used to build the database query; the "*" wildcard is supported to substitute zero or more characters. The returned patients are those owned by the Patient Demographic Supplier actor. To consult the list of available patients, see http://gazelle.ihe.net/PatientManager/patient/allPatients.seam?actor=PDS . Note that only the subset of active patients is queried.
Table-1 : PQD-3 fields supported by the PDQ/PDS simulator for ITI-21 transaction
|
HL7 FIELD |
ELEMENT NAME |
JAVA OBJECT / ATTRIBUTE (indicative) |
SQL CLAUSE |
EXTRA INFO |
|
PID.3 |
Patient Identifier List | patient.patientIdentifiers | like (ignores case) | also filter according to QPD-8 |
| PID.3.1 | Patient Identifier List (ID Number) | patientIdentifer.fullPatientId | like (ignores case), MatchMode = START | |
| PID.3.4.1 | Patient Identifier List (Assigning Authority - namespace ID) | patientIdentifier.domain.namespaceID | domain namespaceID like (ignores case) | |
| PID.3.4.2 | Patient Identifier List (Assigning Authority - universal ID) | patientIdentifier.domain.universalID | domain universal ID like (ignores case) | |
| PID.3.4.3 | Patient Identifier List (Assigning Authority - universal ID Type) | patietnIdentifier.domain.universalIDType | domain universal ID type like (ignores case) | |
| PID.3.5 | Patient Identifier List (Identifier Type Code) | patientIdentifier.identifierTypeCode | like (ignores case) | |
| PID.5.1.1 | Patient Name (family name/surname) | patient.lastName | like (ignores case) | |
| PID.5.2 | Patient Name (given name) | patient.firstName | like (ignores case) | |
|
PID.7.1 |
Date/Time of Birth | patient.dateOfBirth | between 'date 0:00 am' to 'date 11:59 pm' | date format : yyyyMMddHHmmss |
|
PID.8 |
Administrative Sex | patient.genderCode | equals | Gender code (F, M ...) |
|
PID.11.1 |
Patient Address (Street) | patient.street | like (ignores case) | |
| PID.11.3 | Patient Address (City) | patient.city | like (ignores case) | |
| PID.11.4 | Patient Address (State) | patient.state | like (ignores case) | |
| PID.11.5 | Patient Address (Zip Code) | patient.zipCode | like (ignores case) | |
| PID.11.6 | Patient Address (Country Code) | patient.countryCode | like (ignores case) | iso3 |
|
PID.18 |
Patient Account Number | patient.accountNumber | like (ignores case) | |
| PID.18.1 | Patient Account Number (ID Number) | patient.accountNumber | like (ignores case), MatchMode = START | |
| PID.18.4.1 | Patient Account Number (Assigning Authority - namespace ID) | patient.accountNumber | like (ignores case) %^^^value, MatchMode = START | |
| PID.18.4.2 | Patient Account Number (Assigning Authority - universal ID) | patient.accountNumber | like (ignores case) %^^^%&value, MatchMode = START | |
| PID.18.4.3 | Patient Account Number (Assigning Authority - universal ID Type) | patient.accountNumber | like (ignores case) %^^^%&%&value, MatchMode = START | |
|
PID.6.1.1 |
Mother's maiden name (last name) | patient.mothersMaidenName | like (ignores case) | |
|
PID.13.9 |
Phone Number - Home (any text) | patient.phoneNumber | like (ignores case) |
The table below gathers the parameters the simulator is able to map to its database to perform the query and send back the batch of corresponding patients. Note that when several parameters are provided, the AND operator is used to build the database query; the "*" wildcard is supported to substitute zero or more characters. The returned patients are those owned by the Patient Encounter Supplier actor. To consult the list of available patients, see http://gazelle.ihe.net/PatientManager/patient/allPatients.seam?actor=PES. Note that only the subset of open encounters for active patients is queried.
The parameters gathered in table Table-1 are also supported for this transaction. In addition, you can provide the following parameters (see Table-2).
Table-2 : PQD-3 fields supported by the PDQ/PDS simulator for ITI-22 transaction
|
HL7 FIELD |
ELEMENT NAME |
JAVA OBJECT / ATTRIBUTE (indicative) |
SQL CLAUSE |
EXTRA INFO |
| PV1.2 | Patient class | encounter.patientClassCode | equals | Patient class code (I, O ...) |
| PV1.3.1 | Assigned Patient location (Point of care) | movement.assignedPatientLocation | like (ignores case), MatchMode = START | |
| PV1.3.2 | Assigned Patient location (Room) | movement.assignedPatientLocation | like (ignores case) %^value, MatchMode = START | |
| PV1.3.3 | Assigned Patient location (Bed) | movement.assignedPatientLocation | like (ignores case) %^%^value, MatchMode = START | |
| PV1.3.4 | Assigned Patient location (Facility) | movement.assignedPatientLocation | like (ignores case) %^%^%^value, MatchMode = START | |
| PV1.7 | Attending doctor | encounter.attendingDoctor | like (ignores case) | |
| PV1.8 | Referring doctor | encounter.referringDoctor | like (ignores case) | |
| PV1.10 | Hospital service | encounter.hospitalServiceCode | like (ignores case) | |
| PV1.17 | Admitting doctor | encounter.admittingDoctor | like (ignores case) | |
| PV1.19.1 | Visit number (ID number) | encounter.visitNumber | like (ignores case) | |
| PV1.19.4.1 | Visit number (Assigning authority namespaceID) | encounter.visitNumberDomain.namespaceID | like (ignores case) | |
| PV1.19.4.2 | Visit number (Assigning authority universalID) | encounter.visitNumberDomain.universalID | like (ignores case) | |
| PV1.19.4.3 | Visit number (Assigning authority universal ID Type) | encounter.visitNumberDomain.universalIDType | like (ignores case) |
The list of the domains known by the Patient Demographics Supplier actor is available under Patient Demographics Query / Patient Demographics Suppliers. It is built up from the list of different assigning authorities for which the simulator owned patient identifiers.
As defined in the technical framework, the Patient Demographics Supplier is able to send results in a interactive mode using a continuation pointer. The list of pointers is regularly cleaned up, a pointer for which no request has been received within the previous hour is destroyed.
When querying the supplier in interactive mode, the Patient Demographics Consumer can send a cancel query message (QCN^J01^QCN_J01) to inform the supplier that no more result will be asked. At this point, the supplier destroys the pointer associated to the provided query tag.