Interactive example · fictional data
The patient should not need to understand the operation.
Documents, pending items and a reference number organized from a reimbursement request, without anticipating coverage or payment.
Conceptual demonstration. It does not represent a customer case or prove available features.
Video
Transcript
[Illustrative example · fictional data] [“I had surgery and I need to request a reimbursement.”] [Patient · Reimbursement request] A patient requests reimbursement for surgery, in one sentence.
[NebulaOS · Starya builds and connects within the scope of the operation · Intake channel and records · Case system] [Illustrative interface · Features and integrations depend on the deployment.] On NebulaOS, connected by Starya within the scope of the operation, the request moves from the intake channel to the case system.
[Illustrative flow] [Operation · Request documents] [Invoice missing] [Pending item · the request does not move] [Follow-up channel · To proceed, we only need the invoice.] Behind the conversation, the flow organizes the documents: the report and receipt match; the invoice is missing. The patient is asked for that document only.
[Invoice] [Document file] [Case system · Opening requested · awaiting reference number] The invoice arrives. The file goes to the review team, and the case opening is requested.
[Reference number confirmed] [Reference number RS-208-P] [Coverage, amount and payment: under review, not anticipated] The case system confirms the opening and returns the reference number. Coverage, amount and payment remain under review.
[The patient didn’t need to understand the operation.] [Starya · We accelerate your AI strategy. NebulaOS is the operating foundation.] The patient didn’t need to understand the operation.
What confirms completion
The case system returns the reference number confirming the request was opened.
What NebulaOS supports in this scenario
In this scenario, NebulaOS follows the request across the intake channel and records, the request documents, the follow-up channel, the document file and the case system, connected within the scope of the operation, and asks only for the missing document. Document reading and plan rules depend on the deployment and remain proposed in this example.
- NebulaWorks Brings together the work, owners, pending items and process artifacts.
- Starya / FDE Reduces repeated requests for missing information by improving collection instructions.
Try it yourself
Walk through the steps of this scenario and see what changes with each choice. Fictional data; no system is accessed.
Open the simulation
Illustrative simulation · no system is accessed
From a simple request to a confirmed reference number
Goal Open a reimbursement request with the right documents, asking only for what is missing, without anticipating coverage, amount or payment.
- 01Request
- 02Documents
- 03Case
- 04Reference
What we know now · v1 · In progress · step 1 of 4
The request arrived in one sentence.
“I had surgery and I need to request a reimbursement.” Customer service identifies the context and the documents required. The patient does not need to know how the operation works.
Who answers now Customer service
System Intake channel and records
Preserved history
Every step, pending item and response stays here, in this session only. Starting over clears the simulation.
No fact recorded yet.
Systems and responsibilities
| System | What it answers for | How it takes part |
|---|---|---|
| Intake channel and records | Request and context given by the patient | Receives the request and the follow-up messages |
| Request documents | Surgical report, invoice and receipt (fictional) | Checked. Automated reading is a proposed part, not yet validated in operation |
| Document file | Organized set for the review team | Prepared by the operation |
| Case system | Opening of the request and reference number | Receives the opening request and is the only one that confirms the reference number |
Questions to take to your team
- Systems and data Which documents really need to be sent?
- Systems and data In which system is the request opened and tracked?
- Owner Who identifies what is missing and requests it?
- Result What does the reference number confirm, and what remains under review?
Use these questions with the guide What to ask about AI already in use
Related content
Steps
Owner, system, state and pending item of the experience’s 4 steps, with decisions and limits
Step 1 · Request
Receive the request
The patient describes the need. The operation identifies the context and the documents required.
- Owner
- Customer service
- System
- Intake channel and records
- State
- Request received
- Pending
- The document set still needs preparing.
Step 2 · Documents
Check documents and ask for what is missing
The illustrative flow organizes the documents, finds that the invoice is missing and asks the patient for that document only. The case keeps its history while it waits.
- Owner
- Document review
- System
- Request documents
- State
- Awaiting the missing item
- Pending
- The review cannot proceed without the document.
Step 3 · Case
Prepare the case
Once the missing item arrives, the set goes to the responsible review. Inconsistencies are handled separately.
- Owner
- Review team
- System
- Document file
- State
- Ready for review
- Pending
- Opening in the destination system still needs confirmation.
Step 4 · Reference
Record the reference number
The responsible system confirms the case was opened and returns a reference number for follow-up.
- Owner
- Reimbursement team
- System
- Case system
- State
- Reference confirmed
- Pending
- Coverage, amount and payment remain under review.
Decisions to explore
- Missing document
- Inconsistency between documents
- Sufficient documentation
Pending items and limits
- The reference number confirms the request was opened, not coverage.
- Approved amount and payment are outside this scope.
- Document reading and plan rules are proposed parts of this example, not yet validated in operation.
Text version
The main content, without depending on the video or the simulation.
Initial request “I had surgery and I need to request a reimbursement.”
The request arrives in a single sentence. The operation identifies the context, organizes the documents, asks only for what is missing and prepares the case for the responsible team. The reference number confirms the case was opened; review, coverage and payment come later.
The patient says they had surgery and need to request a reimbursement. The operation identifies the documents required and notices the invoice is missing. It asks only for that item and keeps the case waiting. Once the invoice arrives, the file goes to the review team and the case system confirms the opening with a reference number. Coverage, amount and payment remain under review.