Business Context Index > Business Rules
Business Rules
Data Contribution Business Rules
| ID | Description | Search Parameter/FHIR Field |
|---|---|---|
| 1 | The Data Contribution API must support FHIR R4 specifications. | |
| 2 | miCDR must validate received data against the Provincial Client Registry (PCR) and the Provincial Provider Registry (PPR). | |
| 3 | The patient's date of birth received during data intake must match the date of birth in the PCR. | |
| 4 | Every resource in the contribution payload must specify the method of processing (e.g. POST) | |
| 5 | Every MI transaction bundle must provide the patient, practitioner, and organization associated with the data. | |
| 6 | OCINet must check and ensure all MustSupport elements are populated if the associated data is available. | |
| 7 | Business identifiers (e.g. patient MRN, accession number) must provide type information that matches the system of the identifier | Identifier.type |
| 8 | MI report and imaging manifest submission must provide a reference of the order associated to it if available. |
Data Query Business Rules
| ID | Description | Search Parameter/FHIR Field |
|---|---|---|
| 1 | All miCDR FHIR search queries must include patient identifier which can be an HCN, MRN or ECID (Enterprise Client ID) | search parameter must contain patient.identifier |
| 1.1 | Patient identifier search parameter must include both system and value | identifier.system and identifier.value must be present |
| 2 | The patient information provided in the query must be accurate according to the most recent Ontario health card number or MRN. | patient.identifier |
| 3 | The FHIR API shall support all of the optional search parameters as per current FHIR IG. | All parameters |
| 4 | Any parameters chosen in the filtering criteria should not have a blank value. | All parameters |
| 5 | The FHIR API shall support READ requests based on MI imaging study, MI report, and MI order. | ImagingStudy.id, DiagnosticReport.id, ServiceRequest.id |
| 6 | When search query does not have start date, all applicable data before the end date is in scope. When no end date is provided, all applicable data after the start date is in scope. The most recent or current document is in scope if neither a start date nor an end date is provided. | |
| 7 | When a date or datetime search parameter is present, it should provide values precise to the second + time offset | |
| 8 | If no MI data falls within the parameters of the request, the API must return appropriate notification in the query response. | OperationOutcome |
| 9 | All of the available miCDR data elements as per the current FHIR specification should be returned in response to the query. | |
| 10 | The FHIR API must validate the data in the query parameter against the Provincial Client Registry (PCR) and the Provincial Provider Registry (PPR). | |
| 11 | Where query is made against patient with active Consent Directive, the API must return proper OperationOutcome in the response indicating blocked data due to consent directive. | |
| 12 | Where query is made against Temporary Consent Override, the API must return response “information unblocked” to all users at the organization for the eight hour duration. | |
| 13 | In the search query, if no lower limit is specified for Encounter date, document bundle time stamp, document reference start date, the system shall default the data out query search period to 120 days back from the current date. | Encounter.date.start, Bundle(document).timestamp |
| 14 | If no page size is specified in the search query, the default page size will be 50 records. The maximum number of records returned in a page is 100 | _count |
Patient Identification
Patient identifier is required to uniquely identify a patient. The submission shall provide organization issued medical record number (MRN) and should provide Ontario health card number when available.
Provider Identification
Practitioner identifier is required to uniquely identify a practitioner. The practitioner’s license number or registration number issued by the regulatory college shall be provided.
Organization Identification
Organization identifier is required to uniquely identify an organization. Organizations in MI are identified by UPIs assigned by OH.
Local Code System OIDs
Code System OIDs for locally defined codes (e.g., local medical imaging procedure codes used in ServiceRequest.code) submitted by each MI data contributor SHALL be the same as the local code system OIDs used by the same contributor for other Ontario provincial repositories, including OCRE and acCDR.