Designed synthetic illustration; not patient data or a diagnostic result
Doctor home visit

A connected path from the home request to documented follow-up

NAWA’s code contains a substantial patient, assigned-provider and operations model for the doctor-home-visit service type. The model is documented here while public regions and commercial availability remain unannounced.

Documented modelPublic availability unannounced
See how NAWA connectsIllustrative model; it does not represent live product data, and approved product captures are still pending.
Conceptual platform modelThe connected NAWA ecosystem
Interactive conceptual map. Visual paths illustrate two-way data flow between the NAWA center and documented platform surfaces; they do not represent live product data.
Illustrative two-way data flowIllustrative two-way flow
NAWAOne connection
Code-backed care model

A doctor home visit, from request to follow-up

The platform code models the patient, assigned-provider and operations paths together. This is an explanation of the model—not a public-launch or coverage announcement.

Documented modelPublic availability unannounced
  1. Request the visit

    The request record can include a saved address, doctor-visit service type, specialty, reason, urgency, preferred date and time, notes and a calculated estimate. The current mobile form does not expose every field.

  2. Dispatch and schedule

    The current dispatcher selects an enabled provider within the configured distance. Acceptance creates the scheduled visit; rejection or expiry returns the request for another attempt.

  3. Arrival and verification

    The visit moves through Scheduled, En route, Arrived and In progress. The model includes numeric ETA/location updates, arrival proof and one-time-code verification—not a live route map claim.

  4. Document and plan next steps

    Structured documentation can capture observations, vitals, procedures, administered medicines, patient instructions and a follow-up plan during or after the visit. A safe patient summary and rating can close the loop after completion.

Patient

Addresses, request status, pre-schedule cancellation, visit details, ETA values, summary and rating.

Assigned provider

Home-visit availability, assignment response, visit states, check-in proof, verification, documentation, a provider-recorded escalation log and completion.

Operations

Pricing configuration, request monitoring, manual dispatch, assignment expiry and stale-location checks.

Patient path

Request, understand the status, and keep the outcome

The coded patient path covers the request context and a safe post-visit summary without turning the marketing website into a care channel.

Explore 3 pointsAddress and preference · Status and arrival context · Summary and rating

Address and preference

The request record can include a saved address, doctor-visit type, specialty, reason, urgency, preferred date and time, and notes. The current mobile form does not expose every field.

Status and arrival context

Request and visit states, numeric location freshness, distance and ETA values are modelled; a live route map is not claimed.

Summary and rating

After completion, safe instructions, selected observations, a documented follow-up plan and the patient’s rating can close the information loop.

Assigned-provider path

Accept, arrive, verify, care, and document

The operational path models visit execution and structured documentation while avoiding an unsupported doctor-role or qualification claim.

Explore 3 pointsAssignment response · Arrival and proof · Documented care

Assignment response

The assigned provider can enable home visits and accept or reject a pending assignment. Acceptance creates the scheduled visit.

Arrival and proof

The model includes separate check-in proof and one-time-code verification mechanisms for arrival and visit start.

Documented care

Structured observations, vitals, procedures, administered medicines, patient instructions and a follow-up plan can be documented during or after the visit, alongside a provider-recorded escalation log.

Operational truth

A deep model with explicit implementation boundaries

The code supports pricing configuration, request monitoring, manual dispatch, assignment expiry and stale-location checks. Important qualification and commercial gaps remain visible.

Explore 3 pointsCurrent dispatch rule · No payment claim · No emergency or coverage claim

Current dispatch rule

Current selection uses general home-visit availability, prior attempts and distance; it does not yet prove specialty, credentials, work hours or daily capacity.

No payment claim

The model calculates estimates and final price, but no automatic payment, insurance or refund workflow is claimed.

No emergency or coverage claim

The website does not present this as an emergency service, 24/7 operation, nationwide coverage or a confirmed encounter-record integration.

Code-backed documented model · Public region and commercial availability unannounced.

Follow the real availability state

Any operating region and access path would be published only after approval. The marketing website is not a booking or emergency channel.

A connected path from the home request to documented follow-up | NAWA Digital Health