Releases of the PS-CA Implementation Guide may be found on a table on the Home Page of this Project.


Superset Example

Additional information on this profile (including the JSON & XML structure and detailed element descriptions) can be found at package/structuredefinition-profile-patient-ca-ps.json

PS-CA Profile

idΣ0..1string
metaΣ0..1Meta
implicitRulesΣ ?!0..1uri
language0..1codeBinding
text0..1Narrative
contained0..*Resource
individual-recordedSexOrGenderI0..*Extension(Complex)
modifierExtension?! I0..*Extension
id0..1string
extensionI0..*Extension
useΣ ?!0..1codeBinding
typeΣ0..1CodeableConceptBinding
systemΣ1..1uri
valueΣ1..1string
periodΣ0..1Period
assignerΣ0..1Reference(Organization)
id0..1string
versionCodeI0..1Extension
useΣ ?!0..1codeBinding
typeΣ1..1CodeableConceptBindingFixed Value
systemΣ1..1uri
valueΣ1..1string
periodΣ0..1Period
assignerΣ0..1Reference(Organization)
id0..1string
extensionI0..*Extension
useΣ ?!0..1codeBinding
typeΣ1..1CodeableConceptBindingFixed Value
systemΣ1..1uri
valueΣ1..1string
periodΣ0..1Period
assignerΣ0..1Reference(Organization)
activeΣ ?!0..1boolean
id0..1string
extensionI0..*Extension
useΣ ?!0..1codeBinding
textS Σ0..1string
familyS Σ0..1string
givenS Σ0..*string
prefixΣ0..*string
suffixΣ0..*string
periodΣ0..1Period
telecomΣ0..*ContactPoint
genderS Σ0..1codeBinding
birthDateS Σ1..1date
deceasedBooleanboolean
deceasedDateTimedateTime
addressΣ0..*Address
maritalStatus0..1CodeableConceptBinding
multipleBirthBooleanboolean
multipleBirthIntegerinteger
photo0..*Attachment
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
relationship0..*CodeableConceptBinding
name0..1HumanName
telecom0..*ContactPoint
address0..1Address
gender0..1codeBinding
organizationI0..1Reference(Organization)
period0..1Period
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
language1..1CodeableConceptBinding
preferred0..1boolean
generalPractitioner0..*Reference(Organization | Practitioner | PractitionerRole)
managingOrganizationΣ0..1Reference(Organization)
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
otherΣ1..1Reference(Patient | RelatedPerson)
typeΣ1..1codeBinding

Extensions

This profile uses the following extensions:

Key Differences between the IPS-UV and PS-CA

Must Support Differences:

The following elements are considered Must Support in the IPS-UV specification that are relaxed in this version of the PS-CA profile:

  • Patient.telecom

  • Patient.address

  • Patient.generalPractitioner

    Note: Systems that support these elements are encouraged to send them in patient summaries

Cardinality Differences:

There are no cardinality differences between this profile and IPS-UV

Vocabulary Differences:

  • Patient.identifier
    • slices added for JPID & MRN identifier types anticipated to be used by early implementers

Other differences between the IPS and PS-CA Include:

  • Patient.name.text: comment added

Ontario Requirements

Profile Details

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

Simplifier Profile: Patient (PS-ON - Derived from PS-CA)

Usage Notes

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

.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.12.0

.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) or Practitioner (PS-ON) or Organization (PS-ON) profile. Other references may be sent as well, as long as at least one PractitionerRole (PS-ON) is included

Alberta Requirements

Profile Details

Canonical URL:https://www.alberta.ca/fhir/psab/StructureDefinition/PatientPSAB

Simplifier Profile:

Command 'link' could not render: Resource was not found for 'canonical=https://simplifier.net/alberta-patient-summary/patientpsab'

Restrictions

Alberta Patient Summary (PS-AB) employs a set of constraints that prevent patient summaries created in Alberta to include certain elements from Patient.

Patient records sent in a PS-AB Bundle SHALL NOT contain any of the following Patient details:

  • .text
  • .active
  • .address.text
  • .maritalStatus
  • .multipleBirth
  • .photo
  • .contact.gender
  • .contact.organization
  • .contact.period
  • .generalPractitioner
  • .managingOrganization

These elements are restricted based on current privacy requirements that require data that is collected, used or disclosed be limited to only the amount of health information that is essential to enable the custodian or the recipient of the information to carry out the intended purpose.

Usage Notes

The Patient Resource is used to provide information about the person who is the subject of a patient summary.

.id

  • identifier for the Patient resource, unique within the submitted Bundle
  • if a persistent identity for the resource is not available to use when constructing a Bundle for transmission, a UUID SHOULD be used in this element (with a corresponding value in Bundle.entry.fullUrl)

.meta

  • metadata about the patient resource, relevant to the submission or data exchange

.identifier

  • SHALL have one identifier
  • Alberta Unique Lifetime Identifier (ULI) SHOULD be provided when available
  • the patient's health care number from another jurisdiction SHALL be provided if the patient is from outside the province and does not have a ULI
  • .type
    • the type of patient identifier, to ensure correct interpretation and usage of the identifier value
    • SHALL always be populated
  • .system
    • the namespace / naming system used for this patient identifier
    • SHALL always be populated
    • SHALL use URI from
      Command 'pagelink' could not render: Page not found.
      , and SHALL use the associated identifier type code for .type, and MAY use the associated assigning authority name for assigner.display
  • .assigner
    • organization that issued/manages the identifier
  • .value
    • a unique identifier assigned to the individual patient by a recognized legal entity or authority
    • SHALL always be populated
    • maximum character length SHALL be 20

.name

  • SHALL have at least one name
  • at least one name SHALL match the registered name in the Alberta provincial insurance
  • .text
  • the patient's full name in the format that would be used for communications or correspondence with the patient
    • SHALL alway be populated
    • MAY include a preferred name in addition to or instead of a legal given name
    • maximum character length SHALL be 200
  • .family
    • the legal surname or family name of the patient
    • SHALL always be populated
  • .given
    • the legal first name or given name of the patient

.telecom

  • preferred telephone number for the subject patient. Email address is NOT collected for communications purposes as email is not an acceptable method for communicating confidential / clinical information
  • SHALL have at least one .telecom:Phoneenforced by an invariant in Bundle resource

.gender

  • the patient's gender used for administrative purposes (e.g. as registration for healthcare insurance plan membership, etc.)
  • SHALL always be set to "other" and the actual value SHALL be placed in .individual-recordedSexOrGender extension

.birthDate

  • the birth date of the patient
  • SHALL always be populated

.address

  • SHOULD have at least one address
  • If address is provided:
    • use SHALL be assumed as "home" when not valued
    • type
      • speciifes the type of address being submitted, to distinguish between mailing address, physical addresses, or other allowed types
      • SHALL be assumed as "both" (i.e., "physical" and "postal") when not valued
    • .line
      • specifies the unique location of the physical or mailing address within the city or municipality
      • physical address line includes street or house number, unit or apartment number, and/or street direction as applicable
      • SHALL have at least one
    • .city
      • the name of the city, town, hamlet, village or other delivery centre
      • SHALL always be populated
    • .state
    • .postalCode
      • the postal code, zip code or equivalenta designation associated to the patient's address
      • SHALL always be populated
    • .country

.contact

  • a contact party (e.g. guardian, partner, friend) for the patient
  • .relationship
    • the nature of the relationship between the patient and the contact person
  • .name
    • the full name of the patient's contact person
  • .address
    • the address of the patient's contact, when different from the patient's address

.communication

  • .language
    • a language in which the patient is comfortable communicating about their health
  • .language.coding.code
    • if populated:SHALL use ISO 639-3. Codes are available from SIL International (registration autority for ISO 639-3)
  • .language.coding.system
    • if populated:SHALL use "http://terminology.hl7.org/CodeSystem/iso639-3"

Extensions

.individual-recordedSexOrGender

  • administrative gender used for verifying patient identity
  • SHALL always be populated
  • .value SHALL always be populated and SHALL use code from AdministrativeGender_AB value set AdministrativeGender_AB

British Columbia Requirements

Profile Details

Canonical URL:http://fhir.infoway-inforoute.ca/io/psca/StructureDefinition/patient-ca-ps

Simplifier Profile: BC uses the PS-CA profile directly and does not deploy a distinct conformance profile to test the usage notes / comments below

Usage Notes

identifier

  • Comments: EMPI uses the PHN (BC Personal Health Number). EMPI does not explicitly define MRN. If it is considered as other identifiers, then there is a discrepancy around type. PS-CA requires type for MRN, but IdentifierCABaseline marked it as optional. Infoway suggests that if an identifier is specifically mentioned type as MRN, then it should be mapped to the MRN identifier with the fixed type value of MR. Otherwise, it should be mapped as all slices.

name

  • Comments: EMPI's Patient Profile, this element is (0..) (EMPI's (S) indicates it must be supported.) and according to EMPI team, it will always be provided, but PS-CA needs at least one name(1..). We suggest adhering to the precedent set by PS-CA and treating this as an obligatory requirement (filling in the relevant fields wherever possible and marking them with 'unknown' or a comparable designation to indicate the absence of information in the IG). According to Canada Health Infoway's FHIR SME suggestion, while it may appear optional in BC-EMPI or baseline, a restriction (through invariant) mandates the validator to generate an error message if the given or family name of a patient remains unpopulated.

telecom

  • Comments: There are three contact fields: Cell Phone, Home Phone, and Email.

gender

  • Comments: Gender is required by PS-CA while it is marked as optional in EMPI (cardinality is 0..1). Though there is a tag (S) which binds the implementation to support. This will be a dropdown field.

birthdate

  • Comments: Birthdate is required on PS-CA but optional in EMPI. EMPI tagged (S) as must be supported. We propose filling the birthdate field to the fullest extent possible. This will ensure that PS-BC aligns with the patient profiles specified by PS-CA, International Patient Summary (IPS), and other jurisdictions. Per the FHIR specification, "For this element, it is expected to provide an estimated year as a guess, at least if the real DOB is unknown." If the estimation is impossible, a similar course of action (as name) can be pursued, such as designating a date like '1800-01-01' and clarifying this in the IG. Infoway suggests upon a cursory review of the patient summary specifications, including PS-CA, PS-ON, and IPS, among others, it appears that all of them classify this element as mandatory.

communication.language

  • Comments: This will be a dropdown field with different languages of choice.

generalPractitioner

  • Comments: This will be a checkbox field (Yes/No) representing the Most Responsible Provider (MRP) to be displayed in the Provider/Source section in the PS Form UI.

contact.relationship

  • Comments: This will be a dropdown field with different relationships of choice.

Extensions

extension:individual-recordedSexOrGender

  • Comments: In BC, the EMPI allows for a gender code of 'X'. This will be a dropdown field.

extension:patient-interpreterRequired

  • Comments: This extension will be represented as a Checkbox Field (Yes/No) on the front-end Patient Summary UI.