Patient Demographics Query for Mobile (PDQm)
3.1.0 - Trial-Implementation International flag

This page is part of the IHE Patient Demographics Query for Mobile (v3.1.0: Publication) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions

Resource Profile: PDQm Patient Profile

Official URL: https://profiles.ihe.net/ITI/PDQm/StructureDefinition/IHE.PDQm.Patient Version: 3.1.0
Active as of 2024-12-02 Computable Name: PDQmPatient

Overview

The PDQm Patient Profile establiashes the following base requirements:

  • when any element in FHIR Core Patient are known, and when authorized to return the element, then all elements that are core to FHIR Patient SHOULD be returned
  • forbids modifier extensions and implicit rules - so that all uses do not need to be concerned with changes to the meaning of the core elements of the Patient resource
  • adds the patient-mothersMaidenName extension as an extension available to hold the mother’s maiden name

Use of Business Identifiers

To facilitate working with and matching resources across specifications and servers, Patient.identifier is REQUIRED. Including business identifiers in Patient.identifier is important for allowing the Patient resource to maintain identity outside of the context of the FHIR server on which it resides. This would be the case when the resource is copied to another server, saved to a file, migrated to a new FHIR server, etc.

Patient.identifier is typically populated with an identifier assigned by an assigning authority in the local patient identifier domain. Populating with identifiers issued by jurisdictional authorities, such as the patient’s national identifier, drivers license number, jurisdictional healthcare identifier, etc., is also typical when policy allows for those identifiers to be disclosed to the client system.

When no existing business identifier exists, the Patient Demographics Supplier might construct one in one of the following ways:

Option 1: Populate Patient.identifier.value with the full URL for the Patient resource as it would be accessed by the client when doing a READ request. In this case, the corresponding value for Patient.identifier.system SHALL be urn:ietf:rfc:3986.

Option 2: Populate Patient.identifier.value with a Universally Unique Identifier, including the urn:uuid: prefix. In this case, the corresponding value for Patient.identifier.system SHALL be urn:ietf:rfc:3986. The UUID SHOULD be persisted within the FHIR resource so that subsequent accesses return the same identifier, but it is not REQUIRED in environments where doing so is not possible.

When multiple Patient Resources are used to represent the same Patient, Patient.link SHALL be used to describe the relationship between the resources.

When returning Patient Resources, the Patient Demographics SHALL ensure that:

  • No more that one Patient Resource referencing a Patient Identity contains active=true
  • When returning multiple Patient Resources for the same Patient, Patient.link SHALL be used to describe the relationship between each Patient Resource
  • When one Patient Resource has become subsumed by another, the subsumed Patient SHALL use Patient.link to point at the surviving Patinet Resource and Patient.link.type SHALL be replaced-by.

Patient Demographics Consumers SHOULD be able to traverse Patient.link and use Patient.active to determine if a given Patient is currently active in the system.

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from Patient

NameFlagsCard.TypeDescription & Constraintsdoco
.. Patient C 0..* Patient Information about an individual or animal receiving health care services
iti-pdqm-linkstatus: If Patient.link is present, then Patient.active SHALL be present
... implicitRules 0..0
... Slices for extension 0..* Extension Extension
Slice: Unordered, Open by value:url
.... MothersMaidenName 0..1 string Mother's Maiden name
URL: http://hl7.org/fhir/StructureDefinition/patient-mothersMaidenName
... modifierExtension 0..0
... identifier 1..* Identifier An identifier for this patient
.... system 1..1 uri Assigning Authority ID or other identifiation namespace
.... value 1..1 string The value that is unique
... active SC 0..1 boolean Whether this patient's record is in active use
... name SC 0..* HumanName A name associated with the patient
iti-pdqm-patname: Either Patient.name.given and/or Patient.name.family and/or Patient.name.text SHALL be present or a Data Absent Reason Extension SHALL be present.
... telecom S 0..* ContactPoint A contact detail for the individual
... birthDate S 0..1 date The date of birth for the individual
... address S 0..* Address An address for the individual
... link SC 0..* BackboneElement Link to another patient resource that concerns the same actual person
.... type 1..1 code replaced-by | replaces | refer | seealso

doco Documentation for this format

Constraints

IdGradePath(s)DetailsRequirements
iti-pdqm-linkstatuserrorPatientIf Patient.link is present, then Patient.active SHALL be present
: link.exists() implies active.exists()
iti-pdqm-patnameerrorPatient.nameEither Patient.name.given and/or Patient.name.family and/or Patient.name.text SHALL be present or a Data Absent Reason Extension SHALL be present.
: (family.exists() or given.exists() or text.exists()) xor extension.where(url='http://hl7.org/fhir/StructureDefinition/data-absent-reason').exists()

 

Other representations of profile: CSV, Excel, Schematron