visit the hl7 website
Ontario Medical Imaging HL7® FHIR® Implementation Guide v1.0.0-Ballot
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. Business Model

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

2.1. Business Model


2.1.1. Context

This implementation guide is intended to support the contribution and consumption of MI data from Ontario miCDR. miCDR platform will use FHIR standard with the following purposes:

  • FHIR based platform (R4 and higher)
  • Exposes a patient’s longitudinal record through a set of FHIR APIs (both provider and patient access)
  • Abstracts the underlying clinical repositories
  • Long term goal is to collect once, reuse many times

miCDR solution for this implementation guide will support synchronous and asynchronous data flow for Hospitals and ICHSCs data contribution. RESTful APIs are by default synchronous. This means when data contributors submit data, they shall wait for the response from miCDR. Under asynchronous flow, when data is sent, the FHIR resources will not be created right away, instead the interface will return an HTTP code 202 that indicates it intends to process it. The request is placed in an internal queue for processing. Contributor does not have to wait for further response before sending another request. When the resources are later processed and stored in miCDR, an asynchronous response will be sent to the contributor.


2.1.2. Model

This diagram shows the data flow supported by miCDR.



-->

Actors There are three main actors involved in miCDR data flow:

  • Data Contributors: Health Information Custodians (HICs) that provide patient care and contribute their medical imaging (MI) data directly to miCDR using FHIR-based interfaces. Examples include hospitals and ICHSCs.
  • Data Consumers: For this implementation guide, the consumers are the provincial viewers and other point of service systems that provide users access to miCDR data through miCDR FHIR interface..
  • miCDR: The miCDR Repository is an Ontario Health digital health asset that supports sharing of patient's medical imaging data among health care providers. The repository provides APIs to be used by authorized systems to submit, retrieve miCDR data to/from the repository.
Version: v1.0.0-ballot FHIR Version: R4.0.1

Powered by SIMPLIFIER.NET

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