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

Known Issues & Future Development

This Implementation Guide is part of the PS-CA Specification, intended for review, socialization, and feedback. During development, several issues were detected that could not be resolved in time prior to publication; issues with multiple—but no "best"—solutions possible; and issues with conflicting guidance. Some of those issues are listed below. Open issues are those for which no decision has been made, are pending feedback, or, for which there is an outstanding action. Issues are marked as close when a decision has been made, or the issue resolved.

Feedback is requested on both open and closed issues. Instructions for feedback submission can be found at Specification Feedback.

Known Issues

  1. Validation Tooling - Expanding Value Sets / Intersectional Value Sets

    There are two tooling issues leading to IPS value sets not being expanded and validated against by current FHIR tools:

    1. The is a current limitation in Simplifier validation tooling to perform expansion and filter capabilities that are necessary for the validator to determine if a slice is met on loaded examples.
    2. More broadly, there is a known issue with the FHIR Validator Tooling/FHIR terminology server that the validator uses (tx.fhir.org) not supporting value sets that combine multiple value sets and/or apply filters as part of the sequence for defining the value set (an approach IPS uses for many of its value sets).
      • After this fix is applied, Implementers will be able to validate the examples including IPS value sets against the FHIR Validator GUI - IG Package is loaded and can be validated against by selecting "Options" and then choosing "https://packages.simplifier.net/ca.infoway.io.psca" from the dropdown of Implementation Guides.

  2. Referenced ValueSets and CodeSystems are not resolvable.

    Some referenced ValueSets are not available at their canonical URL; some (particularly Canada-specific) ValueSets are not on the terminology servers used in IG publication (i.e. tx.fhir.org). Some referenced ValueSets are not currently available as FHIR R4 and may require conversion before use. Primarily, these issues impact validation against Canada Health Infoway-hosted ValueSets during development of derived Implementation Guides. (This doesn't affect deployed systems, since, in that environment, instances will be validated against locally present value sets.) For several of these ValueSets, "stub" resources have been created to stand-in within this Implementation Guide for the unresolvable ValueSets.

    Current guidance is to manually download the referenced value sets from, for example, the Terminology Gateway. Investigation is needed to determine if the problem ValueSets can be made "resolvable" through Infoway, or if they can be added to the standard terminology servers.

  3. Must Support Relaxation

    Several elements flagged as Must Support in IPS-UV are not flagged in PS-CA due to feedback received about jurisdictional support. These elements are called out on relevant profile pages in this implementation guide. Feedback is requested about:

    • Whether it was appropriate to relax the Must Support requirement for these specific elements
    • Whether Must Support should be relaxed or added on additional elements

  4. IPS 2.0.0-Ballot Terminology Realignment

    As part of the IPS 2.0.0-Ballot release, in consultation with SNOMED International, there are several changes in terminology bindings (see https://jira.hl7.org/browse/FHIR-46365 for additional details).

    • SNOMED has codes for absent/unknown, so there is no longer a need for separate IPS absent/unknown codes
    • SNOMED IPS FreeSet is no longer identified as a separate/additional binding, as they are part of the full SNOMED CT.
      These changes have not been applied to PS-CA, and need to be assessed within the Canadian implementors landscape, in conjunction with ongoing efforts to stand up the Canadian Terminology Server. Additional details will follow in the next PS-CA release.

  5. Packaged Profiles do not include Snapshots

    Current tooling is unable to generate FHIR profile snapshots when creating packages for this project. If you wish to retrieve the snapshots for a particular profile, you can select the "Download snapshot as XML/JSON" option from the respective profile page within the Simplifier project (top-right corner of the project profile page, not the IG page)

  6. Examples files may have validation errors

    • Some validation tooling are indicating errors with the fullURL values currently in the examples. We are investigating this, and will provide updated examples in an updated release if necessary.

  7. Canonical URL mismatches identified as errors using IGPublisher

    • When using IGPublisher with the PS-CA FHIR profiles and valuesets, IGPublisher will identify errors with Canonical URLs not matching the resource URLs. This applies to includes extensions from PrescribeIT and from TerminologyGateway Stub ValueSets. IGPublisher expects all input conformance assets (profiles, valuesets, codesystems, extensions) to share the same base URL fhir.infoway-inforoute.ca/io/psca/.

Closed Issues

  1. AdditionalBinding Rendering

    This version introduces the AdditionalBinding Extension which has been utilized by IPS since the IPS 1.1.0 release to convey additional terminology that is relevant under certain contexts (e.g., proposed for use with countries that do not have SNOMED CT licensing, utilized heavily in legacy data, etc.). See Profiling Conventions and Approach.

    • This extension is applied to the binding element and renders in IGPublisher now renders in Simplifier.

  2. individual-RecordedSexOrGender Cross-Version Extension

    This version socializes the RecordedSexOrGender Extension. Previously, tooling required for it to be "re-published" in this guide to pre-adopt an extension published in R5. The HL7 Extensions Pack now includes both the R5 and R4 versions of this extension and dependencies have been updated accordingly.

Note: To view previously closed issues please review prior versions of the PS-CA. You may find the previous versions of the guide here.