ArogyaShutra
Connected care. Accountable records.
These coverage labels are transcribed from the supplied audit, not independently reclassified. “Local” does not mean production ready. [S1]
The interface, as observed
Original CSS + JavaScript · Real local API via Python bridge · Synthetic examples
1440 × 1000 CSS-pixel viewport; full-page capture. Existing source branding is unchanged. Full-resolution PNG ↗
Language toggle exercised. Translation quality was not independently reviewed. Full-resolution PNG ↗
390 × 844 CSS-pixel viewport; full-page capture. Not a physical device. Full-resolution PNG ↗
Record-table capture — Reception and patient registry
Records shown are seeded synthetic examples. No record mutations were made. Full-resolution PNG ↗
Create-form capture — rendered, not submitted
Form rendering only; no submission or field-completeness certification. Full-resolution PNG ↗
[S2] Capture metadata, timestamps, routes and screenshot hashes. Offline rendering uses actual app functions with a local HTTP bridge; browser network navigation, cookies, service workers and transport enforcement were not validated.
What this sample actually checks
| Check | Observed result | Boundary / context |
|---|---|---|
| Local HTTP shell route | 200 | Python client, not browser navigation |
| Overview metrics | 5 displayed | English and Bengali headings rendered |
| Bengali language toggle | PASS | সারসংক্ষেপ |
| 390 px navigation | PASS | Menu opened and closed |
| Horizontal page overflow | 0 px | At the two measured viewport widths |
| Sampled record table | 2 rows | Reception and patient registry |
| Sampled create form | PASS | 8 labels rendered |
| Create / edit submission | NOT ATTEMPTED | Opening a form is not a persistence test |
Corroborating automated tests
These exact tests were matched to the fresh run. They support their named invariants; they do not prove every source requirement. [S3]
| Source requirement | Test reference | Fresh run |
|---|---|---|
| AS-F03 Clinical documentation | HealthcareDomainTests.test_hospital_notes_require_treating_doctor_and_preserve_signed_content | PASS |
| AS-F04 Orders and service catalogue | HealthcareDomainTests.test_rejected_specimen_cannot_produce_a_verified_or_released_report | PASS |
| AS-F05 Specimen chain of custody | HealthcareDomainTests.test_rejected_specimen_cannot_produce_a_verified_or_released_report | PASS |
Scope that stays visible
Patient identity, specimen custody and qualified report review are separate steps. Drafts are never shown as released reports. This system does not diagnose or recommend treatment.
রোগী শনাক্তকরণ নমুনার হেফাজত ও যোগ্য ব্যক্তির প্রতিবেদন যাচাই পৃথক ধাপ। খসড়াকে প্রকাশিত ফল বলা হয় না। এই ব্যবস্থা রোগ নির্ণয় বা চিকিৎসা সুপারিশ করে না।
All 12 supplied requirements and their residual limitations
| Requirement | Source status | Implementation scope / remaining work |
|---|---|---|
| AS-F01 Patient identity and duplicates | PARTIAL | Facility-scoped identity, bilingual names, optional birth date/estimated age and non-merging duplicate references. Remaining: Duplicate matching is name plus known birth date; trained merge workflow and merge history are absent. |
| AS-F02 Encounter and consent | PARTIAL | Immutable outpatient/emergency identity, responsible active doctor and separate episode/administrative consent. Remaining: Inpatient episodes/admission management are absent; an emergency label is not clinical triage. |
| AS-F03 Clinical documentation | Local implementation | Treating-doctor authored notes, exact-content signing, provenance and linked amendments preserve signed history. Remaining: Human clinical review and policy acceptance remain mandatory; no diagnosis or certified-signature provider is included. |
| AS-F04 Orders and service catalogue | Local implementation | Manually versioned service codes/methods/references/fees, supervisor approval and treating-doctor orders with frozen terms. Remaining: The operator must supply reviewed source data and qualified staff; no AI ordering or provider catalogue is connected. |
| AS-F05 Specimen chain of custody | Local implementation | Unique barcode, actor/time custody stages, reasoned rejection and linked recollection with a new barcode. Remaining: Device/label-printer integration and target-facility operational checks remain external. |
| AS-F06 Verified laboratory reports | Local implementation | Structured results, independent verifier, bound patient snapshot/hash, critical gate, immutable release and linked corrections. Remaining: Values and critical flags are human-entered; analyzer integration/reference-data validation are not supplied. |
| AS-F07 Critical-result escalation | PARTIAL | Assigned in-app critical alerts, required acknowledgment and recorded worker escalation to configured supervisors. Remaining: No SMS, call or paging transport is connected; worker supervision and real response times are unverified. |
| AS-F08 Admission and bed occupancy | Blocked | No inpatient bed-management workflow. Remaining: Admission, bed statuses, transfer, discharge and overlapping-occupancy prevention are not implemented. |
| AS-F09 Medication dispensing and administration | Blocked | No pharmacy or bedside administration workflow. Remaining: Patient/item/quantity-confirmed dispensing and administration events are not implemented. |
| AS-F10 Consolidated billing | PARTIAL | Released services create one linked invoice; bounded cash receipts/refunds cannot alter clinical findings. Remaining: Consolidated inpatient bills, deposits, discount authorization, insurer claims and digital callbacks are absent. |
| AS-F11 Patient portal and release | Local implementation | Authenticated patient/caregiver grants with documented authority, expiry/revocation and released-only portal/document access. Remaining: No national identity check or anonymous phone-based download is supplied. |
| AS-F12 Downtime and recovery | Local implementation | Numbered manual downtime entries preserve event/entry times and unverified state; treating-doctor reconciliation preserves prior encounter. Remaining: Operators supply approved paper forms; no encrypted browser record store or automatic offline merge is provided. |
App-specific coverage JSON · Supplied release gates (Source snapshots and local paths are not published with this site.)
Sources and provenance
[S1] Supplied feature coverage (Source snapshots and local paths are not published with this site.); subset linked above. No coverage status has been upgraded by this pack.
[S2] Fresh UI capture record and original PNGs. Harness method and exclusions.
[S3] Fresh 143-test validation · Full test log.
[S4] Supplied ArogyaShutra module (Source snapshots and local paths are not published with this site.) · Supplied frontend source (Source snapshots and local paths are not published with this site.).
[S5] Supplied release-candidate validation (Source snapshots and local paths are not published with this site.) · Source-subset hashes (Source snapshots and local paths are not published with this site.).