Ontario Health
Ontario Clinical Report Exchange Implementation Guide v1.0.0 - Trial Use
fhir-logo
  • Index
  • Home
    • Home
    • Introduction
    • Relationship to Other Specifications
    • Scope
    • Glossary
  • Business Context
    • Business Context
    • Business Model
    • Business Data
    • Use Cases
    • Business Rules
  • Technical Context
    • Technical Context
    • Implementer Responsibility
    • Conformance Rules
    • Connectivity Summary
  • FHIR Artifacts
    • FHIR Artifacts
    • Interactions
    • Profiles
    • Extensions
    • Terminology
    • System URIs
    • Examples
    • Capability Statement
    • Response Handling
    • Downloads
  • Change Log
    • Change Log
    • Known Issues & Future Developments
    • Revision History
    1. Index
    2. Business Context
    3. Use Cases

For a full list of available versions, see the Directory of published versions

2.3. Use Cases

The use cases below provide a basic illustration of how actors interact with the OCRE.

2.3.1. Actors

Participant Type Description
Data Contributor Organization Health Information Custodian (HIC) contributing clinical reports and/or medical imaging reports to OCRE and operator of Data Contributor System.
Data Contributor System System A system, e.g. a hospital or ICHSC, that is used by HICs to contribute clinical reports and/or medical imaging reports to OCRE.
OCRE Solution System OCRE receives clinical reports and medical imaging reports from Data Contributors, validates and publishes these reports to OH Pub/Sub services.
OH Pub/Sub services System A system designed to notify interested systems (subscribers) in near real-time whenever specific events related to FHIR resources occur in another system (the publisher).
Point of service system System A software application used by health information custodians for viewing or managing personal health information (PHI). Common PoS systems include, but are not limited to, provincial clinical viewers, health information system (HIS) and primary care electronic medical records (EMRs). For OCRE, the point of service system receives the report from OCRE solution.

2.3.2. UC-C1 – Data Contributor System submits a medical imaging report (Transaction Bundle) to OCRE

Data Contributor System submits a medical imaging report to OCRE and report passes all FHIR profile and terminology validations.

Steps:

  1. Data Contributor System submits a medical imaging report to OCRE.
  2. Report is processed and passes all validation steps.
  3. OCRE publishes this report to OH Pub/Sub services.
  4. OH Pub/Sub services notify point of service system that subscribed to this report type & patient or are recipients of this report
  5. Point of service system receives a medical imaging report from OH Pub/Sub services.

Alternate Workflows:

  1. Data Contributor System submits a medical imaging report to OCRE and it fails profile validation with Error annotation.
    1. Data Contributor System submits a medical imaging report to OCRE.
    2. Report is processed and fails profile validation with Error annotation.
    3. Notification is generated and sent to Data Contributor.
    4. Report is not published to OH Pub/Sub services and is unavailable for Point of service system.
  2. Data Contributor System submits a medical imaging report to OCRE and it fails profile validation with Warning and/or Information annotation (no Error).
    1. Data Contributor System submits a medical imaging report to OCRE.
    2. Report is processed and fails profile validation with Warning and/or Information annotation (no Error).
    3. Notification is generated and sent to Data Contributor.
    4. Report is published to OH Pub/Sub services which sents a notification to point of service system.
    5. Point of service system receives a medical imaging report from OH Pub/Sub services.

2.3.3. UC-C2 – Data Contributor System submits a clinical report (Document Bundle) to OCRE

Data Contributor System submits a clinical report to OCRE and it passes all FHIR profile and terminology validations.

Steps:

  1. Data Contributor System submits a clinical report to OCRE.
  2. clinical report is processed and passes all validation steps.
  3. OCRE publishes this clinical report to OH Pub/Sub services.
  4. Pub/Sub notifies point of service system that subscribed to this document type & patient or are recipients of this document
  5. Point of service system receives a clinical report from OH Pub/Sub services.

Alternate Workflows:

  1. Data Contributor System submits a clinical report to OCRE and it fails profile validation with Error annotation.
    1. Data Contributor System submits a clinical report to OCRE.
    2. Clinical report is processed and fails profile validation with Error annotation.
    3. Notification is generated and sent to Data Contributor.
    4. Clinical report is not published to OH Pub/Sub services and is unavailable for point of service systems.
  2. Data Contributor System submits a clinical report to OCRE and it fails profile validation with Warning and/or Information annotation (no Error).
    1. Data Contributor System submits a clinical report to OCRE.
    2. Clinical report is processed and fails profile validation with Warning and/or Information annotation (no Error).
    3. Notification is generated and sent to Data Contributor.
    4. Clinical report is published to OH Pub/Sub services which sents a notification to Point of service system.
    5. Point of service system receives a clinical report from OH Pub/Sub services.
Version: 1.0.0 FHIR Version: R4.0.1

Powered by SIMPLIFIER.NET

HL7® and FHIR® are the registered trademarks of Health Level Seven International