Delivery & services
Agree responsibilities, volume and accountable follow-up.
Managed Revenue People Services
Specify delegated revenue tasks, authorized users, provider and payer boundaries and service coverage. Name the organization that retains each clinical, contractual and financial decision.
Establish source access, work queues and the documents needed for eligibility, coding, authorization or claim tasks. Approve handover rules and quality checks before processing live work.
Perform only the agreed tasks through authorized workflows. Route missing clinical evidence, contracting questions and payer disputes to the retained owner and keep submission authority explicit.
Reconcile completed work, remittance and outstanding exceptions with the provider. Review agreed measures, support coverage and change requests against the service terms without promising unsupported financial outcomes.
Your configuration
Use the registered details of your organization. Do not enter patient records here.
Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.
| Column | Required | Format | Example |
|---|---|---|---|
Registered organization namelegal_name | Yes | text | Example Healthcare Organization |
Commercial registration numberregistration_number | Yes | text | EXAMPLE-CR-001 |
Countrycountry | Yes | SA / AE / BH / KW / QA / OM / EG / OTHER | SA |
Tax registration numbervat_number | Optional | text | — |
Add every facility included in your subscription. These become real, separate facilities in your app.
Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.
Load / review first: Your organization
| Column | Required | Format | Example |
|---|---|---|---|
Facility namename | Yes | text | Example Facility |
Facility typetype | Yes | hospital / clinic / polyclinic / laboratory / other | clinic |
Facility licenselicense_number | Yes | text | EXAMPLE-LICENSE-001 |
Addressaddress | Yes | text | Example training address |
Phonephone | Yes | text | +966500000000 |
Time zonetimezone | Yes | Asia/Riyadh / Asia/Dubai / Asia/Qatar / Africa/Cairo / UTC | Asia/Riyadh |
Create departments, consultation rooms, wards and beds. You can add more inside your app.
Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.
Load / review first: Facilities
| Column | Required | Format | Example |
|---|---|---|---|
Facility number (starting at 1)facility | Yes | integer 1–1000 | 1 |
Department namename | Yes | text | Example Department |
Create departments, consultation rooms, wards and beds. You can add more inside your app.
Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.
Load / review first: Facilities
| Column | Required | Format | Example |
|---|---|---|---|
Facility numberfacility | Yes | integer 1–1000 | 1 |
Location namename | Yes | text | Example Room |
Typekind | Yes | room / ward / bed | room |
Inside location (optional)parent | Optional | text | — |
Your verified account becomes the facility administrator. Invite staff in the account portal; staff seats are enforced.
Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.
| Column | Required | Format | Example |
|---|---|---|---|
Namename | Yes | text | Example Staff |
Work emailemail | Yes | staff@example.invalid | |
Clinical rolerole | Yes | facility_admin / doctor / nurse / pharmacist / reception / billing / member | doctor |
Healthcare service directory
Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.
Load / review first: Departments · Rooms, wards and beds
| Column | Required | Format | Example |
|---|---|---|---|
Local service codeservice_code | Yes | text | EXAMPLE-SVC-001 |
English namename_en | Yes | text | Example service |
Arabic namename_ar | Yes | text | خدمة تدريبية |
Facility numberfacility | Yes | integer 1–1000 | 1 |
Departmentdepartment | Yes | text | Example Department |
Locationlocation | Yes | text | Example Room |
Service functioninternal_type | Yes | general / scheduling / lab / pharmacy / store | scheduling |
Draft charge definitions with release-bound SBS codes
Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.
Load / review first: Services & department catalogue
| Column | Required | Format | Example |
|---|---|---|---|
Facility numberfacility | Yes | integer 1–1000 | 1 |
Local service codeservice_code | Yes | text | EXAMPLE-SVC-001 |
Gross price in minor currency unitsgross_price_minor | Yes | integer 0–2147483647 | 15000 |
Currencycurrency | Yes | SAR | SAR |
SBS codesbs_code | Optional | text | — |
SBS releasesbs_release | Optional | text | — |
Mapping approval referencemapping_evidence | Optional | text | — |
Registry function settings applied to native scheduling closures with readback
Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.
Load / review first: Rooms, wards and beds
| Column | Required | Format | Example |
|---|---|---|---|
Facility numberfacility | Yes | integer 1–1000 | 1 |
Selected feature IDfeature | Yes | scheduling | scheduling |
Function settingfunction_key | Yes | scheduling.closures | scheduling.closures |
Closure namename | Yes | text | Example closure |
First closed datevalid_from | Yes | YYYY-MM-DD | 2026-12-01 |
Last closed datevalid_to | Yes | YYYY-MM-DD | 2026-12-01 |
Closed fromstart_time | Yes | HH:MM | 08:00 |
Closed untilend_time | Yes | HH:MM | 17:00 |
Room (blank closes the whole facility)location | Optional | text | Example Room |
Create the legal payer, insurer, administrator/TPA and provider counterparties that every downstream contract, policy, tariff and integration route names.
Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.
| Column | Required | Format | Example |
|---|---|---|---|
internal codeinternal_code | Yes | Source-backed value | TO-CONFIRM |
legal name arlegal_name_ar | Yes | Source-backed value | TO-CONFIRM |
legal name enlegal_name_en | Yes | Source-backed value | TO-CONFIRM |
country codecountry_code | Yes | Source-backed value | SA |
statusstatus | Yes | Readiness condition: status=active | draft |
evidence stateevidence_state | Yes | Readiness condition: evidence_state in activation-grade evidence | absent |
commercial registrationcommercial_registration | Optional | Source-backed value | TO-CONFIRM |
tax numbertax_number | Optional | Source-backed value | TO-CONFIRM |
license numberlicense_number | Optional | Source-backed value | TO-CONFIRM |
parent organizationparent_organization | Optional | Source-backed value | TO-CONFIRM |
contact directorycontact_directory | Optional | Source-backed value | TO-CONFIRM |
Approval referenceapproval_reference | Yes | text | EXAMPLE-REF-001 |
Mark which organization is the risk-bearing payer/insurer so policy, claim and settlement decisions do not infer that a TPA is the payer.
Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.
Load / review first: organizations
| Column | Required | Format | Example |
|---|---|---|---|
organizationorganization | Yes | Source-backed value | TO-CONFIRM |
rolerole | Yes | Readiness condition: role=insurer | insurer |
effective fromeffective_from | Yes | Source-backed value | 2026-10-09 |
statusstatus | Yes | Readiness condition: status=active | draft |
evidence stateevidence_state | Yes | Readiness condition: evidence_state in activation-grade evidence | absent |
effective toeffective_to | Optional | Source-backed value | 2026-10-09 |
network scopenetwork_scope | Optional | Source-backed value | TO-CONFIRM |
notesnotes | Optional | Source-backed value | TO-CONFIRM |
Approval referenceapproval_reference | Yes | text | EXAMPLE-REF-001 |
Declare delegated administrator/TPA roles when claims, eligibility, authorizations or portals are handled by an intermediary.
Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.
Load / review first: organizations
| Column | Required | Format | Example |
|---|---|---|---|
organizationorganization | Yes | Source-backed value | TO-CONFIRM |
rolerole | Yes | Readiness condition: role=tpa | tpa |
effective fromeffective_from | Yes | Source-backed value | 2026-10-09 |
statusstatus | Yes | Readiness condition: status=active | draft |
evidence stateevidence_state | Yes | Readiness condition: evidence_state in activation-grade evidence | absent |
effective toeffective_to | Optional | Source-backed value | 2026-10-09 |
portal referenceportal_reference | Optional | Source-backed value | EXAMPLE-REF-001 |
escalation matrixescalation_matrix | Optional | Source-backed value | TO-CONFIRM |
Approval referenceapproval_reference | Yes | text | EXAMPLE-REF-002 |
Bind insurer-to-administrator delegation terms so routing and SLA ownership are explicit instead of inferred from names.
Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.
Load / review first: insurer roles · tpa roles
| Column | Required | Format | Example |
|---|---|---|---|
insurer orginsurer_org | Yes | Source-backed value | TO-CONFIRM |
administrator orgadministrator_org | Yes | Source-backed value | TO-CONFIRM |
effective fromeffective_from | Yes | Source-backed value | 2026-10-09 |
claim submission deadlineclaim_submission_deadline | Yes | Source-backed value | TO-CONFIRM |
payment slapayment_sla | Yes | Source-backed value | TO-CONFIRM |
statusstatus | Yes | Readiness condition: status=active | draft |
evidence stateevidence_state | Yes | Readiness condition: evidence_state in activation-grade evidence | absent |
effective toeffective_to | Optional | Source-backed value | 2026-10-09 |
portal urlportal_url | Optional | Source-backed value | TO-CONFIRM |
authorization slaauthorization_sla | Optional | Source-backed value | TO-CONFIRM |
appeal slaappeal_sla | Optional | Source-backed value | TO-CONFIRM |
contact matrixcontact_matrix | Optional | Source-backed value | TO-CONFIRM |
Approval referenceapproval_reference | Yes | text | EXAMPLE-REF-001 |
Record the signed hospital-provider commercial contract that gives authority for allowed pricing, billing windows and settlement terms.
Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.
Load / review first: organizations · insurer roles
| Column | Required | Format | Example |
|---|---|---|---|
payer or insurer orgpayer_or_insurer_org | Yes | Source-backed value | TO-CONFIRM |
provider facilityprovider_facility | Yes | Source-backed value | TO-CONFIRM |
contract numbercontract_number | Yes | Source-backed value | EXAMPLE-CONTRACT-001 |
effective fromeffective_from | Yes | Source-backed value | 2026-10-09 |
currencycurrency | Yes | Source-backed value | SAR |
statusstatus | Yes | Readiness condition: status=active | draft |
evidence stateevidence_state | Yes | Readiness condition: evidence_state in activation-grade evidence | absent |
effective toeffective_to | Optional | Source-backed value | 2026-10-09 |
network tiernetwork_tier | Optional | Source-backed value | TO-CONFIRM |
claim submission deadlineclaim_submission_deadline | Optional | Source-backed value | TO-CONFIRM |
payment termspayment_terms | Optional | Source-backed value | TO-CONFIRM |
appeal termsappeal_terms | Optional | Source-backed value | TO-CONFIRM |
Approval referenceapproval_reference | Yes | text | EXAMPLE-REF-001 |
Reconcile normal, denied, partially paid, reversed and unmatched activity with explicit finance ownership.
Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.
Load / review first: Service prices & SBS mapping · provider contracts · Acceptance tests
| Column | Required | Format | Example |
|---|---|---|---|
Control codecontrol_code | Yes | text | EXAMPLE-FIN-01 |
Transaction typetransaction_type | Yes | charge / invoice / claim / remittance / reversal / refund / write_off | claim |
Currencycurrency | Yes | ISO 4217 | SAR |
Expected source totalsource_total | Yes | decimal | 1000.00 |
Observed target totaltarget_total | Yes | decimal | 1000.00 |
Approved tolerancetolerance | Yes | decimal; do not assume a tolerance | 0.00 |
Exception queue / ownerexception_route | Yes | text | Finance review |
Reconciliation evidenceevidence_reference | Yes | text | EXAMPLE-REF-001 |
Approval referenceapproval_reference | Yes | text | EXAMPLE-REF-002 |
Freeze products, versions, facilities, delivery mode and acceptance scope.
Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.
| Column | Required | Format | Example |
|---|---|---|---|
Catalogue product IDproduct_id | Yes | text | outpatient |
Agreed releaserelease | Yes | text | TO-CONFIRM |
Operating modemode | Yes | native / connected | native |
Facility scopefacility_scope | Yes | text | all |
Included in this projectincluded | Yes | true / false | true |
Accountable roleowner_role | Yes | text | Project owner |
Acceptance evidenceacceptance_test | Yes | text | Approved end-to-end test |
Approval referenceapproval_reference | Yes | text | EXAMPLE-REF-001 |
Map roles to permitted actions and verify access across facility boundaries.
Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.
Load / review first: Facilities · Planned team
| Column | Required | Format | Example |
|---|---|---|---|
Rolerole | Yes | text | doctor |
Facility scopefacility_scope | Yes | text | EXAMPLE-FACILITY-001 |
Resourceresource | Yes | text | Patient record |
Actionaction | Yes | text | read |
Allowedallowed | Yes | true / false | true |
Approverapprover_role | Yes | text | Security owner |
Test evidenceevidence_reference | Yes | text | EXAMPLE-REF-001 |
Record locally approved pathways, responsibilities and exception handling.
Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.
Load / review first: Departments · Access & approvals
| Column | Required | Format | Example |
|---|---|---|---|
Workflow IDworkflow_id | Yes | text | EXAMPLE-WF-001 |
Product IDproduct_id | Yes | text | outpatient |
Entry evententry_event | Yes | text | Patient arrival |
Responsible roleresponsible_role | Yes | text | Nurse |
Required informationrequired_information | Yes | text | Verified identity and visit context |
Next eventnext_event | Yes | text | Clinical consultation |
Handover ownerhandover_owner | Yes | text | Doctor |
Exception pathexception_path | Yes | text | Identity mismatch to review |
Workflow approvalapproval_reference | Yes | text | EXAMPLE-REF-001 |
Approve target fields, transformations and merge rules against the exact application release.
Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.
Load / review first: Project scope
| Column | Required | Format | Example |
|---|---|---|---|
Datasetdataset | Yes | text | Patient master |
Source fieldsource_field | Yes | text | Legacy identifier |
Target fieldtarget_field | Yes | text | TO-CONFIRM |
Transformationtransformation | Yes | text | Preserve as text |
Identifier systemidentifier_system | Yes | text | TO-CONFIRM |
Requiredrequired | Yes | true / false | true |
Null policynull_policy | Yes | text | Reject missing required ID |
Duplicate keydedup_key | Yes | text | Source system + identifier |
Validation rulevalidation | Yes | text | No duplicate source keys |
Mapping approvalapproval_reference | Yes | text | EXAMPLE-REF-001 |
Reconcile records and monetary or quantity totals, including rejects. Zero example counts do not mean a migration is complete.
Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.
Load / review first: Migration mapping
| Column | Required | Format | Example |
|---|---|---|---|
Batch IDbatch_id | Yes | text | EXAMPLE-BATCH-001 |
Datasetdataset | Yes | text | Patient master |
SHA-256 file hashfile_hash | Yes | 64 hex characters | 2825f4a89ff1b4df487b710b7af407ee007bf4b0213bf09a77352937d8c5b34c |
Source recordssource_count | Yes | integer | 0 |
Accepted recordsaccepted_count | Yes | integer | 0 |
Rejected recordsrejected_count | Yes | integer | 0 |
Financial or stock totalcontrol_total | Yes | decimal | 0 |
Statusstatus | Yes | staged / validated / loaded / reconciled / rolled_back | staged |
Rollback evidencerollback_reference | Yes | text | EXAMPLE-REF-001 |
Batch approvalapproval_reference | Yes | text | EXAMPLE-REF-002 |
Record complete positive, negative, boundary, access and failure tests per product.
Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.
Load / review first: Project scope · Clinical workflow configuration
| Column | Required | Format | Example |
|---|---|---|---|
Test IDtest_id | Yes | text | UAT-001 |
Product IDproduct_id | Yes | text | outpatient |
Scenarioscenario | Yes | text | Visit from arrival to financial follow-up |
Preconditionspreconditions | Yes | text | Approved setup and synthetic data |
Exact actionsactions | Yes | text | TO-CONFIRM |
Expected resultexpected_result | Yes | text | TO-CONFIRM |
Actual resultactual_result | Yes | text | NOT-RUN |
Statusstatus | Yes | not_run / pass / fail / blocked | not_run |
Evidence referenceevidence_reference | Yes | text | EXAMPLE-REF-001 |
Approverapprover_role | Yes | text | Product owner |
Verify that each role can perform normal work, exceptions and downtime tasks.
Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.
Load / review first: Clinical workflow configuration · Acceptance tests
| Column | Required | Format | Example |
|---|---|---|---|
Rolerole | Yes | text | Nurse |
Workflowworkflow | Yes | text | Patient registration |
Trainertrainer_role | Yes | text | Superuser |
Session datesession_date | Yes | YYYY-MM-DD | 2026-10-09 |
Attendance evidenceattendees_reference | Yes | text | EXAMPLE-REF-001 |
Competency testcompetency_test | Yes | text | Complete a synthetic visit |
Resultresult | Yes | not_run / pass / fail | not_run |
Follow-upfollow_up | Yes | text | TO-CONFIRM |
Assign every cutover action, hold point, decision owner and tested rollback path.
Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.
Load / review first: Acceptance tests · Migration batch log · Training & competency
| Column | Required | Format | Example |
|---|---|---|---|
Sequencesequence | Yes | integer | 1 |
Actionaction | Yes | text | Confirm the change window |
Ownerowner_role | Yes | text | Project owner |
Dependencydependency | Optional | text | — |
Planned timeplanned_time | Yes | ISO 8601 with offset | 2026-10-09T20:00:00+03:00 |
Verificationverification | Yes | text | TO-CONFIRM |
Rollback triggerrollback_trigger | Yes | text | Critical acceptance failure |
Rollback actionrollback_action | Yes | text | TO-CONFIRM |
Approvalapproval_reference | Yes | text | EXAMPLE-REF-001 |
Document ownership, customer-declared support targets, restore tests and certificate renewals. These values are your own declarations and are never a MANSOQ service level.
Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.
Load / review first: Cutover & rollback
| Column | Required | Format | Example |
|---|---|---|---|
Serviceservice | Yes | text | MANSOQ application |
Ownerowner_role | Yes | text | Support lead |
Customer-declared support hourssupport_hours | Yes | text | TO-CONFIRM |
Customer-declared severityseverity | Yes | text | TO-CONFIRM |
Customer-declared response targetresponse_target | Yes | text | TO-CONFIRM |
Customer-declared escalation routeescalation_route | Yes | text | TO-CONFIRM |
Monitoring evidencemonitoring_reference | Yes | text | EXAMPLE-REF-001 |
Restore testrestore_test_reference | Yes | text | EXAMPLE-REF-002 |
Certificate or license ownerrenewal_owner | Yes | text | TO-CONFIRM |
Illustrative operating cases
A provider assigns an agreed administrative claim workstream to a managed team.
Every delegated task has an owner, disposition and evidence; clinical and submission authority remain explicit.
The managed team receives a response that needs a provider clinical or contract decision.
The scope exception is documented and no unauthorized clinical or financial decision is taken by the service team.
Worked operating scenarios
Hold the affected administrative task, identify the provider owner and obtain the accepted evidence before proceeding.
Route it back to the provider and record a scope decision or controlled change request.
Delivery boundary
People services are distinct from software licensing and integration activation. Agree staffing, delegated authority, hours, deliverables and support terms in the service proposal.
Qualified people, authorized access and an accepted operating scope, separate from RCM software. Agree responsibilities: Specify delegated revenue tasks, authorized users, provider and payer boundaries and service coverage. Name the organization that retains each clinical, contractual and financial decision. Prepare the work: Establish source access, work queues and the documents needed for eligibility, coding, authorization or claim tasks. Approve handover rules and quality checks before processing live work. Process & escalate: Perform only the agreed tasks through authorized workflows. Route missing clinical evidence, contracting questions and payer disputes to the retained owner and keep submission authority explicit. Review service delivery: Reconcile completed work, remittance and outstanding exceptions with the provider. Review agreed measures, support coverage and change requests against the service terms without promising unsupported financial outcomes.
Explore the detailsConfigure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include administration agreements (rcm_administration_agreements.csv); Access & approvals (access_matrix.csv); Revenue & reconciliation controls (rcm_financial_controls.csv); Support handover (support_handover.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.
Explore the detailsMissing authority or supporting evidence Hold the affected administrative task, identify the provider owner and obtain the accepted evidence before proceeding. Work falls outside delegated scope Route it back to the provider and record a scope decision or controlled change request.
Explore the detailsPeople services are distinct from software licensing and integration activation. Agree staffing, delegated authority, hours, deliverables and support terms in the service proposal.
Explore the details