Admission to discharge
A patient moves from admission to the ward, then leaves with a connected discharge record.
MANSOQ IN PRACTICE
Explore the people, decisions and connected records from the first action to the final handover.
END-TO-END WORKFLOW CASE
A patient moves from admission to the ward, then leaves with a connected discharge record.
A patient arrives for a planned inpatient stay. Reception, the ward, diagnostics and finance must work from the same encounter through discharge.
An admission is one journey, even when responsibility changes between several teams.
Confirm the patient identity, admission details and responsible service against the shared record.
Document the ward handover, observations and care responsibilities for the incoming team.
Record the assessment and connect medication and departmental requests to this inpatient encounter.
Complete the selected laboratory or pharmacy work and return its documented result to the care context.
Record the discharge summary, medication plan and follow-up responsibility for the next team.
Review encounter-linked charges, patient liability and payments; assign any outstanding balance for follow-up.
Identity · Admission · Service
Each stage identifies the team, the action and the record carried forward.
Confirm the selected capabilities, required companions and external connections during configuration.
If a result or discharge task is outstanding, keep it attached to the encounter with a named owner; the clinical team decides the care action.
Responsible team · Treating clinicianKeep missing notes or results attached to the encounter. The receiving team identifies the responsible service and records the follow-up.
Responsible team · Nursing teamReturn the disputed item to its source activity. Review the charge or record correction with the responsible team before financial closure.
Responsible team · Finance teamExternal systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
The clinical and operating-room teams work through preparation, procedure and recovery.
A patient attends a scheduled day-surgery service. Booking, theatre preparation, the procedure, recovery and billing must remain connected.
Theatre readiness and the recovery handover need more than a booking on a calendar.
Link the scheduled case, patient and responsible surgical service to the encounter.
Document the agreed preoperative assessment and preparation requirements for the surgical team.
Connect the case to selected theatre resources and required consumables within the agreed operating-room scope.
Record perioperative activity and the procedure against the patient’s case rather than a separate account.
Carry the procedure record, observations and next responsibilities into recovery and discharge documentation.
Reconcile recorded services and consumables with the case bill and assign financial follow-up.
Booking · Encounter · Service
Each stage identifies the team, the action and the record carried forward.
Confirm the selected capabilities, required companions and external connections during configuration.
When a case is rescheduled, update the booking and resource responsibility while retaining the preparation record for review.
Responsible team · Access & coordinationKeep missing notes or results attached to the encounter. The receiving team identifies the responsible service and records the follow-up.
Responsible team · Nursing teamReturn the disputed item to its source activity. Review the charge or record correction with the responsible team before financial closure.
Responsible team · Finance teamExternal systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
The next ICU team reviews the observations, medication and responsibilities it needs.
An ICU patient’s care is handed from one shift to the next. The incoming team needs the documented observations, medication and pending work together.
A handover must transfer responsibility as well as information.
Open the correct inpatient encounter and confirm the current ICU team and location.
Review recorded observations and clinical notes with their encounter context; assess care professionally.
Bring the documented medication and order context into the handover for the responsible clinical team.
Link available results and outstanding departmental work to the same encounter.
Document the care handover and identify who takes responsibility for each next action.
Update the next care plan or documented ward transfer while preserving the ICU encounter history.
Identity · Encounter · ICU location
Each stage identifies the team, the action and the record carried forward.
Confirm the selected capabilities, required companions and external connections during configuration.
If information is missing, identify its source and responsible team in the handover instead of treating an absent result as a completed task.
Responsible team · Nursing teamKeep missing notes or results attached to the encounter. The receiving team identifies the responsible service and records the follow-up.
Responsible team · Nursing teamReturn the disputed item to its source activity. Review the charge or record correction with the responsible team before financial closure.
Responsible team · Finance teamExternal systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
Revenue teams follow service activity through billing, payer responses and reconciliation.
A hospital encounter includes ward care, departmental services and patient payments. Finance needs to explain every charge and remaining balance.
Revenue follow-up starts with the services actually recorded in the encounter.
Record the patient, encounter and payer or self-pay context before financial follow-up.
Link recorded departmental and care services to accountable encounter charges.
Check the agreed tariffs and patient contribution against the recorded services and coverage.
Review the invoice and use the selected ZATCA exchange scope where configured and activated.
Match recorded payments or payer financial responses to the relevant account and invoice.
Assign unresolved differences for review and record the reconciliation decision and next action.
Encounter · Payer · Patient account
Each stage identifies the team, the action and the record carried forward.
Confirm the selected capabilities, required companions and external connections during configuration.
A disputed charge returns to its service reference for review; a corrected financial record keeps the original encounter trace.
Responsible team · Finance teamKeep missing notes or results attached to the encounter. The receiving team identifies the responsible service and records the follow-up.
Responsible team · Nursing teamReturn the disputed item to its source activity. Review the charge or record correction with the responsible team before financial closure.
Responsible team · Finance teamExternal systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
Reception, the clinician and the billing team share one encounter from arrival to payment.
A new patient books a consultation, arrives at the clinic, receives a documented care plan and completes the visit’s financial steps.
Reception, consultation and payment should describe the same visit.
Connect the appointment to the selected service and patient identity.
Confirm the shared patient record and establish the outpatient encounter and financial context.
Review the available history and record the assessment and agreed care plan.
Attach the clinician’s orders and prescriptions to the consultation context.
Review recorded services, patient contribution and payment against the encounter.
Record the next appointment or follow-up responsibility with the consultation’s care context.
Appointment · Service · Identity
Each stage identifies the team, the action and the record carried forward.
Confirm the selected capabilities, required companions and external connections during configuration.
If the patient already has a record, verify the identity before continuing so the new encounter follows the correct history.
Responsible team · Access & coordinationIdentify the missing source and record who follows it up. The clinician decides how the available context affects the consultation.
Responsible team · Treating clinicianUpdate the encounter and next appointment responsibility; review any affected service charges against the documented activity.
Responsible team · Access & coordinationExternal systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
A returning patient’s previous notes and relevant results inform the next consultation.
A returning patient has a follow-up consultation after earlier testing. The clinician needs the prior plan and available results beside today’s record.
A follow-up should build on the previous visit instead of restarting the story.
Confirm the patient and connect the new appointment to the existing record.
Review the prior consultation and its recorded follow-up reason.
Review relevant available results and record their interpretation in today’s consultation.
Document the current assessment and the clinician’s changes to orders or medication.
Link today’s recorded service and payment responsibility to the follow-up encounter.
Record the next appointment, referral or documented follow-up action.
Identity · Appointment · Prior encounters
Each stage identifies the team, the action and the record carried forward.
Confirm the selected capabilities, required companions and external connections during configuration.
When a result has not arrived, record the pending item and the responsible follow-up; do not present it as reviewed.
Responsible team · Treating clinicianIdentify the missing source and record who follows it up. The clinician decides how the available context affects the consultation.
Responsible team · Treating clinicianUpdate the encounter and next appointment responsibility; review any affected service charges against the documented activity.
Responsible team · Access & coordinationExternal systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
The care team links a clinical order and the available result back to the encounter.
During a consultation, a clinician requests a test and prescribes medication. Each request needs an owner and a return path to the visit.
A request is useful when the result or medication step returns to the care context.
Review the patient record and the current consultation before creating a request.
Connect the requested service and documented clinical context to the encounter.
Document the clinician’s prescription and its encounter reference.
Use the selected native department or agreed external connection to carry the request.
Review available results in the encounter and document the next clinical action.
Review delivered service charges while the care team records remaining follow-up responsibilities.
Patient · Consultation
Each stage identifies the team, the action and the record carried forward.
Confirm the selected capabilities, required companions and external connections during configuration.
External diagnostics and dispensing require an agreed interface or documented handover; an order alone does not imply a native laboratory or pharmacy.
Responsible team · Integration & IT teamIdentify the missing source and record who follows it up. The clinician decides how the available context affects the consultation.
Responsible team · Treating clinicianUpdate the encounter and next appointment responsibility; review any affected service charges against the documented activity.
Responsible team · Access & coordinationExternal systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
The revenue team traces coverage and approvals through the claim and payer response.
An insured patient attends a clinic. Reception verifies coverage, the revenue team follows the required approval and the claim is reconciled after the visit.
Care activity, payer decisions and the patient’s contribution must remain traceable together.
Check coverage and retain the response with the patient and encounter context.
Record the preauthorization request, payer response and next responsibility where required.
Record the consultation and services in the same outpatient encounter.
Apply the agreed contract and tariff context to reviewed charges and patient liability.
Review the claim work queue and payer response, assigning any correction to its owner.
Match remittance and payments to the claim and encounter; identify unresolved differences.
Coverage · Eligibility response
Each stage identifies the team, the action and the record carried forward.
Confirm the selected capabilities, required companions and external connections during configuration.
A rejection remains a work item with its reason, correction and resubmission history. NPHIES exchange is used only in the selected, activated scope.
Responsible team · Revenue teamIdentify the missing source and record who follows it up. The clinician decides how the available context affects the consultation.
Responsible team · Treating clinicianUpdate the encounter and next appointment responsibility; review any affected service charges against the documented activity.
Responsible team · Access & coordinationExternal systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
The next specialist receives the shared record and the documented referral context.
A patient is referred from one specialty to another within a polyclinic. The receiving clinician needs the referral reason, previous notes and available results.
Different specialties should add to one patient story.
Record the assessment and the reason a specialist review is requested.
Arrange the receiving specialty appointment against the existing patient identity.
Review the referring note and relevant available results before documenting the specialist encounter.
Link the specialist’s orders and prescription to the receiving consultation.
Document the specialist assessment and follow-up responsibility for the referring service.
Keep each encounter’s services and billing distinct while retaining the shared patient context.
Assessment · Referral reason
Each stage identifies the team, the action and the record carried forward.
Confirm the selected capabilities, required companions and external connections during configuration.
If the receiving service needs more information, record the missing referral context and return the task to the responsible service.
Responsible team · Treating clinicianReturn the missing information to the referring or requesting team while retaining the original patient and encounter references.
Responsible team · Department teamReview the reason against the delivered service and agreed contract scope. Record the correction and next financial owner.
Responsible team · Revenue teamExternal systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
The laboratory handles the order and specimen before the result returns to the clinician.
A specialty clinic requests a laboratory test. The laboratory processes the work, returns the result and the clinician documents its review.
The result must return to the patient and the consultation that requested it.
Record the requested laboratory service in the correct specialty encounter.
Confirm the patient, request and supported specimen workflow before processing.
Complete the selected native laboratory work or agreed LIS exchange.
Attach the documented result to its request and patient encounter.
Review the result professionally and document the next care action.
Review the delivered service charge while retaining any remaining clinical follow-up.
Order · Encounter · Requested service
Each stage identifies the team, the action and the record carried forward.
Confirm the selected capabilities, required companions and external connections during configuration.
A rejected or incomplete specimen stays connected to the original request, with the laboratory’s documented reason and next responsibility.
Responsible team · Laboratory teamReturn the missing information to the referring or requesting team while retaining the original patient and encounter references.
Responsible team · Department teamReview the reason against the delivered service and agreed contract scope. Record the correction and next financial owner.
Responsible team · Revenue teamExternal systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
Clinical prescribing connects to pharmacy operation and stock responsibilities.
A patient leaves a specialist consultation with a prescription. The polyclinic pharmacy reviews, dispenses and records the selected medication work.
Prescribing, dispensing and stock movement need distinct responsibilities in one connected path.
Record the clinician’s prescription against the specialty encounter.
Verify the patient and prescription context within the selected pharmacy scope.
Document the pharmacist’s review and any clarification needed from the prescriber.
Record the agreed dispensing activity against the prescription and patient.
Link recorded dispensing to inventory responsibilities where inventory is included.
Review medication charges and preserve documented follow-up for the care team.
Prescription · Clinician · Encounter
Each stage identifies the team, the action and the record carried forward.
Confirm the selected capabilities, required companions and external connections during configuration.
An unavailable item or unclear prescription returns to the responsible pharmacist and prescriber; the software does not choose a substitute treatment.
Responsible team · Pharmacy teamReturn the missing information to the referring or requesting team while retaining the original patient and encounter references.
Responsible team · Department teamReview the reason against the delivered service and agreed contract scope. Record the correction and next financial owner.
Responsible team · Revenue teamExternal systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
Revenue teams follow the visit’s insurance and financial work through the payer response.
An insured specialty visit includes diagnostics and medication. The revenue team follows coverage, approvals, claims and payment allocation across those services.
Several departments can contribute to one claim without losing the origin of each service.
Record eligibility and the relevant coverage context for the visit.
Connect required preauthorization requests and payer decisions to the requested services.
Record consultation, diagnostic and pharmacy activity with its encounter reference.
Review the claim work items and use the agreed, activated exchange channel.
Assign rejection reasons for correction, review and documented resubmission where needed.
Match payer remittance to claim records and assign remaining financial differences.
Eligibility · Coverage · Encounter
Each stage identifies the team, the action and the record carried forward.
Confirm the selected capabilities, required companions and external connections during configuration.
A partially paid claim keeps the paid allocation and unresolved lines separate, with a documented reason and follow-up owner.
Responsible team · Finance teamReturn the missing information to the referring or requesting team while retaining the original patient and encounter references.
Responsible team · Department teamReview the reason against the delivered service and agreed contract scope. Record the correction and next financial owner.
Responsible team · Revenue teamExternal systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
Teams coordinate care within defined entity, patient-record and access boundaries.
A patient moves between services in a medical-city network. The receiving entity needs the permitted care context while each organization retains its data boundaries.
Continuity across entities requires governed access, not unrestricted record sharing.
Agree the entities, identity scope and permitted record exchange for this composition.
Document the patient’s current encounter and reason for the next service.
Confirm the destination and responsible team for the referral or transfer.
Carry the agreed information through the selected connection with source references.
Review permitted information and document the receiving entity’s encounter and responsibilities.
Review supported network reporting within the agreed entity and access boundaries.
Entities · Identity boundary · Permissions
Each stage identifies the team, the action and the record carried forward.
Confirm the selected capabilities, required companions and external connections during configuration.
If an identity cannot be matched or access is outside the agreed boundary, the responsible teams resolve it before exchanging additional records.
Responsible team · Integration & IT teamResolve the patient mapping or access boundary with the source entity before additional records are shared.
Responsible team · Integration & IT teamUse the agreed operating fallback and identify the responsible source team. Review incomplete information explicitly rather than assuming it is current.
Responsible team · Integration & IT teamExternal systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
The admitting team receives the documented emergency encounter and care responsibilities.
A medical-city outpatient service refers a patient for admission. The referral, receiving ward and financial encounter need connected responsibilities.
Changing the care setting should not remove the reason the patient arrived.
Record the outpatient assessment and documented admission referral.
Establish the destination service and the patient identity within the agreed network boundaries.
Connect the admission and ward responsibility to the receiving entity’s record.
Review available referral notes and record the receiving ward’s observations and responsibilities.
Document inpatient care and connect required department requests to the admitted encounter.
Retain the discharge context and review each entity’s recorded charges and account responsibility.
Outpatient encounter · Referral
Each stage identifies the team, the action and the record carried forward.
Confirm the selected capabilities, required companions and external connections during configuration.
When the destination changes, update the responsible entity and transfer record; cross-entity sharing still follows the agreed permissions.
Responsible team · Access & coordinationResolve the patient mapping or access boundary with the source entity before additional records are shared.
Responsible team · Integration & IT teamUse the agreed operating fallback and identify the responsible source team. Review incomplete information explicitly rather than assuming it is current.
Responsible team · Integration & IT teamExternal systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
Specialist departments connect orders, available results and dispensing to the care record.
Several medical-city departments contribute to a patient’s care. The network needs to distinguish native operation from information exchanged with existing systems.
Connected results and operating a department are different responsibilities.
Agree which departments operate in MANSOQ and which retain an external system.
Link each requested service to the correct patient, encounter and department.
Document supported native activity or process the request in the retained source system.
Exchange the agreed results or status through the defined interface and identity mapping.
Review available department information and document the next care responsibility.
Review selected charge linkage with the service’s native or external source reference.
Department · Operating mode · Owner
Each stage identifies the team, the action and the record carried forward.
Confirm the selected capabilities, required companions and external connections during configuration.
If an interface fails, the agreed operational fallback and source owner handle the missing information; connected access does not replace departmental operation.
Responsible team · Integration & IT teamResolve the patient mapping or access boundary with the source entity before additional records are shared.
Responsible team · Integration & IT teamUse the agreed operating fallback and identify the responsible source team. Review incomplete information explicitly rather than assuming it is current.
Responsible team · Integration & IT teamExternal systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
Leadership reviews selected operational and revenue reporting within governed boundaries.
Medical-city leaders review operational and revenue activity across selected entities. They need comparable views with a clear source and reporting boundary.
A network report is useful only when the included entities and definitions are clear.
Define the operational question, selected entities and authorized audience.
Record the relevant care and departmental activity within its source entity.
Review claims, financial responses and outstanding work within the selected reporting scope.
Check included sources, entity permissions and the agreed operational definitions.
Use supported operational and revenue views to identify work requiring attention.
Record the responsible team and return operational questions to the relevant source.
Question · Entities · Access
Each stage identifies the team, the action and the record carried forward.
Confirm the selected capabilities, required companions and external connections during configuration.
An incomplete source is identified in the review rather than silently treated as zero activity; the source owner resolves the reporting gap.
Responsible team · Service leadershipResolve the patient mapping or access boundary with the source entity before additional records are shared.
Responsible team · Integration & IT teamUse the agreed operating fallback and identify the responsible source team. Review incomplete information explicitly rather than assuming it is current.
Responsible team · Integration & IT teamExternal systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
The local team prepares the case so a remote specialist can review the supported context.
A local ICU team requests a remote specialist review. The specialist needs the agreed clinical record, while bedside care stays with the local team.
Remote expertise needs clinical context and a clear return path to the bedside.
Confirm the patient encounter and document the question for specialist review.
Make the agreed notes and observations available through the selected source-system connection.
Review the available information and record the specialist’s assessment within the agreed service.
Document recommendations and the points requiring local clinical review.
Review the specialist note and record the local clinician’s care decision and responsibilities.
Document completed review work and any further specialist or bedside follow-up.
Encounter · Review question
Each stage identifies the team, the action and the record carried forward.
Confirm the selected capabilities, required companions and external connections during configuration.
Missing source information is referred back to the local team. Video, device data and live monitoring are separate connections, not assumed features of this scenario.
Responsible team · Local care teamThe specialist records what is missing and asks the local clinical team to provide or clarify the source information.
Responsible team · Local care teamThe source and interface owners follow the agreed fallback. Bedside care and clinical decisions remain with the responsible local team.
Responsible team · Integration & IT teamExternal systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
The next team receives the documented review, care-plan context and assigned responsibilities.
A remote ICU specialist hands an ongoing review to the next specialist. The local team needs consistent context and explicit follow-up responsibility.
A change of specialist must not erase the review history.
Confirm the patient case and the current documented specialist review.
Provide the documented clinical update within the agreed information-sharing scope.
Document the previous review, open questions and next specialist responsibility.
Read the prior context and document the receiving specialist’s assessment.
Review the updated recommendations and retain local clinical decision responsibility.
Record whether further review is required and which service owns it.
Patient · Active review
Each stage identifies the team, the action and the record carried forward.
Confirm the selected capabilities, required companions and external connections during configuration.
If local and remote records differ, identify the source and ask the responsible clinician to reconcile the information before relying on it.
Responsible team · Local care teamThe specialist records what is missing and asks the local clinical team to provide or clarify the source information.
Responsible team · Local care teamThe source and interface owners follow the agreed fallback. Bedside care and clinical decisions remain with the responsible local team.
Responsible team · Integration & IT teamExternal systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
Specialists review the supported order, result and medication context attached to the case.
A TeleICU review needs notes and results held in a local source system. The teams agree exactly which information is available for the review.
A remote record should show its source and permitted scope.
Identify the clinical notes, observations and results required for this service.
Document the source system, identity mapping and team responsible for the connection.
Carry supported source information through the selected, tested interface.
Check the available context and identify any missing information for local follow-up.
Record the review against the correct case and identify the information used.
Review the specialist record and document the local care or information follow-up.
Required information · Review scope
Each stage identifies the team, the action and the record carried forward.
Confirm the selected capabilities, required companions and external connections during configuration.
Unavailable data is made explicit in the review. An interface agreement determines what can be exchanged; no universal device compatibility is implied.
Responsible team · Integration & IT teamThe specialist records what is missing and asks the local clinical team to provide or clarify the source information.
Responsible team · Local care teamThe source and interface owners follow the agreed fallback. Bedside care and clinical decisions remain with the responsible local team.
Responsible team · Integration & IT teamExternal systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
The delivery team defines what is exchanged and who operates each side of the connection.
A hospital introduces a TeleICU connection alongside its existing clinical system. IT, clinicians and service leads need clear delivery and operating responsibilities.
A usable connection joins technical delivery to a real clinical handover.
Agree the local and remote teams, systems and information needed for the review service.
Document the agreed protocol, identity mapping, licenses and delivery owners.
Prepare an authorized demonstration case and confirm the intended source information.
Review the exchanged context, permitted access and agreed failure handling.
Document the review and demonstrate its return to the responsible local clinician.
Agree acceptance, support ownership and the activated service boundary.
Teams · Systems · Information scope
Each stage identifies the team, the action and the record carried forward.
Confirm the selected capabilities, required companions and external connections during configuration.
A failed test returns to the named interface owner. Activation follows agreed acceptance; connectivity does not grant unrestricted record access.
Responsible team · Integration & IT teamThe specialist records what is missing and asks the local clinical team to provide or clarify the source information.
Responsible team · Local care teamThe source and interface owners follow the agreed fallback. Bedside care and clinical decisions remain with the responsible local team.
Responsible team · Integration & IT teamExternal systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
The care professional reviews the record, documents the visit and records the next responsibility.
A home-care team prepares a planned visit, documents the encounter and hands the next care responsibility to the continuing service.
Care delivered at home still needs one connected clinical and operational record.
Connect the patient, planned visit and responsible home-care service.
Review the documented care plan and earlier visit context before the encounter.
Record observations and the care activity performed within the agreed service.
Document any clinician-reviewed change, medication order or departmental request.
Record the next visit or care-team responsibility with the encounter context.
Connect the documented visit services to the selected billing and revenue follow-up.
Patient · Visit · Service
Each stage identifies the team, the action and the record carried forward.
Confirm the selected capabilities, required companions and external connections during configuration.
If the visit is postponed, record the change and responsible follow-up. Mobile, offline and family messaging are separately agreed scope.
Responsible team · Access & coordinationDocument the visit change and hand the next action to the responsible service. Distinguish planned activity from care actually delivered.
Responsible team · Access & coordinationRecord the new observations and refer the plan update to the responsible clinician; carry the reviewed decision into the next visit.
Responsible team · Treating clinicianExternal systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
The responsible team reviews the documented care goals and updates the agreed plan.
A palliative-care service reviews a patient’s documented goals and care plan over several visits, with input from different professionals.
A person’s goals should remain visible as care responsibilities change.
Review the existing record and documented palliative-care context.
Record the agreed goals and professional care plan within the supported palliative workflow.
Arrange the selected service visits and document the responsible professionals.
Record observations and professional contributions against the current care plan.
Review documented changes and update the care plan through the responsible clinician.
Document the continuing care handover and any outstanding responsibility.
Patient record · Care context
Each stage identifies the team, the action and the record carried forward.
Confirm the selected capabilities, required companions and external connections during configuration.
A change in goals or care needs is referred to the responsible professional for review; the platform records the decision rather than making clinical decisions.
Responsible team · Treating clinicianDocument the visit change and hand the next action to the responsible service. Distinguish planned activity from care actually delivered.
Responsible team · Access & coordinationRecord the new observations and refer the plan update to the responsible clinician; carry the reviewed decision into the next visit.
Responsible team · Treating clinicianExternal systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
The next professional receives the relevant visit notes, care plan and medication context.
A patient receives home-care input from nursing and a clinician. Each professional contributes to the same plan and hands remaining work to the next person.
A multidisciplinary service needs shared context without blurred responsibility.
Document the current care plan and the selected professional service responsibilities.
Arrange visits against the patient’s plan and responsible service.
Record the visit observations and nursing contribution in the patient’s context.
Review the available visit documentation and record any care-plan update.
Link documented medication and department requests to the reviewed care plan.
Record the next professional responsibility and outstanding items for the continuing service.
Care plan · Professional responsibilities
Each stage identifies the team, the action and the record carried forward.
Confirm the selected capabilities, required companions and external connections during configuration.
Conflicting documentation is returned to the responsible professionals for review, with the care-plan update documented in the shared context.
Responsible team · Treating clinicianDocument the visit change and hand the next action to the responsible service. Distinguish planned activity from care actually delivered.
Responsible team · Access & coordinationRecord the new observations and refer the plan update to the responsible clinician; carry the reviewed decision into the next visit.
Responsible team · Treating clinicianExternal systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
Revenue teams trace the home-care activity through charges, claims and payment allocation.
A home-care service completes several visits under an agreed payer or self-pay arrangement. Revenue teams need to follow delivered services through settlement.
A visit schedule is not the same as a delivered service or a settled account.
Record the patient, payer or self-pay arrangement and agreed service context.
Document required coverage or authorization responses and responsible follow-up.
Record the care services delivered in each actual visit encounter.
Link reviewed charges to completed visit activity and the agreed tariff context.
Review the selected invoice or claim workflow and retain response history.
Allocate recorded payments or remittance and assign outstanding balances for follow-up.
Patient · Payer · Service arrangement
Each stage identifies the team, the action and the record carried forward.
Confirm the selected capabilities, required companions and external connections during configuration.
A cancelled visit is reviewed separately from completed care activity; disputed charges return to the documented service record.
Responsible team · Finance teamDocument the visit change and hand the next action to the responsible service. Distinguish planned activity from care actually delivered.
Responsible team · Access & coordinationRecord the new observations and refer the plan update to the responsible clinician; carry the reviewed decision into the next visit.
Responsible team · Treating clinicianExternal systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
Keep the emergency assessment, admitted-care handover and financial encounter connected.
Following emergency assessment, the treating team decides a patient needs admission. The ward receives the documented care context and responsibility.
The ward needs the emergency story, not only a new admission record.
Confirm identity and establish the emergency encounter.
Record observations, assessment and the treating clinician’s care decisions.
Link documented medication and department requests to the emergency encounter.
Document the admission decision and receiving service responsibility.
Carry the emergency context and pending work into the ward handover.
Review encounter-linked service charges while the ward documents continued care.
Identity · Emergency encounter
Each stage identifies the team, the action and the record carried forward.
Confirm the selected capabilities, required companions and external connections during configuration.
A changed destination or outstanding result remains part of the documented transfer and is assigned to the responsible care team.
Responsible team · Nursing teamKeep missing notes or results attached to the encounter. The receiving team identifies the responsible service and records the follow-up.
Responsible team · Nursing teamReturn the disputed item to its source activity. Review the charge or record correction with the responsible team before financial closure.
Responsible team · Finance teamExternal systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
Connect supported SBS mapping, provider services and separate payer tariff responsibilities.
A polyclinic introduces a service into its billing catalogue. Coding and revenue teams must agree the supported code mapping and its payer price rules.
A service code and a payer tariff answer different questions.
Document the service description and operational department.
Confirm the supported SBS release and permitted catalogue usage.
Review the proposed provider-to-code mapping and record the responsible decision.
Record the separate contract price and tariff rules for the service.
Review a selected service charge against its mapping and agreed tariff.
Retain the reviewed mapping and assign responsibility for later catalogue changes.
Service · Description · Department
Each stage identifies the team, the action and the record carried forward.
Confirm the selected capabilities, required companions and external connections during configuration.
An uncertain mapping is held for responsible coding review. Catalogue tooling does not grant licensing rights or define payer reimbursement automatically.
Responsible team · Revenue teamReturn the missing information to the referring or requesting team while retaining the original patient and encounter references.
Responsible team · Department teamReview the reason against the delivered service and agreed contract scope. Record the correction and next financial owner.
Responsible team · Revenue teamExternal systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
Explore a verified assistive task with defined source context and mandatory professional review.
A clinic selects an approved documentation assistance task. The clinician reviews its output before any content becomes part of the care record.
Assistance supports professional documentation; it does not replace clinical judgment.
Agree the named verified assistance task, data boundary and responsible reviewer.
Confirm the correct patient and the documentation context available to the selected task.
Use the selected assistive workflow within its accepted operational scope.
Check the output against the source and correct or reject unsupported content.
Record only the clinician-reviewed documentation in the encounter.
Document the clinician’s care decisions and subsequent orders through the standard care workflow.
Task · Data boundary · Reviewer
Each stage identifies the team, the action and the record carried forward.
Confirm the selected capabilities, required companions and external connections during configuration.
Incorrect or insufficient assistance is rejected by the reviewer. No autonomous diagnosis, treatment selection or universal AI task availability is represented.
Responsible team · Treating clinicianIdentify the missing source and record who follows it up. The clinician decides how the available context affects the consultation.
Responsible team · Treating clinicianUpdate the encounter and next appointment responsibility; review any affected service charges against the documented activity.
Responsible team · Access & coordinationExternal systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.