For a full list of available versions, see the Directory of published versions
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:
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.
This diagram shows the data flow supported by miCDR.
Actors There are three main actors involved in miCDR data flow: