MANSOQ IMPLEMENTATION

A clear path to your first day.

Your products. Your data. Every step, from setup to support.

FROM SCOPE TO SUPPORT

Know what comes next.

01 / 10

Agree the scope

Responsible

Sponsor + product owners

Before you start

Named sponsor, facility list and selected products.

  1. List every legal entity, facility, department, product and operating mode. Separate native operation from a connection to another system.
  2. Pin the application, interface and terminology releases. Confirm availability, licence rights, seats, facilities, storage and support terms against the proposal.
  3. Name clinical, finance, data, security, integration and operations owners. Agree approvals, test evidence and decision deadlines.
  4. Record each assumption: history to migrate, language, currency, time zone, shared identifiers, downtime, external credentials and who owns each system. Do not turn an unresolved assumption into a default.
  5. Agree acceptance criteria and the exact tasks that are out of scope. Give each excluded task a reason, owner and follow-up path.
Acceptance evidence

Signed scope, release list and decision register.

Exceptions & fallback

Unavailable product, missing licence or unapproved data boundary: revise scope before account launch.

Make every assumption explicit.

The public kit describes the current default setup. The template inside your account is authoritative for its version and selected capabilities. Empty datasets need a documented “not applicable” decision. A new product, release or local requirement needs an approved mapping, owner and acceptance test before activation.

YOUR EXISTING SYSTEM

A clear route from where you are.

Choose your system and your goal. See the route, files and checks that apply.

All named systems 55 products & legacy variants

Saudi references and international products are named below. This is a researched directory, not a complete global census or a list of prebuilt MANSOQ connectors. Select “Another vendor” for any unlisted or in-house system.

System / installed productCategoryReferenceExplore
EpicHospital & clinicSaudi reference availableOfficial source ↗
InterSystems TrakCareHospital & clinicSaudi reference availableOfficial source ↗
Oracle Health Millennium (Cerner Millennium)Hospital & clinicOfficial source ↗
Oracle Health Foundation EHRHospital & clinicSaudi reference availableOfficial source ↗
Oracle Soarian ClinicalsHospital & clinicOfficial source ↗
Lean RaqeemSaudi platformsSaudi reference availableOfficial source ↗
ezCaretech BESTCareHospital & clinicSaudi reference availableOfficial source ↗
OASIS HISHospital & clinicSaudi reference availableOfficial source ↗
MEDITECH ExpanseMEDITECH 6.1MEDITECH MAGICMEDITECH Client/ServerHospital & clinicOfficial source ↗
athenaOneHospital & clinicOfficial source ↗
athenaPracticeathenaFlowHospital & clinicOfficial source ↗
eClinicalWorksHospital & clinicOfficial source ↗
NextGen EnterpriseNextGen OfficeHospital & clinicOfficial source ↗
Altera SunriseAltera ParagonAltera TouchWorksHospital & clinicOfficial source ↗
Veradigm EHRVeradigm Practice ManagementHospital & clinicOfficial source ↗
Dedalus ORBISDedalus ORBIS UDedalus DxCareDedalus LorenzoDedalus webPASDedalus MedChartHospital & clinicOfficial source ↗
CGM eMDsCGM APRIMAHospital & clinicOfficial source ↗
System C CareFlow EPRHospital & clinicOfficial source ↗
TPP SystmOneEMIS WebHospital & clinicOfficial source ↗
Philips Tasy EMRHospital & clinicOfficial source ↗
OpenMRSHospital & clinicOfficial source ↗
OpenEMRHospital & clinicOfficial source ↗
BahmniHospital & clinicOfficial source ↗
Clinisys Sunquest LaboratoryClinisys SQ LabLaboratoryOfficial source ↗
Clinisys GLIMSLaboratoryOfficial source ↗
LabWare LIMSLaboratoryOfficial source ↗
Sectra PACSSectra VNASectra RISImagingOfficial source ↗
GE HealthCare Centricity PACSGE Centricity Enterprise ArchiveGE Centricity RISImagingOfficial source ↗
Philips IntelliSpace PACSImagingOfficial source ↗
Siemens Healthineers syngo.viaSiemens Syngo CarbonImagingOfficial source ↗
SAP S/4HANAFinance & supplyOfficial source ↗
Oracle Fusion Cloud FinancialsFinance & supplyOfficial source ↗
Microsoft Dynamics 365 FinanceMicrosoft Dynamics 365 Supply Chain ManagementFinance & supplyOfficial source ↗
Another vendor, in-house system or paper archiveHospital & clinicOfficial source ↗
SELECTED SYSTEM

Epic

JHAH describes its Epic-powered MyChart service. Saudi reference ↗

VENDOR ROUTE TO VERIFY

Obtain the complete agreed export.

  1. Ask the Epic administrator for the approved patient-population EHI export and its release-matched dictionary. Inventory EHI Tables TSV, clinical documents and external storage separately.
  2. For a bounded clinical cohort, assess Epic FHIR Bulk Data separately: register the backend client, obtain site approval, define the authorized group and supported resources, start the asynchronous export, poll its status and retain output/error files.
  3. Check appointments, active inpatient episodes, claims, balances, attachments and imaging against source reports. A clinical FHIR or C-CDA extract may not cover all of them.

Epic API availability does not prove a MANSOQ connector exists. Confirm both release-specific adapters, cohort permissions, export completeness and write ownership.

The complete path, step by step.

9 stages · Owners, inputs, actions, files and acceptance gates.

01Inventory & authorize
Responsible

Project, source-system, data and privacy owners

Required input

Selected systems, facilities, products and action.

  1. Record every source product, environment, release, module, external archive and department system. Confirm extraction/interface rights, vendor work orders, charges, owners and test access.
  2. List each data domain and date/cohort boundary. Decide migrate, connect, archive or exclude with a reason, retention decision and system of record. Include legal holds and secure transfer/hosting location.
Acceptance evidence

Approved inventory and domain-by-domain scope; named owners; unresolved assumptions have an owner and closure test.

Exceptions & fallback

No extraction rights or unresolved consent/retention boundary: hold that domain and record the approved alternative.

02Confirm the destination before extraction
Responsible

MANSOQ release owner and source/target integration leads

Required input

Approved source scope and selected MANSOQ release.

  1. For every domain, identify a verified target resource, field dictionary, supported API/import tool and licensed adapter. Mark unsupported domains as archive or connected with owner approval.
  2. Prepare foundation records first: organizations, facilities, departments, locations, users/permissions, services, practitioners, medication/items and configuration. Provision an isolated private test application; account CSV preparation does not load clinical history.
Acceptance evidence

Release-specific mapping and adapter approved; target permissions and foundation dependencies tested.

Exceptions & fallback

Missing target operation or connector: keep the path blocked until an adapter is approved; never send a vendor FHIR bundle to an assumed MANSOQ ingest endpoint.

03Map identity, terminology & relationships
Responsible

Identity steward and clinical, laboratory, pharmacy and finance owners

Required input

Both data dictionaries, source catalogues and target references.

  1. Define identifier issuer/facility namespaces, source-to-target secure crosswalk and reviewed merge/unmerge rules. Quarantine ambiguous identities; never match only by name.
  2. Map fields, status history, references, null/unknown values, units, precision, code-system releases, time zones and provenance. Include Arabic/English encoding, newborn/unknown patients and corrected/deleted source records.
Acceptance evidence

Reviewed crosswalk policy, terminology equivalence and relationship mapping with explicit unresolved exceptions.

Exceptions & fallback

Unknown code/unit or ambiguous person: quarantine, preserve the original and ask the accountable steward; never guess clinical meaning.

04Extract & verify the complete package
Responsible

Source administrator and secure-transfer owner

Required input

Approved vendor route, filters, dictionaries and secured workspace.

  1. Follow the selected system’s documented export route. Retain actual TSV/NDJSON/XML/DICOM/native files plus clinical documents, images and attachment indexes in their original format. CSV templates here are planning registers.
  2. Create a manifest with extraction time, source filter/watermark, dictionary version, count, bytes and SHA-256 per file/archive part. Verify checksums after encrypted transfer; test decompression and representative attachment retrieval.
  3. List absent domains explicitly. Source reports, not assumptions, supply the expected counts and financial totals.
Acceptance evidence

Verified immutable extraction package and manifest; every missing domain assigned a disposition.

Exceptions & fallback

Failed transfer/hash, truncated file, invalid encoding or unavailable blob: quarantine the package, correct at source and repeat extraction with a new batch ID.

05Rehearse transformation & ordered loads
Responsible

Approved migration operator and target administrator

Required input

Verified extraction, mappings and an isolated test application.

  1. Run the approved transformation adapter with a pinned version and dry-run validation. Capture rejects by source record and reason in the secure workspace.
  2. Load dependencies in approved order: foundation → identities/crosswalk → encounters and relationships → clinical orders/results/documents → medications/care plans → future appointments and active operational records → approved finance/inventory. The release-specific adapter defines exact ordering.
  3. Record batch IDs, before/after counts and receipts. Prove rerun idempotency, duplicate handling and a tested restore point. Do not write directly to live databases or disable audit for convenience.
Acceptance evidence

Dry-run logs, accepted/rejected counts, relationship validation, repeat-run test and restore evidence.

Exceptions & fallback

A dependency or required clinical field fails: stop dependent loads, repair mapping/source, replay only the approved batch and retain both versions.

06Reconcile content, totals & clinical meaning
Responsible

Data owner, representative clinicians and finance/operations owners

Required input

Source counts/totals and dry-run target reports.

  1. Compare counts by facility, domain, date and status; source = loaded + held/rejected + explicitly approved exclusions under the same filters. Confirm orphan references, duplicates, missing attachments and image instances.
  2. Review representative records end to end: identity → encounter → allergies/medications → orders/results → documentation → scheduling/care plan → revenue. Reconcile open balances, partial payments, credit notes and currency/minor units with finance.
  3. Record tolerances before the test, account for every difference and sign accepted exceptions. A count match alone does not establish clinical equivalence.
Acceptance evidence

Signed quantitative and clinical reconciliation with all unresolved safety/financial differences closed or held out of production.

Exceptions & fallback

Unexplained count/amount differences or wrong-patient content: fail the gate, correct the batch and rerun acceptance.

07Test the actual work & train owners
Responsible

Clinical, operations, finance, security and training leads

Required input

Reconciled test application and mapped interfaces.

  1. Run role-based end-to-end cases for each selected product, including normal work, permission denial, cancelled/corrected/duplicate events, partial payment, missing data and downtime recovery.
  2. Train staff on the new source of truth, archive lookup, unresolved-data queues and approved fallback. Record sign-off by department and named go/no-go authority.
Acceptance evidence

Executed UAT and interface cases, access tests, training attendance/competence and go/no-go criteria.

Exceptions & fallback

Failed critical test, missing acceptance owner or untrained coverage: hold activation or reduce the approved rollout scope.

08Freeze, delta & controlled cutover
Responsible

Cutover lead, source/target operators and care/finance owners

Required input

Accepted rehearsal, restore test, timed runbook and authorized change window.

  1. Record baseline and exact final watermark. Agree the source write freeze or event-capture boundary; extract and load final changes, cancellations and corrections only through a verified supported route.
  2. Reconcile the final delta, active inpatient census, pending orders, future appointments, open claims and balances. Assign one writer per domain and switch routes in the approved order.
  3. Time-box smoke tests, downtime work and go/no-go decision. Define the rollback trigger/deadline and how post-switch writes would be preserved and reconciled before any rollback.
Acceptance evidence

Signed final reconciliation, switch receipts, smoke tests and authorized go-live decision.

Exceptions & fallback

No reliable delta, cutover overrun or failed clinical smoke test: do not switch. Use the rehearsed downtime/rollback route; never restore blindly over new clinical writes.

09Monitor, retain & hand over
Responsible

Operations, records/privacy owner and service desk

Required input

Accepted go-live, incident routes and archive/exit policy.

  1. Monitor rejected events, queues, latency, missing data, user access and daily clinical/financial reconciliation during agreed hypercare. Assign defect owners and evidence-based closure.
  2. Test archive lookup, attachments, imaging and restoration; maintain approved retention and legal holds. Renew credentials/licences and document the exit package.
  3. Retire the source only through a separately approved change after archive access, reconciliation, support and retention obligations are accepted.
Acceptance evidence

Signed support handover, tested recovery/archive access, renewal ownership and approved source-retirement decision.

Exceptions & fallback

Missing archive access, unresolved reconciliation or a legal hold: retain the source securely under the agreed access policy.

Check every data domain before you agree scope.

Record native, connected, archive or excluded for every domain. Mark non-applicable items with an owner and reason; scope must never be inferred from missing files.

DomainWhat to inventorySource materialAcceptance / exception
Organization & peopleEntities, sites, departments, rooms/beds, staff/roles, practitioner affiliations, schedules and permissions.Approved CSV/API or vendor master extracts.Foundation references and least-privilege access; do not migrate password hashes or assume source roles match.
Patient identity & relationshipsIdentifiers/issuers, demographics, contacts, guardians, deceased/temporary/newborn identity and merge history.Secure source export and reviewed crosswalk.Identity steward resolves ambiguity; preserve original IDs and facility namespaces.
Clinical episodes & active workEncounters, inpatient census/bed assignments, pending tasks, orders, referrals, care plans and handovers.Vendor extract/API plus final change boundary.Open work requires clinical acceptance and one owning system; a historical summary is insufficient.
Medication continuityAllergies, active/discontinued orders, prescriptions, dispensing and administration history.Clinical export plus approved catalogue mapping.Preserve status, route, strength, units and provenance; pharmacy review before current use.
DiagnosticsLab orders/specimens, preliminary/final/corrected results, units, reference ranges and critical-result status.LIS/EHR extract, documents and event specification.Reconcile patient/order/specimen/version links; no invented conversions or lost corrections.
Imaging & original mediaStudy/series/instance objects, accession, reports, scans, audio/video and attachment index.DICOM/native binaries with indexed export manifest.Confirm all objects remain retrievable and linked; a PDF report is not a full study archive.
Future appointmentsClinic calendars, recurring schedules, booked/cancelled/rescheduled visits, practitioner availability and time zone.Scheduling extract plus final deltas.Count future bookings and test leave/overlap rules; assign one scheduling writer.
Revenue & coveragePolicies/member coverage, payer/provider contracts, SBS mappings, tariffs, authorization, claims, denials and responses.Approved RCM extracts, documents and interface dictionaries.Follow legal entity and effective-date boundaries; migrate open state without duplicate submissions.
Finance & inventoryCharges, receivables/payments/credits, invoices/tax, ledger dimensions, items/lots, stock quantities and costs.Approved finance/stock extracts and reconciliation.Reconcile currencies/minor units, reversals, partial payments, lot expiry and physical counts.
Specialist careOperating-room procedure/recovery, ICU device/vital history, TeleICU reviews, home visits and palliative care plans.Enabled product extracts plus department/device system inventory.Specify active plans, escalation, responsibility and attachments; do not imply every raw device stream fits a clinical API.
Consent, audit & governanceConsents, restrictions, document signatures, author/time/source, revisions, access audit, legal holds and retention.Approved evidence/audit export and preserved provenance.Do not relabel historical authors as current users or change signed originals; agree native versus archive disposition.
Portal & operational linksPatient portal identities, communications, account activation, external document links, analytic/report feeds and integration receipts.Vendor-approved metadata/export and access plan.Re-enrol users through approved identity controls; verify changed links, report definitions and access rather than copying sessions.

Technical instructions describe the reviewed route. The site’s installed release, enabled scopes and approved MANSOQ target adapter decide what can be executed. Record approvals and evidence; uploading these CSVs does not activate a vendor connection or migrate clinical records.

HL7 bulk export workflow ↗NPHIES scope specifications ↗Sources reviewed 10 October 2026.

43 CATALOGUE PRODUCTS

Configure the whole product.

Inputs, functions, dependencies and proof of readiness.

MANSOQ Core

Shared patient identity and record, administrative and clinical context, access, audit and common configuration within an agreed data boundary.

Scope and release review

Configuration checklist

  • Identity rules and duplicate review
  • Facility boundaries, roles and permissions
  • Audit, retention and common configuration

Every function in scope

  • Patient identity and shared record
  • Administrative and clinical perspectives
  • Baseline access and audit
  • Shared configuration and supported base services

Dependencies & modes

Confirm shared setup

Agreed mode: native / connected

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Outpatient Care

Registration, appointments, encounter queues, consultations and follow-up with required clinical and billing scope.

Scope and release review

Configuration checklist

  • Clinics, consultation rooms and specialties
  • Doctor affiliations, schedules and visit types
  • Documentation, orders, results and follow-up

Every function in scope

  • Registration, availability and appointments
  • Queues and encounter context
  • Clinical documentation and relevant results
  • Orders, prescriptions and follow-up
  • Core visit billing

Dependencies & modes

MANSOQ Core

Agreed mode: native

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Inpatient Care

Admission, transfer and discharge, wards, beds, nursing, orders and medication in a complete admitted-care workflow.

Scope and release review

Configuration checklist

  • Wards, beds and transfer states
  • Care teams, shift handovers and care plans
  • Medication, departmental orders and discharge

Every function in scope

  • Admissions, discharge and transfers
  • Wards and bed workflow
  • Nursing documentation and care context
  • Medication and departmental orders
  • Discharge and charge linkage

Dependencies & modes

MANSOQ Core

Agreed mode: native

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Emergency Care

Emergency encounter context, observations and accountable care handovers according to verified operational scope.

Scope and release review

Configuration checklist

  • Arrival and locally approved triage states
  • Urgent care roles, locations and escalation
  • Observation, admission, transfer and discharge

Every function in scope

  • Emergency encounter context, observations and accountable care handovers according to verified operational scope.

Dependencies & modes

MANSOQ Core

Agreed mode: native

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

TeleICU

A defined remote critical-care coordination composition with supported local-system, video or device interfaces scoped separately.

Scope and release review

Configuration checklist

  • Hub/spoke facilities and specialist coverage
  • Patient context sources and device interfaces
  • Remote review, escalation and bedside responsibility

Every function in scope

  • A defined remote critical-care coordination composition with supported local-system, video or device interfaces scoped separately.

Dependencies & modes

MANSOQ Core · System & Device Interfaces

Agreed mode: native

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Home & Palliative Care

Visits, care plans and multidisciplinary documentation with verified palliative workflows. Mobile, offline and family channels are distinct scope.

Scope and release review

Configuration checklist

  • Service zones, visit teams and travel constraints
  • Care plans, consent and caregiver contacts
  • Remote documentation, symptom review and escalation

Every function in scope

  • Visits, care plans and multidisciplinary documentation with verified palliative workflows. Mobile, offline and family channels are distinct scope.

Dependencies & modes

MANSOQ Core

Agreed mode: native

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Operating Room

Verified case booking, preparation, perioperative documentation, resources, consumables and post-operative handover scope.

Scope and release review

Configuration checklist

  • Theatres, resources, sessions and equipment
  • Procedure preparation and approved safety checklist
  • Anesthesia, consumables, recovery and handover

Every function in scope

  • Verified case booking, preparation, perioperative documentation, resources, consumables and post-operative handover scope.

Dependencies & modes

MANSOQ Core · One of: Inpatient Care / Outpatient Care

Agreed mode: native

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Intensive Care

Verified critical-care record, observations, medication and device-connection scope. Monitoring and alarm functionality must be explicitly verified.

Scope and release review

Configuration checklist

  • Bed/monitor inventory and care-team coverage
  • Observations, devices and unit mappings
  • Medication, escalation and shift handover

Every function in scope

  • Verified critical-care record, observations, medication and device-connection scope. Monitoring and alarm functionality must be explicitly verified.

Dependencies & modes

MANSOQ Core · Inpatient Care

Agreed mode: native

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Pharmacy

Medication requests, dispensing and stock operation beyond prescribing or viewing a medication list.

Scope and release review

Configuration checklist

  • Medication catalogue, codes, units and conversions
  • Prescription verification, dispensing and returns
  • Stock lots, expiry and controlled access

Every function in scope

  • Medication requests, dispensing and stock operation beyond prescribing or viewing a medication list.

Dependencies & modes

MANSOQ Core · Orders, Results & Medication · Inventory

Agreed mode: native

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Laboratory

Lab orders, specimen and result workflows with native operation distinct from external LIS integration.

Scope and release review

Configuration checklist

  • Test catalogue, specimens and collection workflow
  • Analyzer mappings, units and reference intervals
  • Result validation, critical-result escalation and amended reports

Every function in scope

  • Lab orders, specimen and result workflows with native operation distinct from external LIS integration.

Dependencies & modes

MANSOQ Core · Orders, Results & Medication

Agreed mode: native

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Radiology

Verified radiology requests, departmental operation and reporting; RIS/PACS interfaces have separate delivery scope.

Scope and release review

Configuration checklist

  • Modalities, procedure catalogue and scheduling
  • RIS/PACS accession identifiers and interfaces
  • Acquisition, reporting, addenda and critical-result escalation

Every function in scope

  • Verified radiology requests, departmental operation and reporting; RIS/PACS interfaces have separate delivery scope.

Dependencies & modes

MANSOQ Core · Orders, Results & Medication

Agreed mode: native

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Inventory

Stock, stores and departmental supply operation within the agreed supported scope.

Scope and release review

Configuration checklist

  • Stores, items, units and suppliers
  • Opening lots, quantities, cost and expiry
  • Receipt, issue, transfer, return and reconciliation

Every function in scope

  • Stock, stores and departmental supply operation within the agreed supported scope.

Dependencies & modes

MANSOQ Core

Agreed mode: native

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Clinical Documentation & Care Planning

Required clinician and nursing documentation, observations, forms, care plans and handovers as defined for the selected care workflow.

Scope and release review

Configuration checklist

  • Approved templates, author roles and signatures
  • Correction and amendment rules
  • Retention and encounter linkage

Every function in scope

  • Required clinician and nursing documentation, observations, forms, care plans and handovers as defined for the selected care workflow.

Dependencies & modes

MANSOQ Core

Agreed mode: native

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Orders, Results & Medication

Required order/result and medication scope for the chosen workflow, separate from native departmental operation.

Scope and release review

Configuration checklist

  • Order types, approved catalogues and destinations
  • Statuses, authorization and cancellation
  • Results, medication links and responsibility

Every function in scope

  • Required order/result and medication scope for the chosen workflow, separate from native departmental operation.

Dependencies & modes

MANSOQ Core

Agreed mode: native

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Patient Access

Registration, scheduling, encounter access and queues; patient portal and family communication scope is separately verified.

Scope and release review

Configuration checklist

  • Identifiers, registration and matching
  • Visit types, booking resources and arrival
  • Consent, cancellation and referral ownership

Every function in scope

  • Registration, scheduling, encounter access and queues; patient portal and family communication scope is separately verified.

Dependencies & modes

MANSOQ Core

Agreed mode: native

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Billing & Finance

Invoices, payments and financial records linked to care activity, with accounting connections defined separately.

Scope and release review

Configuration checklist

  • Gross prices, tax applicability and invoice ownership
  • Payments, refunds and reversals
  • Finance export, control totals and reconciliation

Every function in scope

  • Invoices, payments and financial records linked to care activity, with accounting connections defined separately.

Dependencies & modes

MANSOQ Core

Agreed mode: native / connected

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Revenue Cycle Management

A complete connected revenue workflow with granular modules for eligibility, authorization, payer configuration, charges, claims, denials and reconciliation.

Scope and release review

Configuration checklist

  • Legal entities, contracts and issued policies
  • Benefits, networks, tariffs and rule versions
  • Eligibility through claim, denial, payment and reconciliation

Every function in scope

  • A complete connected revenue workflow with granular modules for eligibility, authorization, payer configuration, charges, claims, denials and reconciliation.

Dependencies & modes

MANSOQ Core

Agreed mode: native / connected

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

SBS Specific Mapping Tooling

Specific supported service-code mapping and update scope. Required clinical/claim codes are not removed to create a price upgrade.

Scope and release review

Configuration checklist

  • Selected SBS codes and release rights
  • Local-service mapping and effective dates
  • Approval evidence and code validation

Every function in scope

  • Specific supported service-code mapping and update scope. Required clinical/claim codes are not removed to create a price upgrade.

Dependencies & modes

MANSOQ Core · Revenue Cycle Management

Agreed mode: native / connected

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Full Supported SBS Catalogue Tooling

Full supported catalogue import, mapping and update tooling; the actual release, scope and usage permissions are agreed.

Scope and release review

Configuration checklist

  • Licensed catalogue release and scope
  • Full code mappings and catalogue import owner
  • Inactive codes, version changes and usage rights

Every function in scope

  • Full supported catalogue import, mapping and update tooling; the actual release, scope and usage permissions are agreed.

Dependencies & modes

MANSOQ Core · Revenue Cycle Management

Agreed mode: native / connected

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

DRG / Casemix / Grouper Integration

Defined coding/casemix workflow, supported grouper release, licensing and interfaces; catalogue access does not imply an active grouper license.

Scope and release review

Configuration checklist

  • Grouper version and licence
  • Coding inputs, completeness and grouping route
  • Casemix outputs, correction and financial use approval

Every function in scope

  • Defined coding/casemix workflow, supported grouper release, licensing and interfaces; catalogue access does not imply an active grouper license.

Dependencies & modes

MANSOQ Core · Revenue Cycle Management

Agreed mode: native / connected

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

NPHIES

Supported eligibility, authorization and claims exchange, with onboarding, credentials, versions and activation agreed explicitly.

Scope and release review

Configuration checklist

  • Provider identity, payer routes and certified package
  • Sandbox/production endpoints and secret references
  • Eligibility, authorization, claim and payment-response tests

Every function in scope

  • Supported eligibility, authorization and claims exchange, with onboarding, credentials, versions and activation agreed explicitly.

Dependencies & modes

MANSOQ Core · Revenue Cycle Management

Agreed mode: native / connected

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

ZATCA E-invoicing

Supported e-invoice integration and onboarding, with applicable phase, configuration and operational responsibilities stated.

Scope and release review

Configuration checklist

  • Legal taxpayer, VAT and applicable phase
  • Invoice sequences, tax categories and device onboarding
  • Clearance/reporting, retry and credential renewal

Every function in scope

  • Supported e-invoice integration and onboarding, with applicable phase, configuration and operational responsibilities stated.

Dependencies & modes

MANSOQ Core · Billing & Finance

Agreed mode: native / connected

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Advanced Analytics

Selected operational, departmental and revenue reports, separate from standard Core reporting.

Scope and release review

Configuration checklist

  • Source ownership, metric definitions and access
  • Refresh, filters, grain and reconciliation
  • Export controls and dashboard acceptance

Every function in scope

  • Selected operational, departmental and revenue reports, separate from standard Core reporting.

Dependencies & modes

MANSOQ Core

Agreed mode: native

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Reviewed AI Assistance

Only verified assistive tasks, defined data boundaries and responsible human review are offered. No autonomous diagnostic claim is made.

Scope and release review

Configuration checklist

  • Approved use case, data access and model version
  • Human review, failure route and audit
  • Evaluation criteria and monitoring; no autonomous clinical assumption

Every function in scope

  • Only verified assistive tasks, defined data boundaries and responsible human review are offered. No autonomous diagnostic claim is made.

Dependencies & modes

MANSOQ Core

Agreed mode: native

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

System & Device Interfaces

Actual HIS, LIS, RIS/PACS, identity, device or API connections, protocols, licenses and delivery scope are specified individually.

Scope and release review

Configuration checklist

  • Protocol/version, source/target and ownership
  • Identifier and terminology mapping
  • Retry, duplicates, queues, outage and recovery

Every function in scope

  • Actual HIS, LIS, RIS/PACS, identity, device or API connections, protocols, licenses and delivery scope are specified individually.

Dependencies & modes

MANSOQ Core

Agreed mode: native / connected

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Network Governance

Defined entity, tenant and record boundaries, accountable access and governed network composition.

Scope and release review

Configuration checklist

  • Legal entities, facility and data boundaries
  • Delegated administration and cross-site roles
  • Patient continuity, shared catalogues and boundary tests

Every function in scope

  • Defined entity, tenant and record boundaries, accountable access and governed network composition.

Dependencies & modes

MANSOQ Core · System & Device Interfaces

Agreed mode: native / connected

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Implementation & Training

Agreed workflow configuration, adoption preparation, training and go-live responsibilities.

Scope and release review

Configuration checklist

  • Scope, owners, releases and acceptance
  • Configuration, tests, training and cutover
  • Support handover and controlled changes

Every function in scope

  • Agreed workflow configuration, adoption preparation, training and go-live responsibilities.

Dependencies & modes

MANSOQ Core

Agreed mode: native / connected

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Data Migration

Source data, transformation, validation, rehearsal and acceptance are scoped separately.

Scope and release review

Configuration checklist

  • Source inventory and retention decision
  • Field mapping, dry runs and rejected records
  • Cutover delta, control totals and rollback

Every function in scope

  • Source data, transformation, validation, rehearsal and acceptance are scoped separately.

Dependencies & modes

MANSOQ Core

Agreed mode: native / connected

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Support & Service Terms

Named service coverage, response, operating responsibilities and agreed continuity targets.

Scope and release review

Configuration checklist

  • Coverage, contacts and severity rules
  • Alert ownership, escalation and restoration
  • Renewals, release maintenance and acceptance

Every function in scope

  • Named service coverage, response, operating responsibilities and agreed continuity targets.

Dependencies & modes

MANSOQ Core

Agreed mode: native / connected

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Equipment & Third-party Licenses

Devices, third-party software/licenses and supplier obligations are quoted independently of MANSOQ software.

Scope and release review

Configuration checklist

  • Device inventory, location and maintenance
  • Protocol, connectivity and commissioning
  • Acceptance tests and biomedical ownership

Every function in scope

  • Devices, third-party software/licenses and supplier obligations are quoted independently of MANSOQ software.

Dependencies & modes

MANSOQ Core

Agreed mode: native / connected

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Managed Revenue People Services

Qualified people, authorized access and an accepted operating scope, separate from RCM software.

Scope and release review

Configuration checklist

  • Delegated duties and payer authority
  • Work queues, source access and quality checks
  • Submission, remittance, reconciliation and reporting

Every function in scope

  • Qualified people, authorized access and an accepted operating scope, separate from RCM software.

Dependencies & modes

MANSOQ Core

Agreed mode: native / connected

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Eligibility

Coverage verification and exchange traces.

Scope and release review

Configuration checklist

  • Member/policy identifiers and payer route
  • Benefit version and service context
  • Unavailable, expired and conflicting cover handling

Every function in scope

  • Coverage verification and exchange traces.

Dependencies & modes

MANSOQ Core

Agreed mode: native / connected

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Preauthorization

Requests, responses, status and next responsibilities.

Scope and release review

Configuration checklist

  • Service/code mapping and evidence requirements
  • Requested, approved, denied and expired states
  • Partial approval, extension, cancellation and escalation

Every function in scope

  • Requests, responses, status and next responsibilities.

Dependencies & modes

MANSOQ Core

Agreed mode: native / connected

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Payer Contracts

Versioned payer, TPA and contract scope.

Scope and release review

Configuration checklist

  • Legal provider/insurer/administrator IDs
  • Signed effective dates and amendments
  • Allowed amounts, deadlines and evidence authority

Every function in scope

  • Versioned payer, TPA and contract scope.

Dependencies & modes

MANSOQ Core

Agreed mode: native / connected

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Networks

Provider and payer network configuration.

Scope and release review

Configuration checklist

  • Provider affiliations and network tiers
  • Effective dates and policy relationships
  • Out-of-network exceptions and precedence

Every function in scope

  • Provider and payer network configuration.

Dependencies & modes

MANSOQ Core

Agreed mode: native / connected

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Benefits & Cost Sharing

Coverage, exclusions, limits and patient contribution.

Scope and release review

Configuration checklist

  • Issued policy, member class and limits
  • Exclusions, deductibles and co-pay
  • Accumulation, exceptions and rule precedence

Every function in scope

  • Coverage, exclusions, limits and patient contribution.

Dependencies & modes

MANSOQ Core

Agreed mode: native / connected

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Tariffs & Price Lists

Service prices, contract rules and versioned mapping.

Scope and release review

Configuration checklist

  • Catalogue codes, currency and gross prices
  • Contracted allowed amounts and assignments
  • Effective overlap, negotiated exceptions and amendments

Every function in scope

  • Service prices, contract rules and versioned mapping.

Dependencies & modes

MANSOQ Core

Agreed mode: native / connected

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Charge Capture

Link service activity to accountable charges.

Scope and release review

Configuration checklist

  • Service event and charge identity
  • Quantity, unit, performer and documentation
  • Missing charge, duplicates, corrections and reversals

Every function in scope

  • Link service activity to accountable charges.

Dependencies & modes

MANSOQ Core

Agreed mode: native / connected

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Claims

Submission scope, work queues, responses and decision traces.

Scope and release review

Configuration checklist

  • Submission authority, deadlines and routes
  • Payload completeness and attachments
  • Status polling, duplicates, cancellation and corrected claims

Every function in scope

  • Submission scope, work queues, responses and decision traces.

Dependencies & modes

MANSOQ Core

Agreed mode: native / connected

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Denials & Resubmission

Reasons, correction, resubmission and follow-up ownership.

Scope and release review

Configuration checklist

  • Payer reason codes and owner routing
  • Documentation correction and appeal deadlines
  • Appeal evidence, resubmission and disposition

Every function in scope

  • Reasons, correction, resubmission and follow-up ownership.

Dependencies & modes

MANSOQ Core

Agreed mode: native / connected

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Remittance

Review payer responses and financial allocation scope.

Scope and release review

Configuration checklist

  • Payer payment reference and claim links
  • Advice lines, deductions and adjustments
  • Partial payment, reversal and unmatched advice

Every function in scope

  • Review payer responses and financial allocation scope.

Dependencies & modes

MANSOQ Core

Agreed mode: native / connected

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

Reconciliation

Trace financial responses, records and agreed close scope.

Scope and release review

Configuration checklist

  • Bank/ledger/payer identifiers and dates
  • Control totals, currencies and exceptions
  • Unallocated cash, settlement and approved adjustments

Every function in scope

  • Trace financial responses, records and agreed close scope.

Dependencies & modes

MANSOQ Core

Agreed mode: native / connected

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

RCM Reporting

Agreed operational views, exports and traceable worklists.

Scope and release review

Configuration checklist

  • Metric definitions and source lineage
  • Role-based queues and refresh windows
  • Financial totals, exports and management review

Every function in scope

  • Agreed operational views, exports and traceable worklists.

Dependencies & modes

MANSOQ Core

Agreed mode: native / connected

Acceptance & exceptions

For each function above, record exact configuration, its destination, owner, expected result and evidence. Test the complete journey plus missing data, access denial, correction, cancellation and outage. Unverified scope or a missing release adapter stays blocked until resolved.

CHOOSE THE PATH THAT FITS

Different settings. Clear decisions.

01New clinic
Assumptions to confirm

No historical data; one entity; outpatient and scheduling.

Sequence & acceptance

Build departments → staff/access → doctors → services → schedules. Mark migration not applicable with the source owner. Test arrival, consultation, orders, invoice and follow-up.

02Multi-specialty clinic
Assumptions to confirm

Shared identity; distinct specialties and clinic resources.

Sequence & acceptance

Map referrals, diagnostics and pharmacy across departments. Prevent doctor schedule overlap across clinics. Test a referral, returned result, prescription and financial follow-up.

03Hospital · 24-hour care
Assumptions to confirm

Inpatient, emergency, theatres and ICU need approved shift and escalation rules.

Sequence & acceptance

Create wards, beds and department access. Document full overnight rosters, midnight handover and escalation in the scheduling preparation file; approve the release-specific roster route before activation. Rehearse admission, transfer, procedure, medication, discharge and claim with downtime.

04Medical city / network
Assumptions to confirm

Entity and facility boundaries approved; shared identifiers explicitly governed.

Sequence & acceptance

Sequence one pilot then dependent sites. Separate access and finance by entity. Test cross-site referral and a forbidden cross-facility action. Accept each wave with its own reconciliation.

05TeleICU hub and spokes
Assumptions to confirm

Approved source context, device connection and bedside responsibility.

Sequence & acceptance

Map patient and device IDs, units and timestamps. Configure specialist coverage, remote review and bedside escalation. Test delayed feed, disconnect, reconnect and specialist handover.

06Home & palliative care
Assumptions to confirm

Consent, caregivers, visit coverage and connectivity are explicit.

Sequence & acceptance

Define service zones and team schedules. Configure approved care plans and escalation ownership. Rehearse home visit, offline contingency, follow-up, medication and financial close.

07Replace a legacy system
Assumptions to confirm

Data owner approves history, active work and read-only retention.

Sequence & acceptance

Inventory patient master, open encounters/orders, coverage, claims, unpaid balances and stock separately. Dry-run mappings, reject ambiguous identities, reconcile totals and rehearse a delta plus rollback.

08Connect an existing department
Assumptions to confirm

A source system keeps the agreed record ownership; mode is connected.

Sequence & acceptance

Define the message contract and identifier mappings. Test duplicate, rejected, delayed and reordered messages. Reconcile source/target counts; decide how work continues during an outage.

09Add a module or new branch
Assumptions to confirm

Existing records are preserved; commercial and configuration change is approved.

Sequence & acceptance

Record the new release and changed scope. Add only required master data through the approved product import route; bootstrap is for new tenants. Retest shared dependencies and accept the branch before switching work.

10RCM-only or managed revenue
Assumptions to confirm

Clinical source remains external; delegated authority and financial ownership are explicit.

Sequence & acceptance

Configure legal parties through policies, benefits, tariffs and routes. Import only approved clinical/charge context. Rehearse denial, partial payment, reversal, unmatched remittance and reconciliation.

11Connection or certification blocked
Assumptions to confirm

Production credential, licence, hardware or external approval is unavailable.

Sequence & acceptance

Keep the connection blocked, assign an owner and use the approved fallback. Continue independent preparation. Activate only after production evidence and repeat all affected end-to-end tests.

12Cutover failure / recovery
Assumptions to confirm

Rollback thresholds, backups and decision owner were agreed before launch.

Sequence & acceptance

Stop affected writes, preserve transaction evidence and follow the rehearsed fallback. Restore only the approved state; reconcile work during the outage, correct the defect and obtain a new go-live decision.

WHAT TO ENTER · WHAT HAPPENS NEXT

Real setup decisions, made clear.

Account owner also sees patients
Enter in the files

Use the administrator’s verified email in staff.csv with role=doctor. Use the same email in doctors.csv and its department assignment.

Validation & destination

One person, one seat. The clinical profile is created while the administrator retains account management.

One doctor, several clinics
Enter in the files

Repeat staff_email across two clinic rows: primary_clinic=true for Clinic A; false for Clinic B. Add distinct schedule_code values and non-overlapping times.

Validation & destination

Exactly one primary affiliation. Overlap is rejected even across facilities.

Two facilities with separate departments
Enter in the files

Save Riyadh first and Jeddah second. Use facility=1 for Riyadh and facility=2 for Jeddah in every dependent file. “Medicine” may appear once in each.

Validation & destination

Names are unique inside each facility; staff access is explicitly assigned. Do not reorder facilities after building references.

Reception may view bookings, not clinical notes
Enter in the files

Create ReceptionAppointments with permission_slug=can_list_schedule and can_list_booking, one row each. Every action must be one the Facility Admin role holds in a subscribed module; patient-chart actions such as can_list_patients are refused. Assign role_name=ReceptionAppointments to the reception email and department.

Validation & destination

Test permitted bookings and denied clinical access. The catalogue does not grant permissions automatically.

Morning and afternoon sessions
Enter in the files

Sunday rows: 08:00–12:00 and 13:00–17:00, slot_minutes=15, separate schedule_code values.

Validation & destination

The midday break stays unavailable; times and effective dates are validated.

Overnight and 24-hour clinical coverage
Enter in the files

Record the full 22:00–06:00 roster, next-day ownership, handover and escalation in scheduling.csv and the product review register. doctor_schedules.csv accepts same-day appointment availability only.

Validation & destination

The implementation owner maps the overnight roster to the selected release and tests midnight/week rollover before acceptance. Do not fake 24:00 or silently omit coverage.

Local service while SBS approval is pending
Enter in the files

service_code=CONSULT-001, gross_price_minor=15000, currency=SAR. Leave sbs_code, sbs_release and mapping_evidence all blank until approved.

Validation & destination

Draft SAR 150.00 local price. Missing SBS authority is tracked; uploading a price does not enable claims.

Partial packs and fractional stock
Enter in the files

Choose the approved UCUM unit first. For 2.5 units enter quantity=2.5; do not enter 2.5 boxes when the item unit means tablets. Repeat a lot across locations only with matching expiry and cost.

Validation & destination

Opening stock stays inactive until physical counts and units reconcile. Negative values and inconsistent lots are rejected.

Expired, recalled or quarantined stock
Enter in the files

List lot and expiry accurately. Document quarantine/disposition and release owner in inventory_opening.csv. Do not substitute a later expiry to make import pass.

Validation & destination

All opening lots are inactive. Product acceptance must test expiry, recall and no-dispense controls before activation.

Lab analyzer or radiology device
Enter in the files

Use asset_code, serial_number and the correct facility/department/location. Record protocol and version, identifier/unit mapping, connection owner and secure credential references in interfaces.csv.

Validation & destination

Creates an inactive asset. Test accepted/rejected messages, units, duplicates, downtime and recovery before hardware commissioning.

A dataset does not apply
Enter in the files

For no hardware in scope: dataset_id=assets_devices, decision=not_applicable, reason=No hardware included in signed scope [reference]. Leave assets_devices empty.

Validation & destination

Every applicable dataset receives a decision. An empty file alone is not a scope decision.

Legacy history and open financial work
Enter in the files

Create separate mappings for patient identity, active encounters, orders, balances and claims. Record source counts, rejected counts, totals, delta cutoff and owner-approved retention.

Validation & destination

Preparation uploads are stored as account evidence. Actual patient/member history uses an approved secure migration adapter and reconciliation, not public CSV examples.

Denial, partial payment and unmatched remittance
Enter in the files

Create one control per transaction type and test case. Enter source_total, target_total, agreed tolerance, exception_route and evidence_reference; preserve original claim identifiers on correction.

Validation & destination

Finance owns the resolution. Reversals, refunds and write-offs need authority and an audit trail; a failed reconciliation blocks acceptance.

Correct a failed CSV without losing other groups
Enter in the files

Upload to the matching group. Review row/column errors, fix the file and re-upload. Apply replaces only that group; Save validates links against the saved foundation.

Validation & destination

Nothing is applied from an invalid preview. A failed server save leaves the last saved setup intact; do not launch until it validates.

Update evidence after provisioning
Enter in the files

Return to Account setup → Implementation files & acceptance evidence. Upload the revised group and Save. Keep actual evidence references and approval owners.

Validation & destination

Each evidence save increments the account version and records the saving administrator and change digests. The frozen native bootstrap snapshot stays unchanged; operational configuration changes require the approved product change route.

REVENUE CYCLE · END TO END

Authority before activation.

Keep contract evidence, configuration and financial controls connected.

  1. 01

    Legal parties

    Legal identifiers, licences and risk-bearing vs delegated roles.

    organizations · Required data & evidence

    Create the legal payer, insurer, administrator/TPA and provider counterparties that every downstream contract, policy, tariff and integration route names.

    Required readiness fields
    • internal_code
    • legal_name_ar
    • legal_name_en
    • country_code
    • status=active
    • evidence_state in activation-grade evidence
    Additional fields to decide
    • commercial_registration
    • tax_number
    • license_number
    • parent_organization
    • contact_directory

    Evidence: Signed payer/administrator/provider legal registration or contract source document.

    Dependencies: none

    organizations
    insurer roles · Required data & evidence

    Mark which organization is the risk-bearing payer/insurer so policy, claim and settlement decisions do not infer that a TPA is the payer.

    Required readiness fields
    • organization
    • role=insurer
    • effective_from
    • status=active
    • evidence_state in activation-grade evidence
    Additional fields to decide
    • effective_to
    • network_scope
    • notes

    Evidence: Signed insurer agreement or payer master approval.

    Dependencies: organizations

    insurer roles
    tpa roles · Required data & evidence

    Declare delegated administrator/TPA roles when claims, eligibility, authorizations or portals are handled by an intermediary.

    Required readiness fields
    • organization
    • role=tpa
    • effective_from
    • status=active
    • evidence_state in activation-grade evidence
    Additional fields to decide
    • effective_to
    • portal_reference
    • escalation_matrix

    Evidence: Delegation clause, TPA agreement or insurer letter naming the TPA.

    Dependencies: organizations

    tpa roles
  2. 02

    Delegation

    Signed authority, deadlines, SLA and escalation.

    administration agreements · Required data & evidence

    Bind insurer-to-administrator delegation terms so routing and SLA ownership are explicit instead of inferred from names.

    Required readiness fields
    • insurer_org
    • administrator_org
    • effective_from
    • claim_submission_deadline
    • payment_sla
    • status=active
    • evidence_state in activation-grade evidence
    Additional fields to decide
    • effective_to
    • portal_url
    • authorization_sla
    • appeal_sla
    • contact_matrix

    Evidence: Signed administration agreement or delegated authority schedule.

    Dependencies: insurer_roles, tpa_roles

    administration agreements
  3. 03

    Provider contracts

    Effective dates, currency, settlement and amendments.

    provider contracts · Required data & evidence

    Record the signed hospital-provider commercial contract that gives authority for allowed pricing, billing windows and settlement terms.

    Required readiness fields
    • payer_or_insurer_org
    • provider_facility
    • contract_number
    • effective_from
    • currency
    • status=active
    • evidence_state in activation-grade evidence
    Additional fields to decide
    • effective_to
    • network_tier
    • claim_submission_deadline
    • payment_terms
    • appeal_terms

    Evidence: Signed provider contract and amendments.

    Dependencies: organizations, insurer_roles

    provider contracts
  4. 04

    Products & issued policies

    Product family, actual policyholder, period, limits and endorsements.

    insurance products · Required data & evidence

    Define the insurer's commercial product/plan family before issued policies and classes inherit or override benefit rules.

    Required readiness fields
    • insurer_org
    • product_code
    • product_name
    • jurisdiction
    • effective_from
    • status=active
    • evidence_state in activation-grade evidence
    Additional fields to decide
    • effective_to
    • network_type
    • product_category

    Evidence: Approved product schedule, CHI material or insurer plan sheet.

    Dependencies: insurer_roles

    insurance products
    issued policies · Required data & evidence

    Represent the actual policyholder/employer contract period, caps and endorsements that member coverages must point to.

    Required readiness fields
    • product
    • policy_number
    • policyholder
    • effective_from
    • effective_to
    • status=active
    • evidence_state in activation-grade evidence
    Additional fields to decide
    • global_policy_limit
    • endorsement_reference
    • renewal_reference
    • family_limit

    Evidence: Issued policy schedule and signed endorsements.

    Dependencies: insurance_products

    issued policies
  5. 05

    Benefit classes

    Class links, network tier and eligible member scope.

    benefit classes · Required data & evidence

    Create policy/class tiers such as VIP, A, B or Basic so benefits, limits and tariffs resolve at the correct insured class.

    Required readiness fields
    • product_or_policy
    • class_code
    • class_name
    • effective_from
    • status=active
    • evidence_state in activation-grade evidence
    Additional fields to decide
    • rank
    • room_grade
    • network_tier
    • annual_limit
    • requires_referral

    Evidence: Policy class schedule or benefit table.

    Dependencies: insurance_products, issued_policies

    benefit classes
  6. 06

    Benefits & exclusions

    Limits, deductibles, co-pay, service conditions and precedence.

    benefit rules · Required data & evidence

    Load covered/uncovered services, copays, deductibles, coinsurance, authorization triggers, limits, exclusions and overrides.

    Required readiness fields
    • benefit_class_or_policy_scope
    • service_code_or_group
    • coverage_decision
    • cost_share_rule
    • effective_from
    • status=active
    • evidence_state in activation-grade evidence
    Additional fields to decide
    • authorization_required
    • limit_scope
    • limit_amount
    • frequency_limit
    • diagnosis_restrictions
    • network_restrictions
    • exclusion_reason

    Evidence: Approved benefits table, exclusion list and policy endorsements.

    Dependencies: benefit_classes

    benefit rules
  7. 07

    Tariffs & assignments

    Gross vs contracted price, currency and effective dates.

    tariffs · Required data & evidence

    Define payer allowed-price lists separately from the hospital gross charge master so live invoices cannot confuse gross and allowed price.

    Required readiness fields
    • tariff_code
    • tariff_name
    • currency
    • effective_from
    • line_items
    • status=active
    • evidence_state in activation-grade evidence
    Additional fields to decide
    • effective_to
    • unit_basis
    • package_rules
    • drug_markup_rules
    • rounding_rules

    Evidence: Signed tariff/price-list attachment or approved amendment.

    Dependencies: provider_contracts

    tariffs
    tariff assignments · Required data & evidence

    Bind a contract/class/site/date context to exactly one applicable tariff precedence path.

    Required readiness fields
    • provider_contract
    • tariff
    • effective_from
    • priority
    • status=active
    • evidence_state in activation-grade evidence
    Additional fields to decide
    • effective_to
    • facility_site
    • department
    • benefit_class
    • network_tier

    Evidence: Contract tariff assignment schedule and approval.

    Dependencies: provider_contracts, benefit_classes, tariffs

    tariff assignments
  8. 08

    Networks & enrolment

    Provider participation, member identifiers, coverage periods and classes.

    networks · Required data & evidence

    Record network participation, exclusions and effective periods before coverage is used.

    Required readiness fields
    • network_code
    • provider_identifier
    • network_tier
    • effective_from
    • effective_to
    • contract_reference
    • approval_reference
    Additional fields to decide

      Evidence: 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.

      Dependencies: rcm_provider_contracts

      Provider networks & participation
      member coverage · Required data & evidence

      Prepare coverage mappings using synthetic references here; actual member identities belong in the approved secure migration route.

      Required readiness fields
      • source_member_reference
      • policy_reference
      • benefit_class_reference
      • network_code
      • effective_from
      • effective_to
      • identity_mapping_reference
      • approval_reference
      Additional fields to decide

        Evidence: 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.

        Dependencies: rcm_issued_policies, rcm_benefit_classes, rcm_networks

        Member coverage mapping
      • 09

        Rule publishing

        Evidence with workspace readback: draft review, activation-grade evidence, maker/checker and immutable version.

        rule publications · Required data & evidence

        Review rule precedence, exceptions and test evidence before immutable publication by authorized owners.

        Required readiness fields
        • rule_reference
        • rule_release
        • precedence
        • eligibility_condition
        • exclusion
        • limit_or_copay
        • test_case_reference
        • maker_reference
        • checker_reference
        • evidence_reference
        • publication_status
        Additional fields to decide

          Evidence: 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.

          Dependencies: rcm_benefit_rules, rcm_tariff_assignments, uat_cases

          Rules, exceptions & publication
        • 10

          NPHIES routing

          Certified package, transaction-specific route, secure credentials and response tests.

          nphies configurations · Required data & evidence

          Store facility identifiers, certified package pins and live-submission permission for the national NPHIES exchange.

          Required readiness fields
          • facility_identifier
          • environment=production
          • certification_status=certified
          • package_pin
          • allow_live_submission=true
          Additional fields to decide
          • onboarding_reference
          • certification_expiry
          • notes

          Evidence: NPHIES onboarding/certification evidence and package pin.

          Dependencies: production_endpoints, production_routing_rules

          nphies configurations
          production endpoints · Required data & evidence

          Configure the production integration endpoint and secret references without storing raw credentials in configuration rows.

          Required readiness fields
          • label
          • environment=production
          • endpoint_url
          • secret_reference
          • effective_from
          • status=active
          Additional fields to decide
          • effective_to
          • timeout_seconds
          • mTLS_profile

          Evidence: Integration onboarding letter and secret-manager reference.

          Dependencies: organizations

          production endpoints
          production routing rules · Required data & evidence

          Map production eligibility, prior authorization, claim and payment transactions to the correct endpoint and payer/administrator route.

          Required readiness fields
          • transaction_type in eligibility/prior_authorization/claim/payment
          • environment=production
          • endpoint
          • priority
          • effective_from
          • status=active
          Additional fields to decide
          • effective_to
          • payer_scope
          • retry_policy
          • fallback_queue

          Evidence: Approved production routing map and connectivity test evidence.

          Dependencies: production_endpoints, administration_agreements

          production routing rules
        • 11

          Finance & invoicing

          Taxpayer/device onboarding is excluded and handled outside this setup; charges, claim, remittance, reversal and control totals are evidence with workspace readback.

          zatca onboardings · Required data & evidence

          Bind each legal taxpayer to ZATCA solution certificate and CSID secret references for legal invoice clearance/reporting.

          Required readiness fields
          • taxpayer_organization
          • vat_registration_number
          • environment=production
          • solution_certificate_reference
          • csid_secret_reference
          • status=active
          Additional fields to decide
          • effective_to
          • invoice_type_scope
          • phase_wave_reference
          • clearance_endpoint
          • reporting_endpoint

          Evidence: ZATCA onboarding approval and secret-manager references.

          Dependencies: organizations

          zatca onboardings
          financial controls · Required data & evidence

          Reconcile normal, denied, partially paid, reversed and unmatched activity with explicit finance ownership.

          Required readiness fields
          • control_code
          • transaction_type
          • currency
          • source_total
          • target_total
          • tolerance
          • exception_route
          • evidence_reference
          • approval_reference
          Additional fields to decide

            Evidence: 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.

            Dependencies: service_billing, rcm_provider_contracts, uat_cases

            Revenue & reconciliation controls
          • 12

            Production acceptance

            Preflight evidence, complete transaction traces, financial reconciliation and accountable approval.

          Use the agreed production specifications; a public guide does not establish certification. Confirm privacy, retention and transfer decisions with the data owner.

          NPHIES official guide ↗ZATCA e-invoicing ↗SDAIA data protection ↗

          65 TEMPLATES · COLUMN BY COLUMN

          Bring your data. See where it goes.

          All templates + examples

          UTF-8 CSV · keep every header · one record for organization, operations, integrations and domain · up to 1,000 records per repeating dataset · maximum 1 MB per upload and 16 MB for the combined saved setup. Larger history needs approved batch migration; no rows are silently dropped. Identifiers are text; booleans are true/false; dates use YYYY-MM-DD. Quote commas and multiline values. Formula cells are rejected.

          Examples are synthetic, not approved configuration. Copy their structure, replace every placeholder and retain leading zeros. Preview errors use record numbers including the header; empty lines are ignored. Save validates linked records; launch reconciles imported counts.

          65 / 65
          Your organizationorganization.csv · 4 columnsAccount CSV import

          Use the registered details of your organization. Do not enter patient records here.

          Destination & acceptance: 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.

          Dependencies: Scope approval

          ColumnMeaningRequiredFormat / accepted valuesExample
          legal_nameRegistered organization name

          Enter registered organization name for your organization. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextExample Healthcare Organization
          registration_numberCommercial registration number

          Enter the stable commercial registration number as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextEXAMPLE-CR-001
          countryCountry

          Enter country for your organization. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSA / AE / BH / KW / QA / OM / EG / OTHERSA
          vat_numberTax registration number

          Enter the stable tax registration number as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          Decide if applicabletextOptional / leave blank
          Facilitiesfacilities.csv · 6 columnsAccount CSV import

          Add every facility included in your subscription. These become real, separate facilities in your app.

          Destination & acceptance: 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.

          Dependencies: Your organization

          ColumnMeaningRequiredFormat / accepted valuesExample
          nameFacility name

          Enter facility name for facilities. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextExample Facility
          typeFacility type

          Enter facility type for facilities. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yeshospital / clinic / polyclinic / laboratory / otherclinic
          license_numberFacility license

          Enter the stable facility license as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextEXAMPLE-LICENSE-001
          addressAddress

          Enter address for facilities. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextExample training address
          phonePhone

          Enter phone for facilities. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yestext+966500000000
          timezoneTime zone

          Enter time zone for facilities. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesAsia/Riyadh / Asia/Dubai / Asia/Qatar / Africa/Cairo / UTCAsia/Riyadh
          Departmentsdepartments.csv · 2 columnsAccount CSV import

          Create departments, consultation rooms, wards and beds. You can add more inside your app.

          Destination & acceptance: 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.

          Dependencies: Facilities

          ColumnMeaningRequiredFormat / accepted valuesExample
          facilityFacility number (starting at 1)

          Use the saved facility position, starting at 1. Reuse that number in every dependent file; do not renumber after imports.

          Yesinteger 1–10001
          nameDepartment name

          Enter department name for departments. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextExample Department
          Rooms, wards and bedslocations.csv · 4 columnsAccount CSV import

          Create departments, consultation rooms, wards and beds. You can add more inside your app.

          Destination & acceptance: 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.

          Dependencies: Facilities

          ColumnMeaningRequiredFormat / accepted valuesExample
          facilityFacility number

          Use the saved facility position, starting at 1. Reuse that number in every dependent file; do not renumber after imports.

          Yesinteger 1–10001
          nameLocation name

          Enter location name for rooms, wards and beds. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextExample Room
          kindType

          Enter type for rooms, wards and beds. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yesroom / ward / bedroom
          parentInside location (optional)

          Optional. Enter the exact name of the room or ward in this file and facility that contains this location, for example a ward for its rooms or a room for its beds. Leave blank for a top-level location. A bed cannot contain a location, and locations cannot contain each other in a loop.

          Decide if applicabletextOptional / leave blank
          Planned teamstaff.csv · 3 columnsAccount CSV import

          Your verified account becomes the facility administrator. Invite staff in the account portal; staff seats are enforced.

          Destination & acceptance: 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.

          Dependencies: Scope approval

          ColumnMeaningRequiredFormat / accepted valuesExample
          nameName

          Enter name for planned team. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextExample Staff
          emailWork email

          Enter work email for planned team. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yesemailstaff@example.invalid
          roleClinical role

          Enter clinical role for planned team. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yesfacility_admin / doctor / nurse / pharmacist / reception / billing / memberdoctor
          Operating preferencesoperations.csv · 7 columnsAccount CSV import

          Set working days, hours, patient identifiers and billing preferences. Your app starts with an empty patient database.

          Destination & acceptance: 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.

          Dependencies: Scope approval

          ColumnMeaningRequiredFormat / accepted valuesExample
          working_daysWorking days

          Enter working days for operating preferences. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yessun-thu / mon-fri / every-daysun-thu
          opening_timeOpening time (HH:MM)

          Enter opening time (hh:mm) for operating preferences. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yestext08:00
          closing_timeClosing time (HH:MM)

          Enter closing time (hh:mm) for operating preferences. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yestext17:00
          slot_minutesAppointment duration (minutes)

          Appointment length, an integer from 5 to 240 minutes. It must divide each availability window without a remainder.

          Yesinteger 5–24015
          patient_prefixPatient record prefix

          Enter patient record prefix for operating preferences. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicabletextEXAMPLE
          billing_currencyBilling currency

          Enter billing currency for operating preferences. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSARSAR
          languageDefault language

          Enter default language for operating preferences. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yesar / enen
          Integration readinessintegrations.csv · 4 columnsAccount CSV import

          Identify external systems. Credentials are entered securely in your own app after launch; approvals may be required before live use.

          Destination & acceptance: 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.

          Dependencies: Scope approval

          ColumnMeaningRequiredFormat / accepted valuesExample
          nphies_provider_idNPHIES provider identifier

          Enter the stable nphies provider identifier as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          Decide if applicabletextOptional / leave blank
          payer_namesPayers / insurers

          Enter payers / insurers for integration readiness. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicabletextOptional / leave blank
          accounting_systemAccounting system

          Enter accounting system for integration readiness. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicabletextOptional / leave blank
          migration_requiredExisting data needs migration

          Enter existing data needs migration for integration readiness. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicabletrue / falsefalse
          Your app addressdomain.csv · 2 columnsAccount CSV import

          Choose a unique address. Eligible packages can attach a domain after ownership and secure connection checks.

          Destination & acceptance: 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.

          Dependencies: Scope approval

          ColumnMeaningRequiredFormat / accepted valuesExample
          slugApp address, for example: my-clinic

          Enter app address, for example: my-clinic for your app address. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yestextexample-clinic
          custom_domainCustom domain (optional)

          Enter custom domain (optional) for your app address. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicabletextOptional / leave blank
          Roles & permissionsroles.csv · 2 columnsAccount CSV import

          Security roles and explicit permissions

          Destination & acceptance: 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.

          Dependencies: Scope approval

          ColumnMeaningRequiredFormat / accepted valuesExample
          role_nameRole name

          Use an installed facility role exactly, or the custom name defined in roles.csv. Repeat the custom name once per permitted action.

          YestextExample scheduling role
          permission_slugPermission identifier

          Choose an identifier from the permission catalogue that the Facility Admin role holds and that belongs to a module in your subscription. Global, organization, patient-chart and questionnaire permissions are not accepted. Test both allowed and denied actions.

          Yestextcan_list_schedule
          Users & department accessuser_access.csv · 4 columnsAccount CSV import

          Facility organization memberships

          Destination & acceptance: 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.

          Dependencies: Planned team · Departments · Roles & permissions

          ColumnMeaningRequiredFormat / accepted valuesExample
          staff_emailStaff email

          Use the same unique email as staff.csv. This identifies the planned person; upload does not send an invitation or create a password.

          Yesemailstaff@example.invalid
          facilityFacility number

          Use the saved facility position, starting at 1. Reuse that number in every dependent file; do not renumber after imports.

          Yesinteger 1–10001
          departmentDepartment name

          Copy the department name from departments.csv for this facility. Spaces and spelling must match; a similarly named department in another facility is a different record.

          YestextExample Department
          role_nameApproved role name

          Use an installed facility role exactly, or the custom name defined in roles.csv. Repeat the custom name once per permitted action.

          YestextDoctor
          Doctors & operational clinicsdoctors.csv · 7 columnsAccount CSV import

          User clinician profile and clinic affiliation

          Destination & acceptance: 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.

          Dependencies: Planned team · Departments · Rooms, wards and beds · Users & department access

          ColumnMeaningRequiredFormat / accepted valuesExample
          staff_emailDoctor email

          Use the same unique email as staff.csv. This identifies the planned person; upload does not send an invitation or create a password.

          Yesemailstaff@example.invalid
          facilityFacility number

          Use the saved facility position, starting at 1. Reuse that number in every dependent file; do not renumber after imports.

          Yesinteger 1–10001
          departmentDepartment

          Copy the department name from departments.csv for this facility. Spaces and spelling must match; a similarly named department in another facility is a different record.

          YestextExample Department
          clinic_locationClinic location

          Copy the saved clinic room. The doctor needs a matching affiliation before you add its schedule.

          YestextExample Room
          qualificationQualification

          Enter qualification for doctors & operational clinics. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTO-CONFIRM
          license_numberPractitioner licence

          Enter the stable practitioner licence as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextEXAMPLE-LICENSE-001
          primary_clinicPrimary clinic

          For a doctor with multiple affiliations, set exactly one row to true and all other rows to false. That row selects the home facility.

          Decide if applicablecheckboxtrue
          Services & department catalogueservices.csv · 7 columnsAccount CSV import

          Healthcare service directory

          Destination & acceptance: 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.

          Dependencies: Departments · Rooms, wards and beds

          ColumnMeaningRequiredFormat / accepted valuesExample
          service_codeLocal service code

          Your stable local service identifier. Reuse it in service_billing.csv; this is distinct from an SBS code.

          YestextEXAMPLE-SVC-001
          name_enEnglish name

          Enter english name for services & department catalogue. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextExample service
          name_arArabic name

          Enter arabic name for services & department catalogue. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yestextخدمة تدريبية
          facilityFacility number

          Use the saved facility position, starting at 1. Reuse that number in every dependent file; do not renumber after imports.

          Yesinteger 1–10001
          departmentDepartment

          Copy the department name from departments.csv for this facility. Spaces and spelling must match; a similarly named department in another facility is a different record.

          YestextExample Department
          locationLocation

          Copy a saved location in this facility. A room, ward or bed must exist before services, devices or stock reference it.

          YestextExample Room
          internal_typeService function

          Enter service function for services & department catalogue. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yesgeneral / scheduling / lab / pharmacy / storescheduling
          Service prices & SBS mappingservice_billing.csv · 7 columnsAccount CSV import

          Draft charge definitions with release-bound SBS codes

          Destination & acceptance: 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.

          Dependencies: Services & department catalogue

          ColumnMeaningRequiredFormat / accepted valuesExample
          facilityFacility number

          Use the saved facility position, starting at 1. Reuse that number in every dependent file; do not renumber after imports.

          Yesinteger 1–10001
          service_codeLocal service code

          Your stable local service identifier. Reuse it in service_billing.csv; this is distinct from an SBS code.

          YestextEXAMPLE-SVC-001
          gross_price_minorGross price in minor currency units

          Enter an integer in the currency’s minor unit: SAR 150.00 is 15000. This creates a draft local price, not a payer-contracted tariff.

          Yesinteger 0–214748364715000
          currencyCurrency

          Enter currency for service prices & sbs mapping. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSARSAR
          sbs_codeSBS code

          Enter a code from the licensed, approved SBS release together with sbs_release and mapping_evidence. Leave all three blank while mapping is pending.

          Decide if applicabletextOptional / leave blank
          sbs_releaseSBS release

          Enter sbs release for service prices & sbs mapping. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicabletextOptional / leave blank
          mapping_evidenceMapping approval reference

          Enter the traceable mapping approval reference held by the named owner. Use a secure record reference, never a credential or an invented approval. TO-CONFIRM means unresolved and cannot prove acceptance.

          Decide if applicabletextOptional / leave blank
          Doctor schedules · every departmentdoctor_schedules.csv · 11 columnsAccount CSV import

          Practitioner schedules and availability

          Destination & acceptance: 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.

          Dependencies: Doctors & operational clinics · Services & department catalogue

          ColumnMeaningRequiredFormat / accepted valuesExample
          schedule_codeUnique schedule code

          Enter the stable unique schedule code as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextEXAMPLE-SCH-001
          facilityFacility number

          Use the saved facility position, starting at 1. Reuse that number in every dependent file; do not renumber after imports.

          Yesinteger 1–10001
          staff_emailDoctor email

          Use the same unique email as staff.csv. This identifies the planned person; upload does not send an invitation or create a password.

          Yesemailstaff@example.invalid
          departmentDepartment

          Copy the department name from departments.csv for this facility. Spaces and spelling must match; a similarly named department in another facility is a different record.

          YestextExample Department
          clinic_locationClinic location

          Copy the saved clinic room. The doctor needs a matching affiliation before you add its schedule.

          YestextExample Room
          weekdayWeekday

          Enter weekday for doctor schedules · every department. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yesmon / tue / wed / thu / fri / sat / sunsun
          start_timeStart time

          Same-day weekly availability start, in the facility time zone. Breaks need separate non-overlapping rows. Overnight rosters require the approved workflow route, not a guessed midnight value.

          YesHH:MM08:00
          end_timeEnd time

          Same-day end, later than start_time. The duration must divide evenly by slot_minutes. Do not use 24:00 or a next-day end here.

          YesHH:MM12:00
          slot_minutesSlot duration

          Appointment length, an integer from 5 to 240 minutes. It must divide each availability window without a remainder.

          Yesinteger 5–24015
          valid_fromValid from

          Enter the actual valid from in YYYY-MM-DD. Confirm start/end ordering and the approved period; example dates are illustrative.

          YesYYYY-MM-DD2026-10-09
          valid_toValid to

          Enter the actual valid to in YYYY-MM-DD. Confirm start/end ordering and the approved period; example dates are illustrative.

          YesYYYY-MM-DD2027-10-09
          Inventory & medication itemsstock_items.csv · 7 columnsAccount CSV import

          Product knowledge catalogue

          Destination & acceptance: 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.

          Dependencies: Facilities

          ColumnMeaningRequiredFormat / accepted valuesExample
          item_codeUnique item code

          Enter the stable unique item code as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextEXAMPLE-ITEM-001
          facilityFacility number

          Use the saved facility position, starting at 1. Reuse that number in every dependent file; do not renumber after imports.

          Yesinteger 1–10001
          nameItem name

          Enter item name for inventory & medication items. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTraining consumable
          product_typeType

          Enter type for inventory & medication items. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yesmedication / consumable / nutritional_productconsumable
          unit_codeUCUM unit code

          Enter the stable ucum unit code as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          Yestext1
          code_systemTerminology system

          Enter the stable terminology system as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          Decide if applicabletextOptional / leave blank
          external_codeExternal code

          Enter the stable external code as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          Decide if applicabletextOptional / leave blank
          Stock lots & opening quantitiesstock_balances.csv · 7 columnsAccount CSV import

          Products, lots and location inventory balances

          Destination & acceptance: 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.

          Dependencies: Inventory & medication items · Rooms, wards and beds

          ColumnMeaningRequiredFormat / accepted valuesExample
          facilityFacility number

          Use the saved facility position, starting at 1. Reuse that number in every dependent file; do not renumber after imports.

          Yesinteger 1–10001
          item_codeItem code

          Enter the stable item code as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextEXAMPLE-ITEM-001
          locationStorage location

          Copy a saved location in this facility. A room, ward or bed must exist before services, devices or stock reference it.

          YestextExample Room
          lot_numberLot number

          Enter the stable lot number as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextEXAMPLE-LOT-001
          expiry_dateExpiry date

          Enter the actual expiry date in YYYY-MM-DD. Confirm start/end ordering and the approved period; example dates are illustrative.

          YesYYYY-MM-DD2027-10-09
          quantityOpening quantity

          Opening quantity in the stock item’s declared unit, not the pack label. Use a nonnegative decimal with at most six decimal places. Reconcile against the physical count.

          Yestext10
          purchase_priceUnit purchase price

          Purchase cost per declared unit. Use a nonnegative decimal; the same lot must use the same cost across locations. Confirm currency with finance.

          Yestext1.50
          Assets, devices & hardwareassets_devices.csv · 11 columnsAccount CSV import

          Device register, location and department assignment

          Destination & acceptance: 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.

          Dependencies: Departments · Rooms, wards and beds

          ColumnMeaningRequiredFormat / accepted valuesExample
          asset_codeUnique asset code

          Enter the stable unique asset code as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextEXAMPLE-LAB-001
          facilityFacility number

          Use the saved facility position, starting at 1. Reuse that number in every dependent file; do not renumber after imports.

          Yesinteger 1–10001
          departmentDepartment

          Copy the department name from departments.csv for this facility. Spaces and spelling must match; a similarly named department in another facility is a different record.

          YestextExample Department
          locationLocation

          Copy a saved location in this facility. A room, ward or bed must exist before services, devices or stock reference it.

          YestextExample Room
          nameDevice name

          Enter device name for assets, devices & hardware. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTraining laboratory analyser
          manufacturerManufacturer

          Enter manufacturer for assets, devices & hardware. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextExample manufacturer
          modelModel

          Enter model for assets, devices & hardware. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextEXAMPLE-MODEL
          serial_numberSerial number

          Enter the stable serial number as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextEXAMPLE-SERIAL
          care_typeProduct / department purpose

          Enter product / department purpose for assets, devices & hardware. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yestextlaboratory
          protocolInterface protocol and version

          Describe the agreed device/interface protocol and version. Creating an asset record does not connect hardware; complete commissioning and interface tests.

          Decide if applicabletextTO-CONFIRM
          maintenance_dueMaintenance due

          Enter the actual maintenance due in YYYY-MM-DD. Confirm start/end ordering and the approved period; example dates are illustrative.

          Decide if applicableYYYY-MM-DD2027-10-09
          Function settings · scheduling closuresproduct_settings.csv · 9 columnsAccount CSV import

          Registry function settings applied to native scheduling closures with readback

          Destination & acceptance: 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.

          Dependencies: Rooms, wards and beds

          ColumnMeaningRequiredFormat / accepted valuesExample
          facilityFacility number

          Use the saved facility position, starting at 1. Reuse that number in every dependent file; do not renumber after imports.

          Yesinteger 1–10001
          featureSelected feature ID

          Choose the selected product feature that owns the function setting. Your account template offers only features with a supported setting; scheduling owns scheduling closures.

          Yesschedulingscheduling
          function_keyFunction setting

          Choose a function setting from the supported registry. scheduling.closures closes booking for the stated dates and hours. Any other key, including retired free-form keys, is refused.

          Yesscheduling.closuresscheduling.closures
          nameClosure name

          A short name your team will recognise for this closure, up to 255 characters. Use one row per closure; nothing is pre-filled, so enter every closure your facility observes.

          YestextExample closure
          valid_fromFirst closed date

          The first closed date in YYYY-MM-DD, in the facility time zone. Enter your own dates; the example date is illustrative.

          YesYYYY-MM-DD2026-12-01
          valid_toLast closed date

          The last closed date in YYYY-MM-DD, the same as or after valid_from. A one-day closure repeats the same date.

          YesYYYY-MM-DD2026-12-01
          start_timeClosed from

          The time booking closes on each closed date, in 24-hour HH:MM and the facility time zone.

          YesHH:MM08:00
          end_timeClosed until

          The time booking reopens on each closed date, in HH:MM and later than start_time on the same day.

          YesHH:MM17:00
          locationRoom (blank closes the whole facility)

          Optional. Copy the name of a room saved for this facility to close only that room. Leave blank to close every room and clinician schedule of the facility.

          Decide if applicabletextExample Room
          Dataset completeness & exceptionsdataset_decisions.csv · 3 columnsAccount CSV import

          Account setup review and product import evidence

          Destination & acceptance: 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.

          Dependencies: Scope approval

          ColumnMeaningRequiredFormat / accepted valuesExample
          dataset_idDataset identifier

          Use a dataset from this account’s product step. Every applicable dataset needs one decision row, even when it is not used.

          Yestextservices
          decisionDecision

          provided requires at least one row in that dataset. not_applicable requires an empty dataset and an explicit scope reason.

          Yesprovided / not_applicableprovided
          reasonReason and approval

          Enter reason and approval for dataset completeness & exceptions. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTO-CONFIRM
          organizationsrcm_organizations.csv · 12 columnsProject record

          Create the legal payer, insurer, administrator/TPA and provider counterparties that every downstream contract, policy, tariff and integration route names.

          Destination & acceptance: 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.

          Dependencies: Scope approval

          ColumnMeaningRequiredFormat / accepted valuesExample
          internal_codeinternal code

          Use the exact source-backed identifier or name, up to 64 Unicode characters as required by the native field. Keep significant leading zeros and case. A valid cell records preparation; it does not establish approval or operational activation.

          YesSource-backed valueTO-CONFIRM
          legal_name_arlegal name ar

          Enter legal name ar for organizations. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueTO-CONFIRM
          legal_name_enlegal name en

          Enter legal name en for organizations. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueTO-CONFIRM
          country_codecountry code

          Enter the source-backed code using exactly 2 uppercase English letters. The example is illustrative and does not select a country or currency for you. Format validation does not verify registration or activate the prepared record.

          YesSource-backed valueSA
          statusstatus

          Enter status for organizations. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesReadiness condition: status=activedraft
          evidence_stateevidence state

          Enter the traceable evidence state held by the named owner. Use a secure record reference, never a credential or an invented approval. TO-CONFIRM means unresolved and cannot prove acceptance.

          YesReadiness condition: evidence_state in activation-grade evidenceabsent
          commercial_registrationcommercial registration

          Enter commercial registration for organizations. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          tax_numbertax number

          Enter the stable tax number as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          Decide if applicableSource-backed valueTO-CONFIRM
          license_numberlicense number

          Enter the stable license number as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          Decide if applicableSource-backed valueTO-CONFIRM
          parent_organizationparent organization

          Enter parent organization for organizations. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          contact_directorycontact directory

          Enter contact directory for organizations. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          approval_referenceApproval reference

          Enter the traceable approval reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-001
          insurer rolesrcm_insurer_roles.csv · 9 columnsProject record

          Mark which organization is the risk-bearing payer/insurer so policy, claim and settlement decisions do not infer that a TPA is the payer.

          Destination & acceptance: 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.

          Dependencies: organizations

          ColumnMeaningRequiredFormat / accepted valuesExample
          organizationorganization

          Enter organization for insurer roles. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueTO-CONFIRM
          rolerole

          Enter role for insurer roles. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesReadiness condition: role=insurerinsurer
          effective_fromeffective from

          Enter the actual effective from in Source-backed value. Confirm start/end ordering and the approved period; example dates are illustrative.

          YesSource-backed value2026-10-09
          statusstatus

          Enter status for insurer roles. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesReadiness condition: status=activedraft
          evidence_stateevidence state

          Enter the traceable evidence state held by the named owner. Use a secure record reference, never a credential or an invented approval. TO-CONFIRM means unresolved and cannot prove acceptance.

          YesReadiness condition: evidence_state in activation-grade evidenceabsent
          effective_toeffective to

          Enter the actual effective to in Source-backed value. Confirm start/end ordering and the approved period; example dates are illustrative.

          Decide if applicableSource-backed value2026-10-09
          network_scopenetwork scope

          Enter network scope for insurer roles. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          notesnotes

          Enter notes for insurer roles. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          approval_referenceApproval reference

          Enter the traceable approval reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-001
          tpa rolesrcm_tpa_roles.csv · 9 columnsProject record

          Declare delegated administrator/TPA roles when claims, eligibility, authorizations or portals are handled by an intermediary.

          Destination & acceptance: 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.

          Dependencies: organizations

          ColumnMeaningRequiredFormat / accepted valuesExample
          organizationorganization

          Enter organization for tpa roles. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueTO-CONFIRM
          rolerole

          Enter role for tpa roles. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesReadiness condition: role=tpatpa
          effective_fromeffective from

          Enter the actual effective from in Source-backed value. Confirm start/end ordering and the approved period; example dates are illustrative.

          YesSource-backed value2026-10-09
          statusstatus

          Enter status for tpa roles. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesReadiness condition: status=activedraft
          evidence_stateevidence state

          Enter the traceable evidence state held by the named owner. Use a secure record reference, never a credential or an invented approval. TO-CONFIRM means unresolved and cannot prove acceptance.

          YesReadiness condition: evidence_state in activation-grade evidenceabsent
          effective_toeffective to

          Enter the actual effective to in Source-backed value. Confirm start/end ordering and the approved period; example dates are illustrative.

          Decide if applicableSource-backed value2026-10-09
          portal_referenceportal reference

          Enter the traceable portal reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          Decide if applicableSource-backed valueEXAMPLE-REF-001
          escalation_matrixescalation matrix

          Enter escalation matrix for tpa roles. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          approval_referenceApproval reference

          Enter the traceable approval reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-002
          administration agreementsrcm_administration_agreements.csv · 13 columnsProject record

          Bind insurer-to-administrator delegation terms so routing and SLA ownership are explicit instead of inferred from names.

          Destination & acceptance: 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.

          Dependencies: insurer roles · tpa roles

          ColumnMeaningRequiredFormat / accepted valuesExample
          insurer_orginsurer org

          Enter insurer org for administration agreements. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueTO-CONFIRM
          administrator_orgadministrator org

          Enter administrator org for administration agreements. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueTO-CONFIRM
          effective_fromeffective from

          Enter the actual effective from in Source-backed value. Confirm start/end ordering and the approved period; example dates are illustrative.

          YesSource-backed value2026-10-09
          claim_submission_deadlineclaim submission deadline

          Enter claim submission deadline for administration agreements. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueTO-CONFIRM
          payment_slapayment sla

          Enter payment sla for administration agreements. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueTO-CONFIRM
          statusstatus

          Enter status for administration agreements. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesReadiness condition: status=activedraft
          evidence_stateevidence state

          Enter the traceable evidence state held by the named owner. Use a secure record reference, never a credential or an invented approval. TO-CONFIRM means unresolved and cannot prove acceptance.

          YesReadiness condition: evidence_state in activation-grade evidenceabsent
          effective_toeffective to

          Enter the actual effective to in Source-backed value. Confirm start/end ordering and the approved period; example dates are illustrative.

          Decide if applicableSource-backed value2026-10-09
          portal_urlportal url

          Enter portal url for administration agreements. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          authorization_slaauthorization sla

          Enter authorization sla for administration agreements. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          appeal_slaappeal sla

          Enter appeal sla for administration agreements. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          contact_matrixcontact matrix

          Enter contact matrix for administration agreements. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          approval_referenceApproval reference

          Enter the traceable approval reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-001
          provider contractsrcm_provider_contracts.csv · 13 columnsProject record

          Record the signed hospital-provider commercial contract that gives authority for allowed pricing, billing windows and settlement terms.

          Destination & acceptance: 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.

          Dependencies: organizations · insurer roles

          ColumnMeaningRequiredFormat / accepted valuesExample
          payer_or_insurer_orgpayer or insurer org

          Enter payer or insurer org for provider contracts. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueTO-CONFIRM
          provider_facilityprovider facility

          Enter provider facility for provider contracts. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueTO-CONFIRM
          contract_numbercontract number

          Enter the stable contract number as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YesSource-backed valueEXAMPLE-CONTRACT-001
          effective_fromeffective from

          Enter the actual effective from in Source-backed value. Confirm start/end ordering and the approved period; example dates are illustrative.

          YesSource-backed value2026-10-09
          currencycurrency

          Enter currency for provider contracts. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueSAR
          statusstatus

          Enter status for provider contracts. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesReadiness condition: status=activedraft
          evidence_stateevidence state

          Enter the traceable evidence state held by the named owner. Use a secure record reference, never a credential or an invented approval. TO-CONFIRM means unresolved and cannot prove acceptance.

          YesReadiness condition: evidence_state in activation-grade evidenceabsent
          effective_toeffective to

          Enter the actual effective to in Source-backed value. Confirm start/end ordering and the approved period; example dates are illustrative.

          Decide if applicableSource-backed value2026-10-09
          network_tiernetwork tier

          Enter network tier for provider contracts. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          claim_submission_deadlineclaim submission deadline

          Enter claim submission deadline for provider contracts. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          payment_termspayment terms

          Enter payment terms for provider contracts. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          appeal_termsappeal terms

          Enter appeal terms for provider contracts. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          approval_referenceApproval reference

          Enter the traceable approval reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-001
          insurance productsrcm_insurance_products.csv · 11 columnsProject record

          Define the insurer's commercial product/plan family before issued policies and classes inherit or override benefit rules.

          Destination & acceptance: 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.

          Dependencies: insurer roles

          ColumnMeaningRequiredFormat / accepted valuesExample
          insurer_orginsurer org

          Enter insurer org for insurance products. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueTO-CONFIRM
          product_codeproduct code

          Use the exact source-backed identifier or name, up to 64 Unicode characters as required by the native field. Keep significant leading zeros and case. A valid cell records preparation; it does not establish approval or operational activation.

          YesSource-backed valueTO-CONFIRM
          product_nameproduct name

          Enter product name for insurance products. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueTO-CONFIRM
          jurisdictionjurisdiction

          Enter the source-backed code using exactly 2 uppercase English letters. The example is illustrative and does not select a country or currency for you. Format validation does not verify registration or activate the prepared record.

          YesSource-backed valueSA
          effective_fromeffective from

          Enter the actual effective from in Source-backed value. Confirm start/end ordering and the approved period; example dates are illustrative.

          YesSource-backed value2026-10-09
          statusstatus

          Enter status for insurance products. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesReadiness condition: status=activedraft
          evidence_stateevidence state

          Enter the traceable evidence state held by the named owner. Use a secure record reference, never a credential or an invented approval. TO-CONFIRM means unresolved and cannot prove acceptance.

          YesReadiness condition: evidence_state in activation-grade evidenceabsent
          effective_toeffective to

          Enter the actual effective to in Source-backed value. Confirm start/end ordering and the approved period; example dates are illustrative.

          Decide if applicableSource-backed value2026-10-09
          network_typenetwork type

          Enter network type for insurance products. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          product_categoryproduct category

          Enter product category for insurance products. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          approval_referenceApproval reference

          Enter the traceable approval reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-001
          issued policiesrcm_issued_policies.csv · 12 columnsProject record

          Represent the actual policyholder/employer contract period, caps and endorsements that member coverages must point to.

          Destination & acceptance: 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.

          Dependencies: insurance products

          ColumnMeaningRequiredFormat / accepted valuesExample
          productproduct

          Enter product for issued policies. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueTO-CONFIRM
          policy_numberpolicy number

          Enter the stable policy number as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YesSource-backed valueEXAMPLE-POLICY
          policyholderpolicyholder

          Enter policyholder for issued policies. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueTO-CONFIRM
          effective_fromeffective from

          Enter the actual effective from in Source-backed value. Confirm start/end ordering and the approved period; example dates are illustrative.

          YesSource-backed value2026-10-09
          effective_toeffective to

          Enter the actual effective to in Source-backed value. Confirm start/end ordering and the approved period; example dates are illustrative.

          YesSource-backed value2026-10-09
          statusstatus

          Enter status for issued policies. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesReadiness condition: status=activedraft
          evidence_stateevidence state

          Enter the traceable evidence state held by the named owner. Use a secure record reference, never a credential or an invented approval. TO-CONFIRM means unresolved and cannot prove acceptance.

          YesReadiness condition: evidence_state in activation-grade evidenceabsent
          global_policy_limitglobal policy limit

          Enter global policy limit for issued policies. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          endorsement_referenceendorsement reference

          Enter the traceable endorsement reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          Decide if applicableSource-backed valueEXAMPLE-REF-001
          renewal_referencerenewal reference

          Enter the traceable renewal reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          Decide if applicableSource-backed valueEXAMPLE-REF-002
          family_limitfamily limit

          Enter family limit for issued policies. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          approval_referenceApproval reference

          Enter the traceable approval reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-003
          benefit classesrcm_benefit_classes.csv · 12 columnsProject record

          Create policy/class tiers such as VIP, A, B or Basic so benefits, limits and tariffs resolve at the correct insured class.

          Destination & acceptance: 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.

          Dependencies: insurance products · issued policies

          ColumnMeaningRequiredFormat / accepted valuesExample
          product_or_policyproduct or policy

          Enter product or policy for benefit classes. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueTO-CONFIRM
          class_codeclass code

          Use the exact source-backed identifier or name, up to 64 Unicode characters as required by the native field. Keep significant leading zeros and case. A valid cell records preparation; it does not establish approval or operational activation.

          YesSource-backed valueEXAMPLE-CLASS
          class_nameclass name

          Enter class name for benefit classes. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueTO-CONFIRM
          effective_fromeffective from

          Enter the actual effective from in Source-backed value. Confirm start/end ordering and the approved period; example dates are illustrative.

          YesSource-backed value2026-10-09
          statusstatus

          Enter status for benefit classes. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesReadiness condition: status=activedraft
          evidence_stateevidence state

          Enter the traceable evidence state held by the named owner. Use a secure record reference, never a credential or an invented approval. TO-CONFIRM means unresolved and cannot prove acceptance.

          YesReadiness condition: evidence_state in activation-grade evidenceabsent
          rankrank

          Enter rank for benefit classes. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          room_graderoom grade

          Enter room grade for benefit classes. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          network_tiernetwork tier

          Enter network tier for benefit classes. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          annual_limitannual limit

          Enter annual limit for benefit classes. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          requires_referralrequires referral

          Enter requires referral for benefit classes. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          approval_referenceApproval reference

          Enter the traceable approval reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-001
          benefit rulesrcm_benefit_rules.csv · 15 columnsProject record

          Load covered/uncovered services, copays, deductibles, coinsurance, authorization triggers, limits, exclusions and overrides.

          Destination & acceptance: 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.

          Dependencies: benefit classes

          ColumnMeaningRequiredFormat / accepted valuesExample
          benefit_class_or_policy_scopebenefit class or policy scope

          Enter benefit class or policy scope for benefit rules. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueTO-CONFIRM
          service_code_or_groupservice code or group

          Enter the stable service code or group as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YesSource-backed valueTO-CONFIRM
          coverage_decisioncoverage decision

          Enter coverage decision for benefit rules. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueTO-CONFIRM
          cost_share_rulecost share rule

          Enter cost share rule for benefit rules. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueTO-CONFIRM
          effective_fromeffective from

          Enter the actual effective from in Source-backed value. Confirm start/end ordering and the approved period; example dates are illustrative.

          YesSource-backed value2026-10-09
          statusstatus

          Enter status for benefit rules. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesReadiness condition: status=activedraft
          evidence_stateevidence state

          Enter the traceable evidence state held by the named owner. Use a secure record reference, never a credential or an invented approval. TO-CONFIRM means unresolved and cannot prove acceptance.

          YesReadiness condition: evidence_state in activation-grade evidenceabsent
          authorization_requiredauthorization required

          Enter authorization required for benefit rules. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          limit_scopelimit scope

          Enter limit scope for benefit rules. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          limit_amountlimit amount

          Enter limit amount for benefit rules. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          frequency_limitfrequency limit

          Enter frequency limit for benefit rules. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          diagnosis_restrictionsdiagnosis restrictions

          Enter diagnosis restrictions for benefit rules. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          network_restrictionsnetwork restrictions

          Enter network restrictions for benefit rules. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          exclusion_reasonexclusion reason

          Enter exclusion reason for benefit rules. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          approval_referenceApproval reference

          Enter the traceable approval reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-001
          tariffsrcm_tariffs.csv · 13 columnsProject record

          Define payer allowed-price lists separately from the hospital gross charge master so live invoices cannot confuse gross and allowed price.

          Destination & acceptance: 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.

          Dependencies: provider contracts

          ColumnMeaningRequiredFormat / accepted valuesExample
          tariff_codetariff code

          Use the exact source-backed identifier or name, up to 64 Unicode characters as required by the native field. Keep significant leading zeros and case. A valid cell records preparation; it does not establish approval or operational activation.

          YesSource-backed valueTO-CONFIRM
          tariff_nametariff name

          Use the exact source-backed identifier or name, up to 255 Unicode characters as required by the native field. Keep significant leading zeros and case. A valid cell records preparation; it does not establish approval or operational activation.

          YesSource-backed valueTO-CONFIRM
          currencycurrency

          Enter the source-backed code using exactly 3 uppercase English letters. The example is illustrative and does not select a country or currency for you. Format validation does not verify registration or activate the prepared record.

          YesSource-backed valueSAR
          effective_fromeffective from

          Enter the actual effective from in Source-backed value. Confirm start/end ordering and the approved period; example dates are illustrative.

          YesSource-backed value2026-10-09
          line_itemsline items

          Enter line items for tariffs. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueTO-CONFIRM
          statusstatus

          Enter status for tariffs. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesReadiness condition: status=activedraft
          evidence_stateevidence state

          Enter the traceable evidence state held by the named owner. Use a secure record reference, never a credential or an invented approval. TO-CONFIRM means unresolved and cannot prove acceptance.

          YesReadiness condition: evidence_state in activation-grade evidenceabsent
          effective_toeffective to

          Enter the actual effective to in Source-backed value. Confirm start/end ordering and the approved period; example dates are illustrative.

          Decide if applicableSource-backed value2026-10-09
          unit_basisunit basis

          Enter unit basis for tariffs. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          package_rulespackage rules

          Enter package rules for tariffs. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          drug_markup_rulesdrug markup rules

          Enter drug markup rules for tariffs. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          rounding_rulesrounding rules

          Enter rounding rules for tariffs. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          approval_referenceApproval reference

          Enter the traceable approval reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-001
          tariff assignmentsrcm_tariff_assignments.csv · 12 columnsProject record

          Bind a contract/class/site/date context to exactly one applicable tariff precedence path.

          Destination & acceptance: 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.

          Dependencies: provider contracts · benefit classes · tariffs

          ColumnMeaningRequiredFormat / accepted valuesExample
          provider_contractprovider contract

          Enter provider contract for tariff assignments. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueEXAMPLE-CONTRACT-001
          tarifftariff

          Enter tariff for tariff assignments. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueTO-CONFIRM
          effective_fromeffective from

          Enter the actual effective from in Source-backed value. Confirm start/end ordering and the approved period; example dates are illustrative.

          YesSource-backed value2026-10-09
          prioritypriority

          Enter priority for tariff assignments. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed value1
          statusstatus

          Enter status for tariff assignments. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesReadiness condition: status=activedraft
          evidence_stateevidence state

          Enter the traceable evidence state held by the named owner. Use a secure record reference, never a credential or an invented approval. TO-CONFIRM means unresolved and cannot prove acceptance.

          YesReadiness condition: evidence_state in activation-grade evidenceabsent
          effective_toeffective to

          Enter the actual effective to in Source-backed value. Confirm start/end ordering and the approved period; example dates are illustrative.

          Decide if applicableSource-backed value2026-10-09
          facility_sitefacility site

          Enter facility site for tariff assignments. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          departmentdepartment

          Copy the department name from departments.csv for this facility. Spaces and spelling must match; a similarly named department in another facility is a different record.

          Decide if applicableSource-backed valueTO-CONFIRM
          benefit_classbenefit class

          Enter benefit class for tariff assignments. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueEXAMPLE-CLASS
          network_tiernetwork tier

          Enter network tier for tariff assignments. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          approval_referenceApproval reference

          Enter the traceable approval reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-001
          nphies configurationsrcm_nphies_configurations.csv · 9 columnsProject record

          Store facility identifiers, certified package pins and live-submission permission for the national NPHIES exchange.

          Destination & acceptance: 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.

          Dependencies: production endpoints · production routing rules

          ColumnMeaningRequiredFormat / accepted valuesExample
          facility_identifierfacility identifier

          Enter the stable facility identifier as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YesSource-backed valueTO-CONFIRM
          environmentenvironment

          Enter environment for nphies configurations. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesReadiness condition: environment=productiontest
          certification_statuscertification status

          Enter certification status for nphies configurations. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesReadiness condition: certification_status=certifiednot_started
          package_pinpackage pin

          Enter package pin for nphies configurations. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueTO-CONFIRM
          allow_live_submissionallow live submission

          Enter allow live submission for nphies configurations. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesReadiness condition: allow_live_submission=truefalse
          onboarding_referenceonboarding reference

          Enter the traceable onboarding reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          Decide if applicableSource-backed valueEXAMPLE-REF-001
          certification_expirycertification expiry

          Enter certification expiry for nphies configurations. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueOptional / leave blank
          notesnotes

          Enter notes for nphies configurations. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          approval_referenceApproval reference

          Enter the traceable approval reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-002
          production endpointsrcm_production_endpoints.csv · 10 columnsProject record

          Configure the production integration endpoint and secret references without storing raw credentials in configuration rows.

          Destination & acceptance: 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.

          Dependencies: organizations

          ColumnMeaningRequiredFormat / accepted valuesExample
          labellabel

          Enter label for production endpoints. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueTO-CONFIRM
          environmentenvironment

          Enter environment for production endpoints. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesReadiness condition: environment=productiontest
          endpoint_urlendpoint url

          Enter endpoint url for production endpoints. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueTO-CONFIRM
          secret_referencesecret reference

          Enter the traceable secret reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YesSource-backed valueEXAMPLE-SECRET-REF-001
          effective_fromeffective from

          Enter the actual effective from in Source-backed value. Confirm start/end ordering and the approved period; example dates are illustrative.

          YesSource-backed value2026-10-09
          statusstatus

          Enter status for production endpoints. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesReadiness condition: status=activedraft
          effective_toeffective to

          Enter the actual effective to in Source-backed value. Confirm start/end ordering and the approved period; example dates are illustrative.

          Decide if applicableSource-backed value2026-10-09
          timeout_secondstimeout seconds

          Enter timeout seconds for production endpoints. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueOptional / leave blank
          mtls_profilemtls profile

          Enter mtls profile for production endpoints. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableReadiness condition: mTLS_profileTO-CONFIRM
          approval_referenceApproval reference

          Enter the traceable approval reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-001
          production routing rulesrcm_production_routing_rules.csv · 11 columnsProject record

          Map production eligibility, prior authorization, claim and payment transactions to the correct endpoint and payer/administrator route.

          Destination & acceptance: 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.

          Dependencies: production endpoints · administration agreements

          ColumnMeaningRequiredFormat / accepted valuesExample
          transaction_typetransaction type

          Enter transaction type for production routing rules. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesReadiness condition: transaction_type in eligibility/prior_authorization/claim/paymentclaim
          environmentenvironment

          Enter environment for production routing rules. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesReadiness condition: environment=productiontest
          endpointendpoint

          Enter endpoint for production routing rules. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueTO-CONFIRM
          prioritypriority

          Enter priority for production routing rules. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed value1
          effective_fromeffective from

          Enter the actual effective from in Source-backed value. Confirm start/end ordering and the approved period; example dates are illustrative.

          YesSource-backed value2026-10-09
          statusstatus

          Enter status for production routing rules. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesReadiness condition: status=activedraft
          effective_toeffective to

          Enter the actual effective to in Source-backed value. Confirm start/end ordering and the approved period; example dates are illustrative.

          Decide if applicableSource-backed value2026-10-09
          payer_scopepayer scope

          Enter payer scope for production routing rules. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          retry_policyretry policy

          Enter retry policy for production routing rules. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          fallback_queuefallback queue

          Enter fallback queue for production routing rules. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          approval_referenceApproval reference

          Enter the traceable approval reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-001
          zatca onboardingsrcm_zatca_onboardings.csv · 12 columnsProject record

          Bind each legal taxpayer to ZATCA solution certificate and CSID secret references for legal invoice clearance/reporting.

          Destination & acceptance: 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.

          Dependencies: organizations

          ColumnMeaningRequiredFormat / accepted valuesExample
          taxpayer_organizationtaxpayer organization

          Enter taxpayer organization for zatca onboardings. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesSource-backed valueTO-CONFIRM
          vat_registration_numbervat registration number

          Enter the stable vat registration number as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YesSource-backed valueTO-CONFIRM
          environmentenvironment

          Enter environment for zatca onboardings. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesReadiness condition: environment=productionTO-CONFIRM
          solution_certificate_referencesolution certificate reference

          Enter the traceable solution certificate reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YesSource-backed valueEXAMPLE-REF-001
          csid_secret_referencecsid secret reference

          Enter the traceable csid secret reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YesSource-backed valueEXAMPLE-SECRET-REF-001
          statusstatus

          Enter status for zatca onboardings. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesReadiness condition: status=activedraft
          effective_toeffective to

          Enter the actual effective to in Source-backed value. Confirm start/end ordering and the approved period; example dates are illustrative.

          Decide if applicableSource-backed value2026-10-09
          invoice_type_scopeinvoice type scope

          Enter invoice type scope for zatca onboardings. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          phase_wave_referencephase wave reference

          Enter the traceable phase wave reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          Decide if applicableSource-backed valueEXAMPLE-REF-002
          clearance_endpointclearance endpoint

          Enter clearance endpoint for zatca onboardings. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          reporting_endpointreporting endpoint

          Enter reporting endpoint for zatca onboardings. Leave blank only after deciding it is not applicable. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Decide if applicableSource-backed valueTO-CONFIRM
          approval_referenceApproval reference

          Enter the traceable approval reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-003
          Provider networks & participationrcm_networks.csv · 7 columnsProject record

          Record network participation, exclusions and effective periods before coverage is used.

          Destination & acceptance: 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.

          Dependencies: provider contracts

          ColumnMeaningRequiredFormat / accepted valuesExample
          network_codeNetwork code

          Enter the stable network code as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextEXAMPLE-NETWORK
          provider_identifierProvider legal identifier

          Enter the stable provider legal identifier as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextEXAMPLE-PROVIDER
          network_tierNetwork tier

          Enter network tier for provider networks & participation. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTO-CONFIRM
          effective_fromEffective from

          Enter the actual effective from in YYYY-MM-DD. Confirm start/end ordering and the approved period; example dates are illustrative.

          YesYYYY-MM-DD2026-10-10
          effective_toEffective to

          Enter the actual effective to in YYYY-MM-DD. Confirm start/end ordering and the approved period; example dates are illustrative.

          YesYYYY-MM-DD2027-10-09
          contract_referenceApproved contract

          Enter the traceable approved contract held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-CONTRACT-001
          approval_referenceApproval reference

          Enter the traceable approval reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-002
          Member coverage mappingrcm_member_coverage.csv · 8 columnsProject record

          Prepare coverage mappings using synthetic references here; actual member identities belong in the approved secure migration route.

          Destination & acceptance: 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.

          Dependencies: issued policies · benefit classes · Provider networks & participation

          ColumnMeaningRequiredFormat / accepted valuesExample
          source_member_referenceSource member reference

          Enter the traceable source member reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          Yestext; no patient identifiers in public examplesEXAMPLE-MEMBER
          policy_referenceIssued policy reference

          Enter the traceable issued policy reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-POLICY
          benefit_class_referenceBenefit class

          Enter the traceable benefit class held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-CLASS
          network_codeNetwork code

          Enter the stable network code as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextEXAMPLE-NETWORK
          effective_fromEffective from

          Enter the actual effective from in YYYY-MM-DD. Confirm start/end ordering and the approved period; example dates are illustrative.

          YesYYYY-MM-DD2026-10-10
          effective_toEffective to

          Enter the actual effective to in YYYY-MM-DD. Confirm start/end ordering and the approved period; example dates are illustrative.

          YesYYYY-MM-DD2027-10-09
          identity_mapping_referenceSecure identity mapping reference

          Enter the traceable secure identity mapping reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          Yestext; secure workspace referenceEXAMPLE-REF-001
          approval_referenceApproval reference

          Enter the traceable approval reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-002
          Rules, exceptions & publicationrcm_rule_publications.csv · 11 columnsProject record

          Review rule precedence, exceptions and test evidence before immutable publication by authorized owners.

          Destination & acceptance: 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.

          Dependencies: benefit rules · tariff assignments · Acceptance tests

          ColumnMeaningRequiredFormat / accepted valuesExample
          rule_referenceRule reference

          Enter the traceable rule reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-RULE
          rule_releaseRule release

          Enter rule release for rules, exceptions & publication. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTO-CONFIRM
          precedenceRule precedence

          Enter rule precedence for rules, exceptions & publication. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yesinteger1
          eligibility_conditionEligibility condition

          Enter eligibility condition for rules, exceptions & publication. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTO-CONFIRM
          exclusionExclusion / reason

          Enter exclusion / reason for rules, exceptions & publication. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTO-CONFIRM
          limit_or_copayLimit / deductible / copay

          Enter limit / deductible / copay for rules, exceptions & publication. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yestext; specify amount, unit and currencyTO-CONFIRM
          test_case_referenceTest case

          Enter the traceable test case held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-UAT
          maker_referencePrepared by

          Enter the traceable prepared by held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-001
          checker_referenceIndependent approval

          Enter the traceable independent approval held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-002
          evidence_referenceActivation evidence

          Enter the traceable activation evidence held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-003
          publication_statusPublication status

          Enter publication status for rules, exceptions & publication. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yesdraft / reviewed / approved / blockeddraft
          Revenue & reconciliation controlsrcm_financial_controls.csv · 9 columnsProject record

          Reconcile normal, denied, partially paid, reversed and unmatched activity with explicit finance ownership.

          Destination & acceptance: 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.

          Dependencies: Service prices & SBS mapping · provider contracts · Acceptance tests

          ColumnMeaningRequiredFormat / accepted valuesExample
          control_codeControl code

          Enter the stable control code as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextEXAMPLE-FIN-01
          transaction_typeTransaction type

          Enter transaction type for revenue & reconciliation controls. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yescharge / invoice / claim / remittance / reversal / refund / write_offclaim
          currencyCurrency

          Enter currency for revenue & reconciliation controls. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesISO 4217SAR
          source_totalExpected source total

          Enter expected source total for revenue & reconciliation controls. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yesdecimal1000.00
          target_totalObserved target total

          Enter observed target total for revenue & reconciliation controls. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yesdecimal1000.00
          toleranceApproved tolerance

          Enter approved tolerance for revenue & reconciliation controls. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yesdecimal; do not assume a tolerance0.00
          exception_routeException queue / owner

          Enter exception queue / owner for revenue & reconciliation controls. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextFinance review
          evidence_referenceReconciliation evidence

          Enter the traceable reconciliation evidence held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-001
          approval_referenceApproval reference

          Enter the traceable approval reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-002
          Project scopeproject_scope.csv · 8 columnsProject record

          Freeze products, versions, facilities, delivery mode and acceptance scope.

          Destination & acceptance: 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.

          Dependencies: Scope approval

          ColumnMeaningRequiredFormat / accepted valuesExample
          product_idCatalogue product ID

          Use a product ID or module key from your purchased package, such as outpatient. Setup rejects a product that is not in the package you bought.

          Yestextoutpatient
          releaseAgreed release

          Enter agreed release for project scope. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTO-CONFIRM
          modeOperating mode

          native runs the product inside MANSOQ. connected is accepted only after Integration readiness declares an integration: an accounting system, or a selected module that connects to an external system.

          Yesnative / connectednative
          facility_scopeFacility scope

          Enter all, or the saved facility numbers this row covers separated by commas, such as 1,2. Numbers start at 1 and cannot exceed the facility count of your package.

          Yestextall
          includedIncluded in this project

          true on the one row that includes a product in this project; a product may be included in at most one row. false records a product you decided to leave out.

          Yestrue / falsetrue
          owner_roleAccountable role

          Enter accountable role for project scope. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextProject owner
          acceptance_testAcceptance evidence

          Enter acceptance evidence for project scope. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextApproved end-to-end test
          approval_referenceApproval reference

          Enter the traceable approval reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-001
          Assumptions & decisionsassumptions_decisions.csv · 8 columnsProject record

          Keep each unresolved assumption visible with an owner and closure test.

          Destination & acceptance: 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.

          Dependencies: Project scope

          ColumnMeaningRequiredFormat / accepted valuesExample
          decision_idDecision ID

          Enter the stable decision id as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextDEC-001
          topicTopic

          Enter topic for assumptions & decisions. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextLegacy records
          assumptionProposed assumption

          Enter proposed assumption for assumptions & decisions. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextNo historical patient import until approved
          statusStatus

          proposed, open, approved or rejected. An approved decision needs the evidence reference of the record that approves it.

          Yesproposed / approved / rejected / openproposed
          owner_roleDecision owner

          Enter decision owner for assumptions & decisions. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextData owner
          evidence_referenceEvidence reference

          Enter the traceable evidence reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-001
          impact_if_wrongImpact if wrong

          Enter impact if wrong for assumptions & decisions. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextMigration scope must change
          closure_testClosure test

          Enter closure test for assumptions & decisions. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextSource inventory approved
          Access & approvalsaccess_matrix.csv · 7 columnsProject record

          Map roles to permitted actions and verify access across facility boundaries.

          Destination & acceptance: 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.

          Dependencies: Facilities · Planned team

          ColumnMeaningRequiredFormat / accepted valuesExample
          roleRole

          Enter role for access & approvals. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yestextdoctor
          facility_scopeFacility scope

          Enter facility scope for access & approvals. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextEXAMPLE-FACILITY-001
          resourceResource

          Enter resource for access & approvals. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextPatient record
          actionAction

          Enter action for access & approvals. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yestextread
          allowedAllowed

          Enter allowed for access & approvals. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yestrue / falsetrue
          approver_roleApprover

          Enter approver for access & approvals. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextSecurity owner
          evidence_referenceTest evidence

          Enter the traceable test evidence held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-001
          Service catalogueservice_catalogue.csv · 9 columnsApproved migration

          Define services and approved code mappings before orders, tariffs and interfaces.

          Destination & acceptance: 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.

          Dependencies: Departments

          ColumnMeaningRequiredFormat / accepted valuesExample
          service_codeLocal service code

          Your stable local service identifier. Reuse it in service_billing.csv; this is distinct from an SBS code.

          YestextEXAMPLE-SVC-001
          name_enEnglish name

          Enter english name for service catalogue. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextExample service
          name_arArabic name

          Enter arabic name for service catalogue. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yestextخدمة تدريبية
          department_codeDepartment code

          Enter the stable department code as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextEXAMPLE-DEPT-001
          unitUnit of service

          Enter unit of service for service catalogue. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTO-CONFIRM
          code_systemCode system

          Enter the stable code system as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextTO-CONFIRM
          releaseCatalogue release

          Enter catalogue release for service catalogue. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTO-CONFIRM
          external_codeApproved external mapping

          Enter the stable approved external mapping as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextTO-CONFIRM
          effective_fromEffective from

          Enter the actual effective from in YYYY-MM-DD. Confirm start/end ordering and the approved period; example dates are illustrative.

          YesYYYY-MM-DD2026-10-09
          Medication cataloguemedication_catalogue.csv · 10 columnsApproved migration

          Pharmacy-approved catalogue. Example records are for training and contain no dose advice.

          Destination & acceptance: 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.

          Dependencies: Service catalogue

          ColumnMeaningRequiredFormat / accepted valuesExample
          item_codeItem code

          Enter the stable item code as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextEXAMPLE-MED-001
          nameDisplay name

          Enter display name for medication catalogue. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTraining medication only
          code_systemCode system

          Enter the stable code system as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextTO-CONFIRM
          codeApproved code

          Enter the stable approved code as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextTO-CONFIRM
          strengthStrength with unit

          Enter strength with unit for medication catalogue. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTO-CONFIRM
          formDosage form

          Enter dosage form for medication catalogue. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTO-CONFIRM
          stock_unitStock unit

          Enter stock unit for medication catalogue. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTO-CONFIRM
          dispense_unitDispense unit

          Enter dispense unit for medication catalogue. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTO-CONFIRM
          conversion_factorApproved unit conversion

          Enter approved unit conversion for medication catalogue. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yesdecimal1
          releaseTerminology release

          Enter terminology release for medication catalogue. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTO-CONFIRM
          Opening inventoryinventory_opening.csv · 10 columnsApproved migration

          Load a signed stock count at a defined cutover time. Confirm whether zero cost is real before approval.

          Destination & acceptance: 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.

          Dependencies: Medication catalogue

          ColumnMeaningRequiredFormat / accepted valuesExample
          item_codeItem code

          Enter the stable item code as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextEXAMPLE-ITEM-001
          store_codeStore code

          Enter the stable store code as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextEXAMPLE-STORE-001
          lot_numberLot number

          Enter the stable lot number as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextEXAMPLE-LOT-001
          expiry_dateExpiry date

          Enter the actual expiry date in YYYY-MM-DD. Confirm start/end ordering and the approved period; example dates are illustrative.

          YesYYYY-MM-DD2027-10-09
          quantityOpening quantity

          Opening quantity in the stock item’s declared unit, not the pack label. Use a nonnegative decimal with at most six decimal places. Reconcile against the physical count.

          Yesdecimal10
          unitStock unit

          Enter stock unit for opening inventory. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTO-CONFIRM
          unit_costApproved unit cost

          Enter approved unit cost for opening inventory. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yesdecimal0
          currencyCurrency

          Enter currency for opening inventory. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesISO 4217SAR
          as_ofCount timestamp

          Enter count timestamp for opening inventory. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesISO 8601 with offset2026-10-09T08:00:00+03:00
          approval_referenceCount approval

          Enter the traceable count approval held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-001
          Clinical workflow configurationclinical_workflows.csv · 9 columnsProject record

          Record locally approved pathways, responsibilities and exception handling.

          Destination & acceptance: 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.

          Dependencies: Departments · Access & approvals

          ColumnMeaningRequiredFormat / accepted valuesExample
          workflow_idWorkflow ID

          Enter the stable workflow id as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextEXAMPLE-WF-001
          product_idProduct ID

          Use a product ID or module key from your purchased package, such as outpatient. Setup rejects a product that is not in the package you bought.

          Yestextoutpatient
          entry_eventEntry event

          Enter entry event for clinical workflow configuration. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextPatient arrival
          responsible_roleResponsible role

          Use an installed facility role name exactly, such as Doctor or Nurse, or a custom role name saved in your roles data. Setup rejects a role it cannot find.

          YestextNurse
          required_informationRequired information

          Enter required information for clinical workflow configuration. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextVerified identity and visit context
          next_eventNext event

          Enter next event for clinical workflow configuration. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextClinical consultation
          handover_ownerHandover owner

          Use an installed facility role name exactly, such as Doctor or Nurse, or a custom role name saved in your roles data. Setup rejects a role it cannot find.

          YestextDoctor
          exception_pathException path

          Enter exception path for clinical workflow configuration. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextIdentity mismatch to review
          approval_referenceWorkflow approval

          Enter the traceable workflow approval held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-001
          Scheduling configurationscheduling.csv · 10 columnsProject record

          Plan resource availability, overlap rules, closures and time zone handling.

          Destination & acceptance: 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.

          Dependencies: Operating preferences · Rooms, wards and beds · Planned team

          ColumnMeaningRequiredFormat / accepted valuesExample
          schedule_idSchedule ID

          Enter the stable schedule id as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextEXAMPLE-SCH-001
          facility_numberFacility number

          Enter the stable facility number as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          Yesinteger1
          department_nameDepartment

          Enter department for scheduling configuration. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextExample Department
          resource_nameStaff or room

          Enter staff or room for scheduling configuration. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextExample Room
          weekdayWeekday

          Enter weekday for scheduling configuration. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yessun / mon / tue / wed / thu / fri / satsun
          start_timeStart time

          Same-day weekly availability start, in the facility time zone. Breaks need separate non-overlapping rows. Overnight rosters require the approved workflow route, not a guessed midnight value.

          YesHH:MM08:00
          end_timeEnd time

          Same-day end, later than start_time. The duration must divide evenly by slot_minutes. Do not use 24:00 or a next-day end here.

          YesHH:MM17:00
          slot_minutesSlot duration

          Appointment length, an integer from 5 to 240 minutes. It must divide each availability window without a remainder.

          Yesinteger minutes15
          timezoneTime zone

          Enter time zone for scheduling configuration. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesIANA time zoneAsia/Riyadh
          approval_referenceScheduling approval

          Enter the traceable scheduling approval held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-001
          Interface specificationinterfaces.csv · 11 columnsProject record

          Define the agreed message contract. Store references to credentials, never the credentials themselves.

          Destination & acceptance: 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.

          Dependencies: Facilities · Service catalogue · Existing systems & versions

          ColumnMeaningRequiredFormat / accepted valuesExample
          interface_idInterface ID

          Enter the stable interface id as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextEXAMPLE-IF-001
          source_systemSource system

          Enter source system for interface specification. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextSRC-EPIC-001
          target_systemTarget system

          Enter target system for interface specification. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextMANSOQ
          directionDirection

          Enter direction for interface specification. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yesinbound / outbound / bidirectionalinbound
          protocol_versionProtocol and version

          Enter protocol and version for interface specification. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTO-CONFIRM
          message_scopeMessage scope

          Enter message scope for interface specification. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTO-CONFIRM
          identifier_mappingIdentifier mapping

          Enter the stable identifier mapping as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextTO-CONFIRM
          secret_referenceSecret manager reference

          Enter the traceable secret manager reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextREFERENCE-ONLY
          retry_policyRetry and duplicate policy

          Enter retry and duplicate policy for interface specification. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTO-CONFIRM
          failure_ownerFailure owner

          Enter failure owner for interface specification. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextIntegration owner
          test_referenceTest evidence

          Enter the traceable test evidence held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-001
          Migration mappingmigration_mapping.csv · 10 columnsProject record

          Approve target fields, transformations and merge rules against the exact application release.

          Destination & acceptance: 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.

          Dependencies: Project scope

          ColumnMeaningRequiredFormat / accepted valuesExample
          datasetDataset

          Enter dataset for migration mapping. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextPatient master
          source_fieldSource field

          Enter source field for migration mapping. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextLegacy identifier
          target_fieldTarget field

          Enter target field for migration mapping. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTO-CONFIRM
          transformationTransformation

          Enter transformation for migration mapping. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextPreserve as text
          identifier_systemIdentifier system

          Enter the stable identifier system as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextTO-CONFIRM
          requiredRequired

          Enter required for migration mapping. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yestrue / falsetrue
          null_policyNull policy

          Enter null policy for migration mapping. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextReject missing required ID
          dedup_keyDuplicate key

          Enter duplicate key for migration mapping. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextSource system + identifier
          validationValidation rule

          Enter validation rule for migration mapping. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextNo duplicate source keys
          approval_referenceMapping approval

          Enter the traceable mapping approval held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-001
          Migration batch logmigration_batches.csv · 10 columnsProject record

          Reconcile records and monetary or quantity totals, including rejects. Zero example counts do not mean a migration is complete.

          Destination & acceptance: 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.

          Dependencies: Migration mapping

          ColumnMeaningRequiredFormat / accepted valuesExample
          batch_idBatch ID

          Enter the stable batch id as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextEXAMPLE-BATCH-001
          datasetDataset

          Enter dataset for migration batch log. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextPatient master
          file_hashSHA-256 file hash

          Enter sha-256 file hash for migration batch log. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yes64 hex characters2825f4a89ff1b4df487b710b7af407ee007bf4b0213bf09a77352937d8c5b34c
          source_countSource records

          Enter source records for migration batch log. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yesinteger0
          accepted_countAccepted records

          Enter accepted records for migration batch log. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yesinteger0
          rejected_countRejected records

          Enter rejected records for migration batch log. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yesinteger0
          control_totalFinancial or stock total

          Enter financial or stock total for migration batch log. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yesdecimal0
          statusStatus

          Enter status for migration batch log. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yesstaged / validated / loaded / reconciled / rolled_backstaged
          rollback_referenceRollback evidence

          Enter the traceable rollback evidence held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-001
          approval_referenceBatch approval

          Enter the traceable batch approval held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-002
          Acceptance testsuat_cases.csv · 10 columnsProject record

          Record complete positive, negative, boundary, access and failure tests per product.

          Destination & acceptance: 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.

          Dependencies: Project scope · Clinical workflow configuration

          ColumnMeaningRequiredFormat / accepted valuesExample
          test_idTest ID

          Enter the stable test id as text. Preserve leading zeros, use the source owner’s assigned value and reuse it in linked records; EXAMPLE is not a real identifier.

          YestextUAT-001
          product_idProduct ID

          Use a product ID or module key from your purchased package, such as outpatient. Setup rejects a product that is not in the package you bought.

          Yestextoutpatient
          scenarioScenario

          Enter scenario for acceptance tests. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextVisit from arrival to financial follow-up
          preconditionsPreconditions

          Enter preconditions for acceptance tests. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextApproved setup and synthetic data
          actionsExact actions

          Enter exact actions for acceptance tests. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTO-CONFIRM
          expected_resultExpected result

          Enter expected result for acceptance tests. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTO-CONFIRM
          actual_resultActual result

          Enter actual result for acceptance tests. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextNOT-RUN
          statusStatus

          Enter status for acceptance tests. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yesnot_run / pass / fail / blockednot_run
          evidence_referenceEvidence reference

          Enter the traceable evidence reference held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-001
          approver_roleApprover

          Enter approver for acceptance tests. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextProduct owner
          Training & competencytraining.csv · 8 columnsProject record

          Verify that each role can perform normal work, exceptions and downtime tasks.

          Destination & acceptance: 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.

          Dependencies: Clinical workflow configuration · Acceptance tests

          ColumnMeaningRequiredFormat / accepted valuesExample
          roleRole

          Use an installed facility role name exactly, such as Doctor or Nurse, or a custom role name saved in your roles data. Setup rejects a role it cannot find.

          YestextNurse
          workflowWorkflow

          Enter workflow for training & competency. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextPatient registration
          trainer_roleTrainer

          Enter trainer for training & competency. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextSuperuser
          session_dateSession date

          Enter the actual session date in YYYY-MM-DD. Confirm start/end ordering and the approved period; example dates are illustrative.

          YesYYYY-MM-DD2026-10-09
          attendees_referenceAttendance evidence

          Enter the traceable attendance evidence held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-001
          competency_testCompetency test

          Enter competency test for training & competency. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextComplete a synthetic visit
          resultResult

          Enter result for training & competency. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          Yesnot_run / pass / failnot_run
          follow_upFollow-up

          Enter follow-up for training & competency. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTO-CONFIRM
          Cutover & rollbackcutover_runbook.csv · 9 columnsProject record

          Assign every cutover action, hold point, decision owner and tested rollback path.

          Destination & acceptance: 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.

          Dependencies: Acceptance tests · Migration batch log · Training & competency

          ColumnMeaningRequiredFormat / accepted valuesExample
          sequenceSequence

          A unique whole number that orders the cutover steps. Dependencies refer to these numbers.

          Yesinteger1
          actionAction

          Enter action for cutover & rollback. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextConfirm the change window
          owner_roleOwner

          Enter owner for cutover & rollback. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextProject owner
          dependencyDependency

          Optional. Leave blank for a step with no prerequisite, or list the smaller sequence numbers it waits for, separated by commas, such as 1,2. Each number must exist in this runbook, so the steps can never form a loop.

          Decide if applicabletextOptional / leave blank
          planned_timePlanned time

          Enter planned time for cutover & rollback. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YesISO 8601 with offset2026-10-09T20:00:00+03:00
          verificationVerification

          Enter verification for cutover & rollback. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTO-CONFIRM
          rollback_triggerRollback trigger

          Enter rollback trigger for cutover & rollback. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextCritical acceptance failure
          rollback_actionRollback action

          Enter rollback action for cutover & rollback. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTO-CONFIRM
          approval_referenceApproval

          Enter the traceable approval held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-001
          Support handoversupport_handover.csv · 9 columnsProject record

          Document ownership, customer-declared support targets, restore tests and certificate renewals. These values are your own declarations and are never a MANSOQ service level.

          Destination & acceptance: 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.

          Dependencies: Cutover & rollback

          ColumnMeaningRequiredFormat / accepted valuesExample
          serviceService

          Enter service for support handover. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextMANSOQ application
          owner_roleOwner

          Enter owner for support handover. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextSupport lead
          support_hoursCustomer-declared support hours

          Your own declared value for the operating handover. It is customer-declared and is never a MANSOQ service level or support commitment; only your signed agreement sets what MANSOQ provides.

          YestextTO-CONFIRM
          severityCustomer-declared severity

          Your own declared value for the operating handover. It is customer-declared and is never a MANSOQ service level or support commitment; only your signed agreement sets what MANSOQ provides.

          YestextTO-CONFIRM
          response_targetCustomer-declared response target

          Your own declared value for the operating handover. It is customer-declared and is never a MANSOQ service level or support commitment; only your signed agreement sets what MANSOQ provides.

          YestextTO-CONFIRM
          escalation_routeCustomer-declared escalation route

          Your own declared value for the operating handover. It is customer-declared and is never a MANSOQ service level or support commitment; only your signed agreement sets what MANSOQ provides.

          YestextTO-CONFIRM
          monitoring_referenceMonitoring evidence

          Enter the traceable monitoring evidence held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-001
          restore_test_referenceRestore test

          Enter the traceable restore test held by the named owner. Use a secure record reference, never a credential or an invented approval. Placeholders such as TO-CONFIRM, TBD or N/A are rejected; leave an optional cell empty until the record exists.

          YestextEXAMPLE-REF-002
          renewal_ownerCertificate or license owner

          Enter certificate or license owner for support handover. A value is required on every supplied row. Use the stated format and replace the synthetic example with the owner-confirmed value.

          YestextTO-CONFIRM
          Existing systems & versionssource_systems.csv · 10 columnsProject record

          Inventory every source EHR, department system, archive and ERP separately, including the exact installed product and licensed extraction route.

          Destination & acceptance: 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.

          Dependencies: Project scope

          ColumnMeaningRequiredFormat / accepted valuesExample
          system_idSystem ID

          A stable project identifier. Reuse it in scope, export, interface and reconciliation files; one row per environment/product.

          YestextSRC-EPIC-001
          vendorVendor

          Name the vendor, not the implementation partner. Use the directory or state your actual vendor.

          YestextEpic
          productInstalled product

          Copy the installed product name from the licence or admin inventory; Oracle Millennium and Soarian are different products.

          YestextEpic EHR
          releaseInstalled release

          Obtain the exact release/build and enabled modules from the source administrator; a vendor family name is insufficient.

          YestextTO-CONFIRM
          environmentEnvironment

          Identify test versus production versus archive. Test access does not grant production rights.

          Yestest / production / archivetest
          facility_scopeFacilities covered

          List approved facility codes separated by |. Confirm separate identifier namespaces and data boundaries.

          YestextEXAMPLE-FACILITY-001
          source_ownerSource administrator role

          Name the accountable role/team that can approve export, API access, downtime and source corrections.

          YestextSource EHR administrator
          export_routeApproved extraction route

          State the approved EHI export, FHIR bulk, HL7 feed or vendor extract with format and scope; do not assume a full export.

          YestextEHI export assessment pending
          licence_referenceLicence/access evidence

          Reference the approved contract or vendor ticket, including extraction/interface charges, restrictions and expiry.

          YestextEXAMPLE-REF-001
          specification_referenceRelease-specific specification

          Reference the vendor export dictionary/API specification for this installed release; public docs are a starting point.

          Yestexthttps://open.epic.com/TechnicalSpecifications
          Migration or coexistence scopetransition_scope.csv · 11 columnsProject record

          Choose the action and decide the system of record for every included data domain, facility and period.

          Destination & acceptance: 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.

          Dependencies: Existing systems & versions

          ColumnMeaningRequiredFormat / accepted valuesExample
          scope_idScope ID

          Unique scope decision ID, reused by export_inventory, integration_scopes and reconciliation.

          YestextSCOPE-001
          system_idSource system ID

          Copy system_id from source_systems.csv. Record separate rows for different source products.

          YestextSRC-EPIC-001
          actionTransition action

          Choose the intended transition. Coexistence needs an ongoing integration plan and one writer per domain.

          Yesmigration / integration / phased / consolidation / archive / carve_out / exit / recoverymigration
          data_domainData domain

          One domain per row, such as identity, encounters, medications, imaging, open claims or future appointments.

          YestextAppointments
          facility_scopeFacility boundary

          List approved facility codes separated by |. Never infer cross-entity permission from a shared network.

          YestextEXAMPLE-FACILITY-001
          history_fromHistory start date

          First included date, inclusive. State an approved boundary; archive anything outside it under a separate decision.

          YesYYYY-MM-DD2020-01-01
          history_toHistory end date

          Last included calendar date, inclusive. Record the precise delta watermark in migration_batches.csv.

          YesYYYY-MM-DD2026-10-09
          target_dispositionDestination

          native requires a verified target resource and adapter; archive retains read-only access; excluded requires an approved reason.

          Yesnative / connected / archive / excludednative
          system_of_recordAuthoritative system after cutover

          Specify which system owns writes for this domain before, during and after cutover. Avoid dual billing or duplicate prescribing.

          YestextMANSOQ after acceptance
          reasonInclusion or exclusion reason

          Explain the user need and exclusions. A blank row does not mean the data can be dropped.

          YestextFuture appointment continuity
          approval_referenceScope approval

          Reference data owner, clinical/finance owner and security approvals, including retention and transfer location.

          YestextEXAMPLE-REF-001
          Export files & checksumsexport_inventory.csv · 10 columnsApproved migration

          Register every vendor export file, attachment bundle and image batch without uploading its patient content to account setup.

          Destination & acceptance: 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.

          Dependencies: Migration or coexistence scope

          ColumnMeaningRequiredFormat / accepted valuesExample
          export_idExport ID

          Unique manifest entry for one file or documented archive part; reference related objects in the secure manifest.

          YestextEXPORT-001
          system_idSource system ID

          Copy the source system identifier; verify the correct environment before extraction.

          YestextSRC-EPIC-001
          scope_idScope ID

          Copy the approved transition scope; unscoped files must stay quarantined.

          YestextSCOPE-001
          formatActual format

          Record the real vendor format. Never rename NDJSON, TSV, XML or DICOM to CSV.

          YesCSV / TSV / NDJSON / XML / DICOM / PDF / native / otherTSV
          secure_file_referenceSecure file reference

          Reference the approved access-controlled storage location. Do not include patient names, public URLs, presigned tokens or file content.

          Yestextsecure-workspace://EXAMPLE/export-001
          sha256File SHA-256

          Compute the actual checksum after extraction and verify it after transfer. A checksum made of one repeated character is rejected; the example checksum is not acceptance evidence.

          Yes64 hex characters390a3d2a42b21012c44c65170f00cb0129db59d9b4b9e67193e195fa81c1bd09
          expected_recordsSource record/object count

          Obtain a source report count using the same filters. For DICOM, distinguish study, series and instance counts.

          Yesinteger120
          extracted_atExtraction timestamp

          Record the extraction time with offset; retain the source query, watermark and time-zone interpretation.

          YesISO 8601 with offset2026-10-09T18:00:00+03:00
          dictionary_referenceExport dictionary

          Record the matching schema version, data dictionary, encoding, delimiter, null markers and attachment index.

          YestextEXAMPLE-REF-001
          transfer_approvalTransfer approval

          Reference approved transfer method, encryption, retention, sender/receiver and access logging.

          YestextEXAMPLE-REF-002
          Patient matching rulesidentity_rules.csv · 9 columnsApproved migration

          Define matching policy and a secure crosswalk schema. Actual identifiers and patient-level mappings belong in the restricted migration workspace.

          Destination & acceptance: 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.

          Dependencies: Existing systems & versions · Migration or coexistence scope

          ColumnMeaningRequiredFormat / accepted valuesExample
          rule_idMatching rule ID

          Stable approved matching policy ID; do not store a patient ID here.

          YestextMATCH-001
          system_idSource system ID

          Identify the namespace owner. The same MRN text in two hospitals need not identify the same person.

          YestextSRC-EPIC-001
          identifier_namespaceIdentifier namespace

          Name the issuer/system URI and site boundary; preserve leading zeros in the secured crosswalk.

          YestextEXAMPLE-HOSPITAL-MRN
          match_methodMatching method

          Use verified identifiers only when valid for this scope. Potential and ambiguous matches require human review.

          Yesverified_identifier / reviewed_crosswalk / manual_reviewverified_identifier
          normalization_ruleNormalization rule

          Define exactly which transformations are permitted for names, identifiers and birth dates. Retain original values and provenance.

          YestextPreserve original; compare approved canonical form
          exception_policyAmbiguous/missing identity handling

          Include newborns, unknown emergency patients, temporary MRNs, changed identifiers, merged/unmerged records and deceased patients.

          YestextQuarantine and refer to identity steward
          crosswalk_referenceSecure crosswalk reference

          Reference the restricted patient-level source-to-target mapping, merge history and validation log; do not put actual crosswalk rows in this account CSV.

          Yestextsecure-workspace://EXAMPLE/crosswalk-schema
          approver_roleIdentity steward

          Name the accountable identity steward and escalation route before any merge.

          YestextHealth information management
          acceptance_referenceMatching evidence

          Reference review counts, unresolved conflicts, negative matching tests and signed acceptance.

          YestextEXAMPLE-REF-001
          Terminology & unit mappingsterminology_mapping.csv · 10 columnsApproved migration

          Map local codes, terminology releases, units and missing values without inventing clinical meaning.

          Destination & acceptance: 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.

          Dependencies: Migration or coexistence scope · Service catalogue

          ColumnMeaningRequiredFormat / accepted valuesExample
          mapping_idMapping ID

          Unique mapping ID for one code pair and release. Reuse it in the review and acceptance evidence.

          YestextMAP-TERM-001
          system_idSource system ID

          Identify the source whose local catalogue defined this code.

          YestextSRC-EPIC-001
          domainDomain

          Identify service, diagnosis, medication, lab test, specimen, unit, route, status or billing code.

          YestextLaboratory result
          source_systemSource code system

          State namespace and release, not only a display label. Verify licence rights before copying terminology.

          YestextEXAMPLE-LOCAL-LAB
          source_codeSource code

          Preserve the original code as text. This is a synthetic example, not an approved clinical code.

          YestextEXAMPLE-LAB-001
          target_systemTarget code system

          Required for exact, broader or narrower; leave empty when equivalence is unmapped. State the approved target code system and release; SBS mapping requires the licensed applicable release. Where an earlier setup still requires this cell, its value is ignored on unmapped rows.

          Decide if applicabletextOptional / leave blank
          target_codeTarget code

          Required for exact, broader or narrower; leave empty when equivalence is unmapped. Select only a reviewed equivalent and keep unresolved mappings unmapped rather than guessing a target code. Where an earlier setup still requires this cell, its value is ignored on unmapped rows.

          Decide if applicabletextOptional / leave blank
          equivalenceEquivalence

          Exact means approved semantic equivalence, not merely similar text; broader/narrower requires an explicit clinical decision.

          Yesexact / broader / narrower / unmappedunmapped
          unit_ruleUnit or conversion rule

          State source/target UCUM units, conversion precision, rounding and reference ranges; never convert clinical values without approval.

          YestextNo conversion until laboratory approval
          approval_referenceTerminology approval

          Reference clinical/pharmacy/laboratory/coding-owner review and the effective release/date.

          YestextEXAMPLE-REF-001
          Migration reconciliationdata_reconciliation.csv · 10 columnsApproved migration

          Prove completeness, identify rejected records and reconcile clinical, image, appointment and financial totals.

          Destination & acceptance: 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.

          Dependencies: Export files & checksums · Migration batch log

          ColumnMeaningRequiredFormat / accepted valuesExample
          check_idCheck ID

          Unique reconciliation check for a batch, scope and measure.

          YestextREC-001
          scope_idScope ID

          Copy the approved data scope and use exactly the same filters at source and target.

          YestextSCOPE-001
          batch_idMigration batch ID

          Copy the migration_batches.csv batch ID; record rerun version and watermark in its evidence.

          YestextEXAMPLE-BATCH-001
          measureReconciliation measure

          Specify the population and unit: records, DICOM instances, attachment bytes, account balance or a clinical field check.

          YestextFuture appointment count
          source_valueSource total

          Numeric total from the signed source report, not an estimate; negative financial balances require an agreed convention.

          Yesdecimal120
          target_valueTarget total

          Total successfully loaded/available at the target under the same scope; avoid counting replay duplicates.

          Yesdecimal118
          held_or_rejectedHeld/rejected total

          Document quarantined/excluded values with reasons; explain every difference instead of silently reducing the source total.

          Yesdecimal2
          toleranceApproved tolerance

          Set with the accountable owner before loading. Critical identity, medications and financial differences require explicit resolution.

          Yesdecimal0
          statusReview status

          Pass only after reconciliation and representative user review; an upload does not approve this evidence.

          Yesopen / passed / failed / waivedopen
          evidence_referenceReport/evidence

          Reference count reports, field-level comparisons, unresolved differences and owner-signed acceptance/waiver.

          YestextEXAMPLE-REF-001
          Integration scope & ownershipintegration_scopes.csv · 8 columnsProject record

          Declare only the selected domains, direction, cadence, authoritative writer and operations owner.

          Destination & acceptance: 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.

          Dependencies: Existing systems & versions · Migration or coexistence scope

          ColumnMeaningRequiredFormat / accepted valuesExample
          interface_idInterface ID

          Stable ID shared by contract, endpoint, message mapping and interface tests.

          YestextIFACE-001
          system_idExisting system ID

          Reference the existing source/peer system. MANSOQ is the other endpoint only when the approved target adapter exists.

          YestextSRC-EPIC-001
          scopeIntegration scope

          Choose one scope per row; use multiple rows for clinical and finance scopes instead of one vague all-data interface.

          Yesidentity_adt / clinical_read / orders_results / medications / appointments / revenue / imaging_devices / finance_inventory / ssoorders_results
          directionDirection

          Relative to MANSOQ: inbound from the peer, outbound to the peer, bidirectional only with per-event write ownership.

          Yesinbound / outbound / bidirectionalinbound
          cadenceDelivery pattern

          Specify the approved latency/schedule in the contract. Bulk export alone is not a real-time change feed.

          Yesevent / scheduled / on_demandevent
          system_of_recordAuthoritative writer

          State who can create, update, cancel or correct each entity. Document loop suppression and conflict handling.

          YestextExisting EHR owns orders; MANSOQ reviews results
          owner_roleIntegration operations owner

          Name the team accountable for delivery, retries, reconciliation and incident escalation.

          YestextIntegration operations
          approval_referenceScope approval

          Reference both system owners, clinical/finance owner, security review and release-specific acceptance.

          YestextEXAMPLE-REF-001
          Interface contractsinterface_contracts.csv · 10 columnsProject record

          Capture release-specific protocol, events, acknowledgements, conflict rules and operational limits before building an adapter.

          Destination & acceptance: 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.

          Dependencies: Integration scope & ownership

          ColumnMeaningRequiredFormat / accepted valuesExample
          interface_idInterface ID

          Copy integration_scopes.csv interface_id; use one approved contract revision per row.

          YestextIFACE-001
          protocolProtocol/profile

          State precise HL7/FHIR/DICOM/REST/file version, profiles/resources/event types and supported interactions; do not infer write support from read APIs.

          YestextHL7 v2.5.1 ORU assessment pending
          specification_referenceSpecification reference

          Reference both endpoint dictionaries and the approved target resource/adapter for the selected MANSOQ release.

          YestextEXAMPLE-REF-001
          acknowledgement_ruleAcknowledgement rule

          Define transport versus application ACK, business rejection, partial batches and completion status.

          YestextApplication acceptance before completed status
          deduplication_ruleReplay/idempotency rule

          State stable event keys, version rules, retention and safe retry behavior; retry must not duplicate encounters, results or invoices.

          YestextSource event ID plus version; retain processed receipt
          conflict_ruleConflict/correction rule

          Cover out-of-order messages, deletes, cancellations, corrected results and concurrent edits.

          YestextSource owns result corrections; quarantine identity conflicts
          retry_limitAutomatic retry limit

          Agreed nonnegative retry count. Route exhausted, poison and unsafe business events to a human-reviewed queue.

          Yesinteger3
          latency_targetAgreed delivery target

          Record the contract target and measurement point. No default clinical service-level commitment is implied.

          YestextTO-CONFIRM
          downtime_routeDowntime and replay route

          Identify who handles downtime, clinical escalation, recovery order and replay authorization.

          YestextDocumented downtime queue; replay after owner review
          approval_referenceContract approval

          Reference both vendors/site owners and release-specific approval, including licensing and acceptance tests.

          YestextEXAMPLE-REF-002
          Endpoint access registerendpoint_access.csv · 9 columnsProject record

          Record endpoint ownership, secure credential references, access scopes, rotation and network approvals without storing secrets.

          Destination & acceptance: 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.

          Dependencies: Interface contracts

          ColumnMeaningRequiredFormat / accepted valuesExample
          interface_idInterface ID

          Copy the interface_id shared by integration_scopes.csv and the approved interface_contracts.csv record for this release.

          YestextIFACE-001
          environmentEnvironment

          Separate test and production access. Promote with separate approval; never reuse sandbox access as production authorization.

          Yestest / productiontest
          endpoint_referenceEndpoint reference

          Reference the controlled endpoint inventory including HTTPS/host/port or DICOM AE titles. Never include token-bearing URLs.

          YestextEXAMPLE-ENDPOINT-REF-001
          auth_methodAuthentication method

          Record the approved OAuth/backend/SMART/SSO/mTLS/other method and exact vendor flow.

          Yestextvendor-approved-oauth
          credential_referenceCredential-manager reference

          Use the credential-manager record reference only. Do not place private keys, passwords, bearer tokens or certificate private material in this CSV.

          YestextEXAMPLE-SECRET-REF-001
          access_scopeGranted scopes/actions

          List least-privilege resources/actions plus facility/patient cohort boundaries. Denied-action tests are required.

          YestextTest-only read scope pending approval
          network_approvalNetwork/TLS evidence

          Reference firewall/allowlist, DNS, TLS/mTLS chain, server identity, hosting boundary and connectivity test.

          YestextEXAMPLE-REF-001
          rotation_ownerRotation owner

          Name who renews credentials/certificates and tests expiry/revocation before service interruption.

          YestextSecurity operations
          approval_referenceAccess approval

          Reference customer and vendor production onboarding approvals; an API key alone is insufficient.

          YestextEXAMPLE-REF-002
          Event & field mappingmessage_mapping.csv · 8 columnsProject record

          Map individual source fields and events to verified target operations with validation and rejected-data behavior.

          Destination & acceptance: 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.

          Dependencies: Interface contracts · Terminology & unit mappings

          ColumnMeaningRequiredFormat / accepted valuesExample
          interface_idInterface ID

          Copy the contract ID; map separately for each event/resource/version.

          YestextIFACE-001
          eventEvent/resource

          Name the source event and required state transition, including cancellations and corrections.

          YestextResult update
          source_pathSource field/path

          Copy from the source dictionary, not an assumed field name. Include cardinality and datatype in mapping evidence.

          YestextEXAMPLE-source-result-code
          target_pathVerified target field/action

          Reference the approved MANSOQ release resource/action and adapter. Public vendor FHIR does not make MANSOQ a generic FHIR ingest server.

          YestextTO-CONFIRM
          transform_ruleTransform/validation rule

          Describe exact code translation, timezone, precision, null handling, reference lookups and provenance.

          YestextApproved code and unit mapping; preserve source value
          requiredRequired field

          true means missing data must fail or quarantine according to the approved rejection policy.

          Yestrue / falsetrue
          rejection_routeInvalid-data handling

          Record the queue, owner, repair process and replay evidence; never silently substitute an invented clinical value.

          YestextQuarantine; notify interface owner; no clinical write
          approval_referenceMapping approval

          Reference clinical/technical/finance reviewers and acceptance cases for this exact mapping.

          YestextEXAMPLE-REF-001
          Interface acceptance testsinterface_tests.csv · 8 columnsProject record

          Test valid, denied, corrected, duplicated, delayed, failed and recovered events for each selected integration.

          Destination & acceptance: 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.

          Dependencies: Event & field mapping · Endpoint access register

          ColumnMeaningRequiredFormat / accepted valuesExample
          test_idTest ID

          Unique acceptance case; add separate rows for failures and recovery, not only the happy path.

          YestextIF-TEST-001
          interface_idInterface ID

          Reference the approved interface scope and contract.

          YestextIFACE-001
          scenarioScenario

          Describe the source state, event sequence, target state and responsible actor using synthetic test identities.

          YestextDuplicate corrected laboratory result
          fixture_referenceSynthetic test fixture

          Reference synthetic/de-identified fixtures approved for the test environment; no patient data in account setup.

          Yestextsecure-test://EXAMPLE/corrected-result
          expectedExpected behavior

          State measurable assertions for content, permissions, acknowledgement, deduplication, timing and reconciliation.

          YestextOne corrected result; no duplicate charge; receipt logged
          statusExecution status

          Record actual test state, not a planned pass. Production enablement requires acceptance evidence.

          Yesnot_run / passed / failed / blockednot_run
          evidence_referenceTest evidence

          Reference source/target receipts, timings, result comparisons, error queue and owner approval.

          YestextEXAMPLE-REF-001
          owner_roleTest owner

          Assign the reviewer who can approve clinical/financial correctness and operational recovery.

          YestextClinical and integration owners
          Archive, retention & exitarchive_retention.csv · 10 columnsProject record

          Keep approved access to excluded history and define contractual retention, restoration, exit and decommission conditions.

          Destination & acceptance: 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.

          Dependencies: Migration or coexistence scope · Migration reconciliation

          ColumnMeaningRequiredFormat / accepted valuesExample
          archive_idArchive ID

          Unique approved archive/exit package ID; reference each original source and release.

          YestextARCH-001
          system_idSource system ID

          Identify the system that generated the retained history and provenance.

          YestextSRC-EPIC-001
          scope_idScope ID

          Reference approved domains/date ranges and why they are retained rather than loaded natively.

          YestextSCOPE-001
          retention_ruleApproved retention rule

          Record the applicable jurisdiction, record class, retention trigger and legal holds. Do not assume a universal number of years.

          YestextTO-CONFIRM by records/privacy owner
          access_ruleRead-only access rule

          State permitted roles, purpose, facility restrictions, patient lookup method and audit ownership.

          YestextApproved care team access with audit
          restore_test_referenceArchive retrieval/restore test

          Reference sampled record, attachment and image retrieval plus tested backup restoration with timings.

          YestextEXAMPLE-REF-001
          exit_formatExit package format

          Agree schema, dictionary, identifiers, binaries, checksums, audit and key handover before contracting an exit.

          YestextTO-CONFIRM
          decommission_gateDecommission gate

          Source shutdown or deletion is a separate approved change after reconciliation, retention and recovery conditions are met.

          YestextAcceptance, legal hold review and archive access approved
          owner_roleArchive owner

          Name ongoing operational, privacy and access owners after the old application is retired.

          YestextRecords and privacy owners
          approval_referenceArchive/exit approval

          Reference approved retention, retrieval, exit, legal-hold and final decommission decisions.

          YestextEXAMPLE-REF-002
          Installed facility roles & permission identifiers

          Doctor · Staff · Nurse · Administrator · Facility Admin · Admin · Volunteer · Pharmacist · Billing Officer

          Custom roles use one row per permission. Global permissions are excluded; the backend checks the installed permission catalogue again.

          IdentifierPermissionContext
          can_create_facilityCan Create on FacilityFACILITY
          can_read_facilityCan Read on FacilityFACILITY
          can_update_facilityCan Update on FacilityFACILITY
          can_write_questionnaireCan Create/Update QuestionnairesQUESTIONNAIRE
          can_archive_questionnaireCan Archive QuestionnairesQUESTIONNAIRE
          can_read_questionnaireCan Read QuestionnairesQUESTIONNAIRE
          can_submit_questionnaireCan Submit QuestionnairesQUESTIONNAIRE
          can_manage_questionnaireCan Manage QuestionnairesQUESTIONNAIRE
          can_view_organizationCan View OrganizationsORGANIZATION
          can_create_organizationCan Create OrganizationsORGANIZATION
          can_delete_organizationCan Delete OrganizationsORGANIZATION
          can_manage_organizationCan Manage OrganizationsORGANIZATION
          can_manage_organization_usersCan Manage Users in an OrganizationORGANIZATION
          can_manage_connected_role_organizationsCan Manage Connected Role OrganizationsORGANIZATION
          can_list_organization_usersCan List Users in an OrganizationsORGANIZATION
          is_geo_adminIs Geo AdminORGANIZATION
          can_create_facility_organizationCan Create Facility OrganizationsFACILITY_ORGANIZATION
          can_create_facility_organization_rootCan Create Facility Organizations RootFACILITY_ORGANIZATION
          can_view_facility_organizationCan View Facility OrganizationsFACILITY_ORGANIZATION
          can_delete_facility_organizationCan Delete Facility OrganizationsFACILITY_ORGANIZATION
          can_manage_facility_organizationCan Manage Facility OrganizationsFACILITY_ORGANIZATION
          can_list_facility_organization_usersCan List Users in a Facility OrganizationsFACILITY_ORGANIZATION
          can_manage_facility_organization_usersCan Manage Users in a Facility OrganizationFACILITY_ORGANIZATION
          can_create_encounterCan Create encounterENCOUNTER
          can_list_encounterCan list encountersENCOUNTER
          can_write_encounterUpdate Encounter non clinicalENCOUNTER
          can_write_encounter_clinical_dataUpdate Encounter related clinical dataENCOUNTER
          can_read_encounterCan Read encounterENCOUNTER
          can_read_encounter_clinical_dataCan Read encounter related clinical dataENCOUNTER
          can_submit_encounter_questionnaireCan submit questionnaire about patient encountersPATIENT
          can_document_late_performanceCan document a late clinical performanceENCOUNTER
          can_create_patientCan Create PatientPATIENT
          can_write_patientCan Update a Patient's dataPATIENT
          can_list_patientsCan list patientsPATIENT
          can_view_clinical_dataCan view clinical data about patientsPATIENT
          can_view_questionnaire_responsesCan view questionnaire responses on patientPATIENT
          can_submit_patient_questionnaireCan submit questionnaire about patientsPATIENT
          can_create_userCan create User in careFACILITY
          can_list_userCan list Users in MANSOQFACILITY
          can_list_facility_locationsCan List Facility LocationsFACILITY
          can_write_facility_locationsCan Create/Update Facility LocationsFACILITY
          can_list_facility_location_organizationsCan List Facility Location OrganizationsFACILITY
          can_create_facility_location_organizationsCan Create/Update Facility Location OrganizationsFACILITY
          can_write_observation_definitionCan Create Observation Definition on FacilityFACILITY
          can_read_observation_definitionCan Read Observation DefinitionFACILITY
          can_list_devicesCan List Devices on FacilityFACILITY
          can_manage_device_associations_to_encountersCan Manage Device Associations to EncountersFACILITY
          can_manage_devicesCan Manage Devices on FacilityFACILITY
          can_write_specimen_definitionCan Create Specimen Definition on FacilityFACILITY
          can_read_specimen_definitionCan Read Specimen DefinitionFACILITY
          can_write_activity_definitionCan Create Activity Definition on FacilityFACILITY
          can_read_activity_definitionCan Read Activity DefinitionFACILITY
          can_write_service_requestCan Write Service Request on FacilityFACILITY
          can_read_service_requestCan Read Service RequestFACILITY
          can_write_healthcare_serviceCan Create Healthcare Service on FacilityFACILITY
          can_read_healthcare_serviceCan Read Healthcare ServiceFACILITY
          can_write_specimenCan Create Specimen on FacilityFACILITY
          can_read_specimenCan Read SpecimenFACILITY
          can_write_diagnostic_reportCan Create Diagnostic Report on FacilityFACILITY
          can_read_diagnostic_reportCan Read Diagnostic ReportFACILITY
          can_write_charge_item_definitionCan Create Charge Item Definition on FacilityFACILITY
          can_read_charge_item_definitionCan Read Charge Item DefinitionFACILITY
          can_set_charge_item_definitionCan Set Charge Item Definition on FacilityFACILITY
          can_create_negative_charge_itemCan Create Negative Charge ItemFACILITY
          can_create_charge_itemCan Create Charge ItemFACILITY
          can_update_charge_itemCan Update Charge ItemFACILITY
          can_read_charge_itemCan Read Charge ItemFACILITY
          can_cancel_charge_itemCan Cancel Charge ItemFACILITY
          can_create_accountCan Create AccountFACILITY
          can_update_accountCan Update AccountFACILITY
          can_read_accountCan Read AccountFACILITY
          can_write_payment_reconciliationCan Write Payment ReconciliationFACILITY
          can_read_payment_reconciliationCan Read Payment ReconciliationFACILITY
          can_destroy_payment_reconciliationCan Destroy Payment ReconciliationFACILITY
          can_write_invoiceCan Write InvoiceFACILITY
          can_read_invoiceCan Read InvoiceFACILITY
          can_destroy_invoiceCan Destroy InvoiceFACILITY
          can_manage_locked_invoiceCan Manage Locked InvoiceFACILITY
          can_read_rcm_configurationCan Read RCM ConfigurationFACILITY
          can_edit_rcm_configurationCan Edit RCM ConfigurationFACILITY
          can_import_rcm_configurationCan Import RCM ConfigurationFACILITY
          can_publish_rcm_configurationCan Publish RCM ConfigurationFACILITY
          can_confirm_rcm_bank_receiptCan Confirm RCM Bank ReceiptFACILITY
          can_manage_rcm_cashCan Manage RCM Bank CashFACILITY
          can_manage_rcm_claimsCan Manage RCM ClaimsFACILITY
          can_prepare_rcm_visitCan Prepare Insured VisitFACILITY
          can_read_registration_insuranceCan Read Registration InsuranceFACILITY
          can_manage_registration_insuranceCan Manage Registration InsuranceFACILITY
          can_manage_data_migrationCan Manage Data MigrationFACILITY
          can_review_migration_identityCan Review Migration IdentityFACILITY
          can_authorize_migration_cutoverCan Authorize Migration CutoverFACILITY
          can_manage_data_subject_requestsCan Manage Data Subject RequestsFACILITY
          can_export_patient_dataCan Export Patient DataFACILITY
          can_manage_automationCan Manage AutomationFACILITY
          can_view_operational_workCan View Operational WorkFACILITY
          can_resolve_operational_workCan Resolve Operational WorkFACILITY
          is_pharmacistPharmacist in MANSOQFACILITY
          read_medication_dispenseMedication Dispense ReadFACILITY
          write_medication_dispenseWrite Medication DispenseFACILITY
          can_write_product_knowledgeCan Create Product Knowledge on FacilityFACILITY
          can_read_product_knowledgeCan Read Product KnowledgeFACILITY
          can_write_productCan Create Product on FacilityFACILITY
          can_read_productCan Read ProductFACILITY
          can_write_supply_deliveryCan Create Supply Delivery on FacilityFACILITY
          can_read_supply_deliveryCan Read Supply DeliveryFACILITY
          can_write_external_supply_deliveryCan Create External Supply Delivery on FacilityFACILITY
          can_write_supply_requestCan Create Supply Request on FacilityFACILITY
          can_read_supply_requestCan Read Supply RequestFACILITY
          can_read_inventory_itemCan Read Inventory ItemFACILITY
          can_write_tag_configCan Create Tag Config on FacilityFACILITY
          can_apply_tag_configCan Apply Tag Config to ResourcesFACILITY
          can_read_tag_configCan Read Tag ConfigFACILITY
          can_write_templateCan Create Template on FacilityFACILITY
          can_read_templateCan Read TemplateFACILITY
          can_preview_templateCan Preview TemplateFACILITY
          can_view_template_schemaCan View Template SchemaFACILITY
          can_generate_report_from_templateCan generate report from templateFACILITY
          can_generate_report_for_completed_encounterCan generate report for completed encounterFACILITY
          can_write_patient_identifier_configCan Create Patient Identifier Config on FacilityFACILITY
          can_read_patient_identifier_configCan Read Patient Identifier ConfigFACILITY
          can_write_token_categoryCan Create on Token CategoryFACILITY
          can_list_token_categoryCan list token category on FacilityFACILITY
          can_write_tokenCan Create on TokenFACILITY
          can_list_tokenCan list token on ObjectFACILITY
          can_write_scheduleCan Create on ScheduleFACILITY
          can_list_scheduleCan list schedule on ObjectFACILITY
          can_list_bookingCan list bookings on ObjectFACILITY
          can_write_bookingCan update bookings on ObjectFACILITY
          can_reschedule_bookingCan reschedule bookings on ObjectFACILITY
          can_create_service_accountCan create service account in careFACILITY
          can_write_resource_categoryCan Create Resource Category on FacilityFACILITY
          can_read_resource_categoryCan Read Resource CategoryFACILITY
          can_write_questionnaire_response_templateCan Create/Update Questionnaire Response TemplatesQUESTIONNAIRE
          can_read_questionnaire_response_templateCan Read Questionnaire Response TemplatesQUESTIONNAIRE

          Implementation answers & references

          How do I implement MANSOQ from account setup to go-live?

          Agree products, release, facilities and data boundaries. Import foundation setup first, then product data with validated references. Approve interfaces and migration mappings, rehearse clinical and financial workflows and exceptions, reconcile totals, accept cutover and recovery, then hand over monitored support. Each stage identifies owners, required files and an acceptance gate.

          Explore the details
          Which CSV templates can I download and upload?

          Use templates for departments, users, roles and permissions, services and SBS mappings, doctors and schedules, assets, stock, devices and selected-product configuration. Download the matching sample and field dictionary. Setup files use the account import route; evidence registers and migration manifests have separately identified destinations. Validate before committing any import.

          Explore the details
          How do I migrate Epic, TrakCare or Oracle Health to MANSOQ?

          Confirm the exact installed product and release and obtain authorized exports and dictionaries. Inventory clinical, operational, financial and attachment domains separately; preserve source identifiers. Approve the target adapter, mapping and test cohort, reconcile records and balances, rehearse final deltas and rollback, then accept the cutover. A FHIR clinical extract alone may not include schedules, claims, balances or images.

          Explore the details
          Source-system migration, integration & file referenceExplore all frequently asked questions