Business Context Index > Business Rules
Business Rules
Data Contribution Business Rules
| Business Rules# | Business Rule Description | FHIR® field /JWT token |
|---|---|---|
| BR-C-100 | The Data Contribution API must support FHIR R4 specifications. | |
| BR-C-101 | DHDR must validate received data against the Provincial Client Registry (PCR) and the Provincial Provider Registry (PPR). | patient, practitioner (prescriber), practitioner (dispense) and organization (pharmacy). |
| BR-C-102 | The patient's date of birth received during data intake must match the date of birth in the PCR. | patient.birthDate |
| BR-C-103 | During data intake DHDR shall augment drug information with information from the Health Canada Drug Product Database the Licensed Natural Health Products Database, and the Canada Health Infoway Canadian Clinical Drug Data Set. | medication |
| BR-C-104 | The patient identifier shall be either an Ontario health card number or a Medical Record Number (MRN) issued by a hospital or community pharmacy. | |
| BR-C-105 | Patients that are not found in the PCR will be contributed to PCR. | patient |
| BR-C-106 | The monitored drug indicator field will be set to true during intake processing if DIN of submitted drug has a CDSA (Canada Drug and Substances Act) schedule in the Health Canada Drug Product Database. | medication.extension.monitoredDrugIndicator |
| BR-C-107 | The whenPrepared and whenHandedOver filelds cannot be greater than the date the data is submitted. | whenPrepared, whenHandedOver |
| BR-C-108 | Data structural and conformance validations shall be done during initial data intake. Further data validations shall be done during processing of dispense and administration record submissions. | medicationDispense medicationAdministration |
Data Query Business Rules
| Business Rules# | Business Rule Description | FHIR® field /JWT token |
|---|---|---|
| BR-Q-101 | GET query should support search by mandatory patient identity parameter of Patient Identifier (health card number or MRN). | patient.identifier |
| BR-Q-102 | The patient information provided in the query must be accurate according to the most recent Ontario health card number or MRN. | patient.identifier |
| BR-Q-103 | Optional search parameter Dispensed Date should be supported if provided by the PoS application. The dispensed date should allow for a date range (FROM date and TO date) or block of time (e.g., last 30 days, last 60 days). If Dispensed Date is not provided by the PoS application, the DHDR response shall provide the records for the last 120 days for Community Pharmacy Dispensed information query and for the last 14 days for Hospital Administration medication query. |
Whenprepared |
| BR-Q-104 | When using End Date, End Date should be greater than the Start Date and should follow the equivalent parameter as in Start Date. | Whenprepare |
| BR-Q-105 | The DHDR PoS API shall support all of the optional search parameters as per current FHIR IG. | All parameters |
| BR-Q-106 | Any parameters chosen in the filtering criteria should not have a blank value. | All parameters |
| BR-Q-107 | The DHDR PoS API shall support READ requests based on MedicationDispense ID and MedicationAdminstration ID. | MedicationDispense ID,MedicationAdminstration ID |
| BR-Q-108 | If no DHDR data falls within the parameters of the request, DHDR must return appropriate notification in the query response. | OperationOutcome |
| BR-Q-109 | All of the available DHDR data elements as per the current FHIR specification should be returned in response to the PoS application query. | |
| BR-Q-110 | DHDR must validate received data against the Provincial Client Registry (PCR) and the Provincial Provider Registry (PPR). | patient, practitioner (prescriber), practitioner (dispense) and organization (pharmacy). |
| BR-Q-111 | Where query is made against patient with active Consent Directive DHDR must return response "Access to Drug and Pharmacy Service Information has been blocked by the Patient". | OperationOutcome |
| BR-Q-112 | Where query is made against Temporary Consent Override DHDR must return response “information unblocked” to all users at the organization for the four-hour duration. | |
| BR-Q-113 | When searching the DHDR, if the same record/event is found in community pharmacy dispensed data and HNS data, DHDR returns the community pharmacy dispensed record only. |
Query Parameters Data
The following table summarizes the mandatory and optional parameters for the query
Mandatory Parameters:
| Data Element | Definition | Example |
|---|---|---|
| Patient Identifier | Ontario health card number (HCN) and Medical Record Number (e.g. issued by hospital or community pharmacy) are allowed as an ID parameter in the current release. Note: HCN version is not supported. DHDR uses HCN for unique identification of a patient while a version number is usually used for verification of the provincial coverage eligibility, which is out of scope for DHDR. |
3821694372 |
| Composition Type | This parameter specifies the type of document | http://loinc.org|29550-1 http://loinc.org|80565-5 |
Optional Parameter:
| Data Element | Definition | Example |
|---|---|---|
| whenprepared | This parameter contains the dispensed date of the substance. Note: If there is no lower limit in the search request, the server will use the default configuration value of 120 days for community pharmacy dispensed information. |
gt2015-02-24 |
| Gender | This parameter should contain the sex at birth as noted on the Ontario health card number | male or female |
| Birth Date | This parameter should contain the date of birth of the patient as on the Ontario health card number | 1929-11-29 |
| effective-time | This parameter contains the administration time of the medication. Note: If there is no lower limit in the search request, the server will use the default configuration value of 120 days for hospital administration medication query. |
2015-01-15T04:30:00+01:00 |