Business Context Index > Business Model

Business Model

This implementation guide is to support OCINet's data migration and ongoing contribution to 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
  • Uses a hybrid model of local and distributed clinical repositories
  • Long term goal is to collect once, reuse many times

miCDR FHIR API for this implementation guide will support an asynchronous data flow for OCINet's data contribution. 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.

This diagram shows the data flow between entities in miCDR.

MI-async

Actors

There are three main actors involved in miCDR data flow:

  • Data Contributors: Health Information Custodians (HICs) that provide patient care and contribute medical imaging (MI) data to regional Diagnostic Imaging Repositories (DIRs). OCINet facilitates the contribution of this data to miCDR on behalf of HICs.

  • 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.