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

Jurisdictional Usage Notes

.id

  • Ontario Usage Notes:

    • 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.
  • Alberta Usage Notes

    • 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.profile

  • Ontario Usage Notes:
    • populate with a fixed value: http://ontariohealth.ca/fhir/StructureDefinition/ca-on-ps-profile-patient|0.12.0

.meta.versionId

  • Ontario Usage Notes:
    • 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

text

  • Alberta Usage Notes:
    • Patient records sent in a PS-AB Bundle SHALL NOT contain any of the following details: .text
    • 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.

extension:individual-recordedSexOrGender

  • Alberta Usage Notes:

    • SHALL always be populated
    • .value SHALL always be populated and SHALL use code from AdministrativeGender_AB value set AdministrativeGender_AB
  • British Columbia Usage Notes: - Comments: In BC, the EMPI allows for a gender code of 'X'. This will be a dropdown field.

extension:patient-interpreterRequired

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

.identifier

  • Ontario Usage Notes:

    • 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
  • Alberta Usage Notes:

    • 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 Patient Identifier Naming System, 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
  • British Columbia Usage Notes:

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

active

  • Alberta Usage Notes:
    • Patient records sent in a PS-AB Bundle SHALL NOT contain any of the following details: .text
    • 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.

.name

  • Ontario Usage Notes:

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

    • 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
  • British Columbia Usage Notes:

    • 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

  • Ontario Usage Notes:

    • SHOULD contain both a telephone number and email address
  • Alberta Usage Notes:

    • 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
  • British Columbia Usage Notes:

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

.gender

  • Ontario Usage Notes:

    • SHALL contain the patient's gender for administrative purposes
  • Alberta Usage Notes:

    • 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
  • British Columbia Usage Notes:

    • Comments: Gender is optional in EMPI (cardinality is 0..1 but has expected implementation support. This will be a dropdown field.

.birthDate

  • Ontario Usage Notes:

    • SHALL contain the patient's date of birth
  • Alberta Usage Notes:

    • SHALL always be populated
  • British Columbia Usage Notes:

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

.address

  • Ontario Usage Notes:

    • SHOULD contain the patient's primary address(es)
  • Alberta Usage Notes:

    • SHOULD have at least one address
    • If address is provided:
      • use SHALL be assumed as "home" when not valued
      • type
        • SHALL be assumed as "both" (i.e., "physical" and "postal") when not valued
      • .line
      • SHALL have at least one
    • .city
      • SHALL always be populated
    • .state
    • .country
    • Patient records sent in a PS-AB Bundle SHALL NOT contain any of the following details: .address.text
    • 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.

.maritalStatus

  • Alberta Usage Notes:
    • Patient records sent in a PS-AB Bundle SHALL NOT contain any of the following details: .maritalStatus
    • 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.

.multipleBirth

  • Alberta Usage Notes:
    • Patient records sent in a PS-AB Bundle SHALL NOT contain any of the following details: .multipleBirth
    • 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.

.photo

  • Alberta Usage Notes:
    • Patient records sent in a PS-AB Bundle SHALL NOT contain any of the following details: .photo
    • 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.

.contact

  • Alberta Usage Notes:

    • Patient records sent in a PS-AB Bundle SHALL NOT contain any of the following contact details: .contact.gender, .contact.organization, .contact.period
    • 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.
  • British Columbia Usage Notes:

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

.communication

  • Alberta Usage Notes:

    • .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"
  • British Columbia Usage Notes:

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

.generalPractitioner

  • Ontario Usage Notes:

    • 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 Usage Notes:

    • Patient records sent in a PS-AB Bundle SHALL NOT contain any of the following details: .generalPractitioner
    • 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.
  • British Columbia Usage Notes:

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

.managingOrganization

  • Alberta Usage Notes:
    • Patient records sent in a PS-AB Bundle SHALL NOT contain any of the following details: .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.