Must Support Definitions

In the context of the Longitudinal Record Access (LRA) Implementation Guide, Must Support elements are defined to ensure that data critical to the functioning of the system and the provincial use cases are adequately handled by both sender and receiver systems. The following outlines the expectations for implementers interacting with Must Support data elements:

For Implementers Sending LRA Content:

  • Senders SHALL demonstrate that the system can produce a value for the Must Support element.
  • Senders SHALL ensure that the system can send or relay the data if available and appropriate (relevant to the current clinical context or the LRA data exchange).
  • For elements not marked as Must Support: Senders MAY still populate these elements when applicable, but this IG does not impose strict requirements. The decision to include non-Must Support elements or extensions will depend on provincial use cases and requirements, allowing flexibility for implementers to adopt these elements as needed.
  • Note: If an element is mandatory but not marked as Must Support, a fixed value can be sent without the expectation that the system must generate or populate that value.

For Implementers Receiving LRA Content:

  • Receivers SHALL be capable of processing resource instances containing Must Support data elements without generating errors or causing the application to fail.
  • Receivers SHOULD display Must Support data elements for human use, or process them (e.g., store or use them for other purposes).
  • Receivers SHALL be able to process resource instances containing Must Support elements that assert missing information (e.g., data that is not available or not present).
  • For elements not marked as Must Support: Receivers MAY accept and process these elements without errors, even if they are not required to display or fully process them. This ensures robust handling of patient data in the LRA context.
  • Note: If an element is mandatory but not marked as Must Support, the receiving system is not expected to process, display, or store that element. This definition provides flexibility while ensuring that key data elements are handled appropriately across provincial systems, maintaining alignment with the LRA use cases and operational needs.

Important Note: These are the base expectations of the LRA Implementation Guide. However, please be aware that there may be additional requirements imposed by the source systems integrated with the LRA platform. It is important to ensure that the system or implementation is compliant with the specific expectations of these source systems, as they may define further rules or constraints beyond what is outlined in this guide.