Profiles & Operations Index > Profile: Patient

Profile: Patient

Canonical URL:http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ps-profile-patient

Simplifier project page: Patient (PS-ON)

Derived from: Patient (R4)

Formal Views of Profile Content

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

Hybrid View

activeΣ ?!0..1boolean
telecomS Σ I0..*ContactPoint
genderS Σ1..1codeBinding
birthDateS Σ1..1date
addressS Σ I0..*Address
maritalStatus0..1CodeableConceptBinding
photoI0..*Attachment
managingOrganizationΣ I0..1Reference(Organization)

Usage

The Patient Resource is used to provide information about the person who is the subject of a Patient Summary in its header.

Notes

.id

  • Definition: Logical id of this artifact
  • used to uniquely identify the resource
  • if a persistent identity for the resource is not available to use when constructing the composition Bundle, a UUID SHOULD be used in this element (with a corresponding value in Bundle.entry.fullUrl)
  • Where .id is populated with a persistent identifier, consumers SHALL NOT expect to be able to resolve the resource and SHALL always use the version of the resource contained in the Bundle to render the composition.

.meta.profile

  • used to declare conformance to this profile
  • populate with a fixed value: http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ps-profile-patient|0.9.1

.meta.versionId

  • SHALL be populated by the Patient Summary Repository server
  • consuming systems can expect this element to be populated when retrieving patient summary instances from the repository
  • source systems do not need to populate this element prior to submission

.identifier

  • business identifier(s) for the patient, multiple allowed
  • SHALL include at least one unique identifier
  • SHOULD include a jurisdictional health card number without a version code in JHN slice
  • MAY include other business identifiers, such as MRN or ECID

.name

  • SHALL contain the patient's full name
  • at least one of family or given is required; some patients may have only one name

.telecom

  • SHOULD contain both a telephone number and email address

.gender

  • SHALL contain the patient's gender for administrative purposes

.birthDate

  • SHALL contain the patient's date of birth

.address

  • SHOULD contain the patient's primary address(es)

.generalPractitioner

  • SHOULD be used to identify the Practitioner(s) that act as the patient's primary care health care practitioner
  • When present, .generalPractitioner.reference SHALL be populated with a reference to a Practitioner resource:
  • When present, .generalPractitioner.display SHOULD be populated with the Practitioner's full name
  • the referenced resource SHALL be included in the message as a Bundle.entry
  • When .generalPractitioner is used, there must be at least one referenced resource that conforms to the PractitionerRole (PS-ON) profile. Other references may be sent as well, as long as at least one PractitionerRole (PS-ON) is included