Profiles & Operations > Operation: Submit SERIS Schedule Information
OR Schedule Introduction & Overview
The SERIS OR Schedule captures the planned start and stop times for each OR in use and any adjustments for room openings and closures throughout a planning horizon. In Ontario, there are multiple scheduling methods that are utilized depending on facility operating procedures:
Open scheduling: In this method, the schedule does not reserve slots for a specialist or service in-advance. The slots might be booked chronologically on a first-come, first-serve basis.
Block scheduling: Pre-allocated time slots are used to create the schedule for a defined time frame. These blocks are assigned to the surgery teams and/or services.
Modified Block scheduling: A combination of open and block scheduling approach. Blocks are assigned by the block scheduling method and then distribution of the unused blocks is organized for additional surgical specialties with the open scheduling method.
The SERIS system and FHIR Implementation Guide supports any of the scheduling methods above.
Any changes to the OR Schedule shall be relayed in near real-time upon modifications in the source system.
Operation
The Submit SETP Message operation allows for the submission of all SETP OR Schedule messages.
High level Requirements
| Requirement No. | Description |
|---|---|
| 1 | Ability for A Designated OR Personnel to create a new OR Schedule for a shift. |
| 2 | Ability for a Designated OR Personnel to update an OR Schedule by adding a block for a specific service or Surgeon(s). |
| 3 | Ability for a Designated OR Personnel to update an OR Schedule by removing the block Surgeon(s) or Service. |
| 4 | Ability for a Designated OR Personnel to update the OR Schedule by updating the block Surgeon(s) or Service. |
| 5 | Ability for a Designated OR Personnel to update the OR Schedule by updating the Slot metadata (block information, status, etc..). |
| 6 | Ability for a Designated OR Personnel to update future OR Schedule shift availability hours (shift operating hours). |
| 7 | Ability for a Designated OR Personnel to update the OR Schedule to modify the duration of available and unavailable time slots. |
| 8 | Ability for a Designated OR Personnel to update the OR Schedule to close an OR temporarily. |
| 9 | Ability for a Designated OR Personnel to update the OR Schedule to close an OR permanently. |
| 10 | Ability for a Designated OR Personnel to update the Planning Horizon. |
| 11 | Ability for a Designated OR Personnel to update the OR details (Name, Status). |
| 12 | Ability for a Designated OR Personnel to correct OR schedule data entered in error. |
OR Schedule Model Diagram
OR Schedule Recommened Worlflow
1. Submit Schedule Details
This section describes the HIS facilities able to submit Operating Room (OR) Schedule details to the SETP respository.
Sequence Diagram
HTTP Request
| API URL | Action | Payload |
|---|---|---|
| [base]/Schedule | Post | Create Schedule |
Sample Payload
Operation Invocation
POST [base]/Schedule/
Response
- OperationOutcome
Example Message
HTTP Method:
POST
Headers:
Content-Type: application/fhir+json
Address:
[base]/Schedule/
Message body:
Link to submit Schedule Resource
2. Submit Slot Details
This section describes the HIS facilities able to submit Operating Room (OR) Slot details to the SETP respository.
Sequence Diagram
HTTP Request
| API URL | Action | Payload |
|---|---|---|
| [base]/Slot | Post | Create Slot |
Sample Payload
Operation Invocation
POST [base]/Slot/
Response
- OperationOutcome
Example Message
HTTP Method:
POST
Headers:
Content-Type: application/fhir+json
Address:
[base]/Slot/
Message body:
3. Submit Location Details
This section describes the HIS facilities able to submit Operating Room (OR) Location details. Location here is a physical place where a surgical procedure can be performed.
Sequence Diagram
HTTP Request
| API URL | Action | Payload |
|---|---|---|
| [base]/Location | Post | Create Location |
Sample Payload
Operation Invocation
POST [base]/Location/
Response
- OperationOutcome
Example Message
HTTP Method:
POST
Headers:
Content-Type: application/fhir+json
Address:
[base]/Location/
Message body:
Link to submit Location Resource
Expected Behaviour
See Response Handling page for a complete listing of response codes.
| Case | Scenario Description | HTTP Status Code | Response Payload |
|---|---|---|---|
| 1 | A valid OR resource is submitted, accepted, and published to the repository | HTTP 201 (Created) | OperationOutcome |
| 2 | An update to an existing OR resource is submitted | HTTP 200 (OK) | OperationOutcome |
| 3 | The submitted OR resource cannot be validated as it does not conform to the specification | HTTP 400 (Bad Request) | Returns an OperationOutcome resource indicating an issue. The client must fix the request and try again. |
| 4 | POST operation contains incorrect header value for "Content-Type" - should be "application/fhir+json" | HTTP 422 (Bad Request) | Returns an OperationOutcome resource indicating an unprocessable content. |
| 5 | OR Case Submit API validates the request but cannot return a valid response due to internal issues. | HTTP 500 (Internal Server Error) | Returns an OperationOutcome resource indicating an issue. |