Service Request
| Rule Number | Rule description | Semantic Common Data Model mapping | Use cases affected | In CACDI? |
| CC-BR-00201 | A referral must include a reason. | Service Request Reason Code | All Service request use cases | No |
| CC-BR-00202 | A referral must include identifying client information (e.g. DOB, address, full name etc.) | Patient.Location.Address | All Service request use cases | No |
| CC-BR-00203 | The referring provider must be different from the receiving provider. | Party Role--> Desired Performer, Clinical Information Life Cycle Event.Clinical Information Life Cycle Event Type Code is "request" and Clinical Information Life Cycle Event --> executed by -->Party Role | All Service request use cases | No |
| CC-BR-00204 | A referral must specify the referring provider. | Clinical Information Life Cycle Event.Clinical Information Life Cycle Event Type Code is "request" and Clinical Information Life Cycle Event --> executed by -->Party Role | All Service request use cases | No |
| CC-BR-00205 | A referral may include electronic and manual communication | Service Request Communication Method Code | All Service request use cases | No |
| CC-BR-00206 | Completed orders may be retroactively documented. | Not applicable | All Service request use cases | No |
| CC-BR-00207 | The service request code is mandatory when the request is not for a referral or consultation since the code may not be known | Service Request Code, Service Request Consultation or Referral Type Code | All Service request use cases | No |
Contact us
If you have questions about this initiative, would like to be added to our stakeholder notification list or would like to participate in our consultations, please email us.
How to cite:
Canadian Institute for Health Information. Service Request. Accessed November 02, 2026.
