Release notes

Profile: Patient

  • Client name validation updated — all characters now permitted except illegal characters (control/non-printable characters and system-breaking characters such as <, >, {, }, |, ^, ~, `)

  • Applies to Client First Name, Client Middle Name, and Client Last Name or Single Name

  • Spaces and special characters are now accepted to support real-world naming variations

  • Postal Code validation enforced — values must follow the format X1X1X1 (no spaces or special characters) for both Client Postal Code and HSP Site Postal Code

  • Validation error now returned when a Postal Code containing special characters or invalid formats is submitted

Profile: EpisodeOfCare

  • Bundle rejection corrected — bundles with Service Enrollment Date present and Health Service Status set to Planned are now accepted

  • Date validation corrected — Service Referral Date can be present without Service First Contact Date; date comparisons enforced only when both values are present

  • Validation corrected — error no longer triggered when Service Enrollment Date is present but Service Initiation Date extension is absent

  • Health Service Status of Active is now accepted when only one of Service Enrollment Date or Service Initiation Date is provided

Profile: HealthcareService

  • Postal Code validation enforced — values must follow the format X1X1X1 (no spaces or special characters) for both Client Postal Code and HSP Site Postal Code

  • Validation error now returned when a Postal Code containing special characters or invalid formats is submitted

Profile: QuestionnaireResponse (Problem Gambling)

  • Conditional logic enforced for gambling questionnaire fields (Q2–Q15)

  • Q2 through Q15 are now only accepted when Q1 (Reason for Seeking Help with Gambling Behaviour) contains option '2 – Own gambling problem' or '3 – Both'

  • Interim requirement — all three Percentage of Time Spent Gambling by Jurisdiction fields must be submitted even when one value is 100%; remaining fields must be submitted as 0%

  • Fields: In Ontario / In Another Province / Outside of Canada — values must sum to 100%

Note: A fix to automate the 0% requirement for remaining jurisdiction fields is targeted for Snapshot 15.

Info
Created:
Organization Canadian FHIR Registry

Canonical claims

This package contains canonicals that conflict with another package or project.

There are no valid canonical claims defined.
>
To install the command line tool, download Firely Terminal
>
For using npm with FHIR packages, read more here
Name Version Release date
hl7.fhir.r4.core 4.0.1