Care workflows
Connect the remote specialist with the local care team and agreed clinical context.
TeleICU
Identify participating facilities, critical-care beds and specialist coverage. Agree which organization owns care, which records remote staff may access and the escalation contacts for each site.
Link the person and encounter to the shared review context. Confirm available observations, notes and imaging sources; commission camera or device connections only within the agreed scope.
Let the authorized specialist review the case and document the assessment and recommendations. Name the bedside owner who receives and acts on the plan; remote advice does not silently transfer clinical responsibility.
Track the next review and handover responsibilities. Maintain contact and downtime procedures for unavailable video, incomplete source information or a case requiring direct escalation.
Your configuration
Use the registered details of your organization. Do not enter patient records here.
Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.
| Column | Required | Format | Example |
|---|---|---|---|
Registered organization namelegal_name | Yes | text | Example Healthcare Organization |
Commercial registration numberregistration_number | Yes | text | EXAMPLE-CR-001 |
Countrycountry | Yes | SA / AE / BH / KW / QA / OM / EG / OTHER | SA |
Tax registration numbervat_number | Optional | text | — |
Add every facility included in your subscription. These become real, separate facilities in your app.
Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.
Load / review first: Your organization
| Column | Required | Format | Example |
|---|---|---|---|
Facility namename | Yes | text | Example Facility |
Facility typetype | Yes | hospital / clinic / polyclinic / laboratory / other | clinic |
Facility licenselicense_number | Yes | text | EXAMPLE-LICENSE-001 |
Addressaddress | Yes | text | Example training address |
Phonephone | Yes | text | +966500000000 |
Time zonetimezone | Yes | Asia/Riyadh / Asia/Dubai / Asia/Qatar / Africa/Cairo / UTC | Asia/Riyadh |
Create departments, consultation rooms, wards and beds. You can add more inside your app.
Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.
Load / review first: Facilities
| Column | Required | Format | Example |
|---|---|---|---|
Facility number (starting at 1)facility | Yes | integer 1–1000 | 1 |
Department namename | Yes | text | Example Department |
Create departments, consultation rooms, wards and beds. You can add more inside your app.
Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.
Load / review first: Facilities
| Column | Required | Format | Example |
|---|---|---|---|
Facility numberfacility | Yes | integer 1–1000 | 1 |
Location namename | Yes | text | Example Room |
Typekind | Yes | room / ward / bed | room |
Inside location (optional)parent | Optional | text | — |
Your verified account becomes the facility administrator. Invite staff in the account portal; staff seats are enforced.
Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.
| Column | Required | Format | Example |
|---|---|---|---|
Namename | Yes | text | Example Staff |
Work emailemail | Yes | staff@example.invalid | |
Clinical rolerole | Yes | facility_admin / doctor / nurse / pharmacist / reception / billing / member | doctor |
Set working days, hours, patient identifiers and billing preferences. Your app starts with an empty patient database.
Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.
| Column | Required | Format | Example |
|---|---|---|---|
Working daysworking_days | Yes | sun-thu / mon-fri / every-day | sun-thu |
Opening time (HH:MM)opening_time | Yes | text | 08:00 |
Closing time (HH:MM)closing_time | Yes | text | 17:00 |
Appointment duration (minutes)slot_minutes | Yes | integer 5–240 | 15 |
Patient record prefixpatient_prefix | Optional | text | EXAMPLE |
Billing currencybilling_currency | Yes | SAR | SAR |
Default languagelanguage | Yes | ar / en | en |
Security roles and explicit permissions
Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.
| Column | Required | Format | Example |
|---|---|---|---|
Role namerole_name | Yes | text | Example scheduling role |
Permission identifierpermission_slug | Yes | text | can_list_schedule |
Facility organization memberships
Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.
Load / review first: Planned team · Departments · Roles & permissions
| Column | Required | Format | Example |
|---|---|---|---|
Staff emailstaff_email | Yes | staff@example.invalid | |
Facility numberfacility | Yes | integer 1–1000 | 1 |
Department namedepartment | Yes | text | Example Department |
Approved role namerole_name | Yes | text | Doctor |
User clinician profile and clinic affiliation
Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.
Load / review first: Planned team · Departments · Rooms, wards and beds · Users & department access
| Column | Required | Format | Example |
|---|---|---|---|
Doctor emailstaff_email | Yes | staff@example.invalid | |
Facility numberfacility | Yes | integer 1–1000 | 1 |
Departmentdepartment | Yes | text | Example Department |
Clinic locationclinic_location | Yes | text | Example Room |
Qualificationqualification | Yes | text | TO-CONFIRM |
Practitioner licencelicense_number | Yes | text | EXAMPLE-LICENSE-001 |
Primary clinicprimary_clinic | Optional | checkbox | true |
Device register, location and department assignment
Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.
Load / review first: Departments · Rooms, wards and beds
| Column | Required | Format | Example |
|---|---|---|---|
Unique asset codeasset_code | Yes | text | EXAMPLE-LAB-001 |
Facility numberfacility | Yes | integer 1–1000 | 1 |
Departmentdepartment | Yes | text | Example Department |
Locationlocation | Yes | text | Example Room |
Device namename | Yes | text | Training laboratory analyser |
Manufacturermanufacturer | Yes | text | Example manufacturer |
Modelmodel | Yes | text | EXAMPLE-MODEL |
Serial numberserial_number | Yes | text | EXAMPLE-SERIAL |
Product / department purposecare_type | Yes | text | laboratory |
Interface protocol and versionprotocol | Optional | text | TO-CONFIRM |
Maintenance duemaintenance_due | Optional | YYYY-MM-DD | 2027-10-09 |
Registry function settings applied to native scheduling closures with readback
Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.
Load / review first: Rooms, wards and beds
| Column | Required | Format | Example |
|---|---|---|---|
Facility numberfacility | Yes | integer 1–1000 | 1 |
Selected feature IDfeature | Yes | scheduling | scheduling |
Function settingfunction_key | Yes | scheduling.closures | scheduling.closures |
Closure namename | Yes | text | Example closure |
First closed datevalid_from | Yes | YYYY-MM-DD | 2026-12-01 |
Last closed datevalid_to | Yes | YYYY-MM-DD | 2026-12-01 |
Closed fromstart_time | Yes | HH:MM | 08:00 |
Closed untilend_time | Yes | HH:MM | 17:00 |
Room (blank closes the whole facility)location | Optional | text | Example Room |
Freeze products, versions, facilities, delivery mode and acceptance scope.
Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.
| Column | Required | Format | Example |
|---|---|---|---|
Catalogue product IDproduct_id | Yes | text | outpatient |
Agreed releaserelease | Yes | text | TO-CONFIRM |
Operating modemode | Yes | native / connected | native |
Facility scopefacility_scope | Yes | text | all |
Included in this projectincluded | Yes | true / false | true |
Accountable roleowner_role | Yes | text | Project owner |
Acceptance evidenceacceptance_test | Yes | text | Approved end-to-end test |
Approval referenceapproval_reference | Yes | text | EXAMPLE-REF-001 |
Map roles to permitted actions and verify access across facility boundaries.
Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.
Load / review first: Facilities · Planned team
| Column | Required | Format | Example |
|---|---|---|---|
Rolerole | Yes | text | doctor |
Facility scopefacility_scope | Yes | text | EXAMPLE-FACILITY-001 |
Resourceresource | Yes | text | Patient record |
Actionaction | Yes | text | read |
Allowedallowed | Yes | true / false | true |
Approverapprover_role | Yes | text | Security owner |
Test evidenceevidence_reference | Yes | text | EXAMPLE-REF-001 |
Define services and approved code mappings before orders, tariffs and interfaces.
Upload this preparation file in Account setup → Implementation files & acceptance evidence. It is saved in your account records. Use the secure migration workspace for actual clinical data. Approve the source-to-target mapping and import adapter for the selected release before any load. Run a dry run, reconcile counts and retain the result log.
Load / review first: Departments
| Column | Required | Format | Example |
|---|---|---|---|
Local service codeservice_code | Yes | text | EXAMPLE-SVC-001 |
English namename_en | Yes | text | Example service |
Arabic namename_ar | Yes | text | خدمة تدريبية |
Department codedepartment_code | Yes | text | EXAMPLE-DEPT-001 |
Unit of serviceunit | Yes | text | TO-CONFIRM |
Code systemcode_system | Yes | text | TO-CONFIRM |
Catalogue releaserelease | Yes | text | TO-CONFIRM |
Approved external mappingexternal_code | Yes | text | TO-CONFIRM |
Effective fromeffective_from | Yes | YYYY-MM-DD | 2026-10-09 |
Record locally approved pathways, responsibilities and exception handling.
Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.
Load / review first: Departments · Access & approvals
| Column | Required | Format | Example |
|---|---|---|---|
Workflow IDworkflow_id | Yes | text | EXAMPLE-WF-001 |
Product IDproduct_id | Yes | text | outpatient |
Entry evententry_event | Yes | text | Patient arrival |
Responsible roleresponsible_role | Yes | text | Nurse |
Required informationrequired_information | Yes | text | Verified identity and visit context |
Next eventnext_event | Yes | text | Clinical consultation |
Handover ownerhandover_owner | Yes | text | Doctor |
Exception pathexception_path | Yes | text | Identity mismatch to review |
Workflow approvalapproval_reference | Yes | text | EXAMPLE-REF-001 |
Plan resource availability, overlap rules, closures and time zone handling.
Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.
Load / review first: Operating preferences · Rooms, wards and beds · Planned team
| Column | Required | Format | Example |
|---|---|---|---|
Schedule IDschedule_id | Yes | text | EXAMPLE-SCH-001 |
Facility numberfacility_number | Yes | integer | 1 |
Departmentdepartment_name | Yes | text | Example Department |
Staff or roomresource_name | Yes | text | Example Room |
Weekdayweekday | Yes | sun / mon / tue / wed / thu / fri / sat | sun |
Start timestart_time | Yes | HH:MM | 08:00 |
End timeend_time | Yes | HH:MM | 17:00 |
Slot durationslot_minutes | Yes | integer minutes | 15 |
Time zonetimezone | Yes | IANA time zone | Asia/Riyadh |
Scheduling approvalapproval_reference | Yes | text | EXAMPLE-REF-001 |
Define the agreed message contract. Store references to credentials, never the credentials themselves.
Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.
Load / review first: Facilities · Service catalogue · Existing systems & versions
| Column | Required | Format | Example |
|---|---|---|---|
Interface IDinterface_id | Yes | text | EXAMPLE-IF-001 |
Source systemsource_system | Yes | text | SRC-EPIC-001 |
Target systemtarget_system | Yes | text | MANSOQ |
Directiondirection | Yes | inbound / outbound / bidirectional | inbound |
Protocol and versionprotocol_version | Yes | text | TO-CONFIRM |
Message scopemessage_scope | Yes | text | TO-CONFIRM |
Identifier mappingidentifier_mapping | Yes | text | TO-CONFIRM |
Secret manager referencesecret_reference | Yes | text | REFERENCE-ONLY |
Retry and duplicate policyretry_policy | Yes | text | TO-CONFIRM |
Failure ownerfailure_owner | Yes | text | Integration owner |
Test evidencetest_reference | Yes | text | EXAMPLE-REF-001 |
Record complete positive, negative, boundary, access and failure tests per product.
Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.
Load / review first: Project scope · Clinical workflow configuration
| Column | Required | Format | Example |
|---|---|---|---|
Test IDtest_id | Yes | text | UAT-001 |
Product IDproduct_id | Yes | text | outpatient |
Scenarioscenario | Yes | text | Visit from arrival to financial follow-up |
Preconditionspreconditions | Yes | text | Approved setup and synthetic data |
Exact actionsactions | Yes | text | TO-CONFIRM |
Expected resultexpected_result | Yes | text | TO-CONFIRM |
Actual resultactual_result | Yes | text | NOT-RUN |
Statusstatus | Yes | not_run / pass / fail / blocked | not_run |
Evidence referenceevidence_reference | Yes | text | EXAMPLE-REF-001 |
Approverapprover_role | Yes | text | Product owner |
Inventory every source EHR, department system, archive and ERP separately, including the exact installed product and licensed extraction route.
Upload this planning CSV in Account setup → Implementation files & acceptance evidence. Preview, apply and save. Keep source clinical files and identity crosswalk records in the approved secure migration workspace. Record actual evidence references after review; this register does not run a vendor connector or import patient history.
Load / review first: Project scope
| Column | Required | Format | Example |
|---|---|---|---|
System IDsystem_id | Yes | text | SRC-EPIC-001 |
Vendorvendor | Yes | text | Epic |
Installed productproduct | Yes | text | Epic EHR |
Installed releaserelease | Yes | text | TO-CONFIRM |
Environmentenvironment | Yes | test / production / archive | test |
Facilities coveredfacility_scope | Yes | text | EXAMPLE-FACILITY-001 |
Source administrator rolesource_owner | Yes | text | Source EHR administrator |
Approved extraction routeexport_route | Yes | text | EHI export assessment pending |
Licence/access evidencelicence_reference | Yes | text | EXAMPLE-REF-001 |
Release-specific specificationspecification_reference | Yes | text | https://open.epic.com/TechnicalSpecifications |
Illustrative operating cases
A bedside team requests specialist input using the agreed hub-and-spoke programme.
The specialist recommendation and local action owner are distinguishable and linked to the case.
A planned specialist review cannot use its accepted video connection.
The communication gap, limitations, recommendations and clinical ownership remain explicit.
Worked operating scenarios
Switch to the approved communication procedure, keep bedside responsibility explicit and reconcile review documentation after recovery.
Identify the missing observation or record and request it from the local owner; record the limits of the remote review.
Delivery boundary
Specialist workflow, video, cameras and clinical/device exchange have distinct delivery boundaries. Confirm each facility’s network, equipment and supported integrations before commissioning.
A defined remote critical-care coordination composition with supported local-system, video or device interfaces scoped separately. Establish hub & spoke: Identify participating facilities, critical-care beds and specialist coverage. Agree which organization owns care, which records remote staff may access and the escalation contacts for each site. Prepare the case: Link the person and encounter to the shared review context. Confirm available observations, notes and imaging sources; commission camera or device connections only within the agreed scope. Review remotely: Let the authorized specialist review the case and document the assessment and recommendations. Name the bedside owner who receives and acts on the plan; remote advice does not silently transfer clinical responsibility. Follow & escalate: Track the next review and handover responsibilities. Maintain contact and downtime procedures for unavailable video, incomplete source information or a case requiring direct escalation.
Explore the detailsConfigure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include Doctors & operational clinics (doctors.csv); Scheduling configuration (scheduling.csv); Assets, devices & hardware (assets_devices.csv); Interface specification (interfaces.csv); Access & approvals (access_matrix.csv); Clinical workflow configuration (clinical_workflows.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.
Explore the detailsRemote connection unavailable Switch to the approved communication procedure, keep bedside responsibility explicit and reconcile review documentation after recovery. Source data is incomplete Identify the missing observation or record and request it from the local owner; record the limits of the remote review.
Explore the detailsSpecialist workflow, video, cameras and clinical/device exchange have distinct delivery boundaries. Confirm each facility’s network, equipment and supported integrations before commissioning.
Explore the details