For a full list of available versions, see the Directory of published versions
Note to Authors:
Create a dedicated operation page if there is a need to describe business context, usage, or constraints.
Otherwise, link directly to the OperationDefinition from the Operations Index page.
Canonical URL: http://ontariohealth.ca/fhir/OperationDefinition/operation-id
Note to Authors:
Explain when and how this operation should be invoked.
Include example scenarios and business rules.
Clarify if the operation is server-side only, client-initiated, or both.
Example usage text:
This operation is used by clients to request a patient’s complete summary in a single Bundle. It may be invoked at either the system or patient level.
Note to Authors:
List input and output parameters clearly.
Distinguish between mandatory and optional parameters.
If parameters reference profiles or value sets, provide links.
Example table:
| Use | Name | Cardinality | Type | Description |
|---|---|---|---|---|
| IN | patient |
1..1 | Reference(Patient) | Identifies the patient whose data is being requested. |
| OUT | since |
0..1 | dateTime | Limits returned results to those after the given date. |
Note to Authors:
Describe the expected return (e.g., Bundle, OperationOutcome).
Provide guidance for handling errors.
Note to Authors:
Capture any additional rules or restrictions (e.g., authentication, authorization, throttling).
If no additional notes, state “No additional business-specific constraints.”