Illustrative scenario — not a client
Telehealth MVP that handles patient data
A small specialist practice launching paid video consultations, with patient intake forms and visit notes stored in the app.
Reviewed by Atin Agarwal, IOanyT · 5 October 2026
Document 1 · Readable requirements
Plain prose, not a bullet dump
An excerpt. A real specification covers every screen and flow.
- R-01
Intake before the first visit
After booking, a new patient completes the practice's intake form and consent. The clinician cannot start the consultation until the intake is complete; returning patients only confirm what has changed.
- R-02
The consultation runs in the browser
Patient and clinician join from a link in their confirmation, with no download. The patient waits in a virtual waiting room until the clinician admits them. If the call drops, both can rejoin from the same link.
- R-03
Visit notes belong to the record
The clinician writes visit notes during or after the call. Notes are locked 24 hours after the visit; later changes are added as dated amendments, never edits. The patient sees a summary the clinician chooses to share.
- R-04
Every view of a record is logged
Each time anyone opens, edits or exports a patient record, the app records who, what and when. Practice administrators can review that log; nobody can change it.
- R-05
Evidence an auditor will ask for
The build produces a control-mapping document and data-flow diagrams showing where patient data enters, moves, rests and leaves, so the practice's HIPAA review starts from evidence rather than interviews.
Document 2 · Wireframes
Every screen, to review
A few of the screens. Wireframes show what is on each screen and where — not the visual design.
Main concern
Current medication
Wed 11:00 · 30 min
- Test camera and mic
- Your intake form
Intake summary
Visit notes
Record access log
Swipe for more screens →
Document 3 · Walkthrough
A day in the life of the app
People catch missing scope in a story far more reliably than in a table of requirements.
On Monday evening a new patient books a 30-minute consultation for Wednesday and pays by card. The confirmation asks her to complete the intake form, which she does on her phone in eight minutes. On Wednesday at 10:58 she clicks the link and waits; the clinician reads her intake, admits her at 11:00, and types notes as they talk. That afternoon the patient opens the app and finds the summary and next steps. The access log shows two entries for her record: the clinician's, and her own.
Document 4 · Scope
Defined by both lists
In this release
- Patient sign-up and secure sign-in
- Intake form completed before the first visit
- Booking and card payment for consultations
- Video consultation in the browser
- Visit notes written by the clinician, visible to the patient
- Access logging on every view of patient records
- Evidence an auditor asks for (control mapping, data-flow diagrams), produced as the work is done
Not in this release
- Native mobile apps
- E-prescribing
- Insurance billing
- Integration with a hospital records system
- Group sessions
On a real quote, each carries a price to add it later.
Document 5 · Assumptions register
What the price rests on
If one turns out to be wrong, that is a pre-agreed trigger to re-quote — not an argument.
- US patients only; HIPAA is the framework that applies
- Under five thousand patients in the first year
- The practice signs a business associate agreement with each vendor in the stack
- The practice provides its intake questions and consent text
Document 6 · The quote
Three tiers. Every line visible.
QA and security sit in every tier. They are never what a smaller tier removes.
| Line item | Lean | Standard | Premium |
|---|---|---|---|
| Patient sign-up and secure sign-in | ● | ● | ● |
| Intake form and consent | ● | ● | ● |
| Booking with card payment | ● | ● | ● |
| Browser video with waiting room | ● | ● | ● |
| Visit notes with locked amendments | ● | ● | ● |
| Record access log | — | ● | ● |
| Control mapping and data-flow diagrams | — | ● | ● |
| Clinician schedules and availability | — | ● | ● |
| Follow-up messaging with patients | — | — | ● |
| Practice reporting | — | — | ● |
| Priority support, three months | — | — | ● |
| Test coverage 80%+ | ● | ● | ● |
| Security review | ● | ● | ● |
| Dependency scanning | ● | ● | ● |
Your own quote shows a total for each tier, locked for 14 days from the moment it is issued.
Lean
Sign-up, intake, booking with payment, browser video and visit notes
Standard
Lean plus access logging, the audit evidence and clinician scheduling
Premium
Standard plus follow-up messaging, reporting and priority support
An illustrative scenario, not a quote for your project. Your quote is built from your own specification, with a blended total on every line instead of a rate card, and locked for 14 days once issued.
What arrives
Enough to decide with. Then enough to build from.
| Artifact | Free | On signature |
|---|---|---|
| Readable requirements Plain prose, not a bullet dump | Included | |
| Wireframes Every screen, to review | Included | |
| Scope summary What the build covers | Included | |
| Explicit exclusions The "not in this release" list, with backlog prices | Included | |
| Assumptions register Every load-bearing assumption, stated | Included | |
| Three-tier itemized price Traceable line items | Included | |
| Machine-readable spec exports | On signature | |
| Editable wireframe files | On signature | |
| openapi.yaml The API contract | On signature | |
| Mapping CSVs | On signature | |
| Given/when/then suites | On signature | |
| Architecture decisions | On signature |
What arrives free
- Readable requirements Included Plain prose, not a bullet dump
- Wireframes Included Every screen, to review
- Scope summary Included What the build covers
- Explicit exclusions Included The "not in this release" list, with backlog prices
- Assumptions register Included Every load-bearing assumption, stated
- Three-tier itemized price Included Traceable line items
What arrives on signature
- Machine-readable spec exports On signature
- Editable wireframe files On signature
- openapi.yaml On signature
- Mapping CSVs On signature
- Given/when/then suites On signature
- Architecture decisions On signature
What happens next
From your description to the build
- 01
You describe it
In plain words. Today a person runs the intake with you by email.
- 02
It asks back
The questions a good engineer would ask, before anything is priced.
- 03
The documents arrive
Everything on this page, for your project, before you pay anything.
- 04
The price holds
The quote is locked for 14 days from the moment it is issued.
- 05
You sign, we build
Every requirement traced from quote line to accepted build. Changes priced before you approve them.
Defined by both lists
Get this quoted for your project.
No signature, no call. A business email unlocks the full quote.