Skip to main content
Standards-anchored

Every line of code traces to a standard.

JCI surveys evaluate hospitals on specific standards. Pneuma's job is to give the hospital the technical capability those standards demand — without inventing new categories of evidence to produce.

Joint Commission International

JCI 7th-edition standards mapped to platform surfaces.

IPSG · International Patient Safety Goals

IPSG.1
Identify patients correctly (2 identifiers)
UUID + hospital MRN; no endpoint acts on id alone
IPSG.2
Effective communication (SBAR handoff)
Structured Situation/Background/Assessment/Recommendation on every alert acknowledgement
IPSG.5
Reduce HAI risk (infection control)
isolation_required risk flag · sepsis composite rule (T + HR + RR)
IPSG.6
Reduce harm from falls
11-flag vulnerable-population enum surfaces high-priority cases in triage queue

MOI · Management of Information

MOI.2
Information privacy + security
requireRpmTenant middleware · tenant_audit_log capture · AES-256-GCM-ready passport column
MOI.3
Data retention + destruction
Soft-delete column on cases · retention sweep cron (Phase 3)
MOI.6
Clinical record completeness
NOT NULL on tenant_id, patient_id, pathway, procedural_date · ICD-10-TM coding
MOI.7
Clinical record retrievability
Composite index (tenant_id, patient_id, taken_at) for O(log n) retrieval
MOI.8
Coded data standards
ICD-10-TM regex-validated on intake · path to Thai SNOMED + LOINC declared

PCC · Patient-Centered Care

PCC.1
Effective communication, language services
4-locale catalog (th-TH primary · en-US · zh-CN · ar-SA) · language_barrier flag
PCC.4
Informed consent
Purpose-bounded PDPA consent ledger · structured withdrawal endpoint
PCC.5
Cultural beliefs + preferences
preferredLanguage + homeCountry captured on every case

AOP · Assessment of Patients

AOP.1.4
Special-population assessment
11-flag enum covers elderly, pediatric, pregnancy, immunocompromised, opioid_naive, difficult_airway

COP · Care of Patients

COP.2
Care coordination
Pathway-specific threshold profile + SBAR handoff on every ack
COP.3
High-risk patient care
4-tier severity ladder · composite rules (sepsis · PE · bleeding)

QPS · Quality Improvement and Patient Safety

QPS.4
Aggregate clinical + managerial data
Alert time-series with severity + pathway + ack timestamps — outcome dashboards in Phase 3
Ministry of Public Health Thailand

National eHealth Strategy 2017–2026 · 5 pillars.

Each hospital tenant declares its capability per pillar inenterprise_hospital_profile.eHealthCapability.

01

Patient eHealth Record

Hospital MRN + tenant-scoped patient identity; Thai 13-digit national ID supported; HIE for cross-hospital portability gated on partner.

02

Telemedicine

Video (Daily.co inherited) and async messaging routes mounted; e-prescribing stays with the HIS.

03

mHealth

Symptom logging via POST /vitals manual_patient source; mobile companion app inherited skeleton (RPM-adapted in Phase 3).

04

Health Information Exchange

OpenAPI 3.1 spec designed for FHIR R4 + Thai FHIR profile; declared HIS field selects adapter (TrakCare · HOSxP · Hospital OS).

05

Data Standards

ICD-10-TM diagnosis coding native; Thai SNOMED CT subset + LOINC vitals mapping declared for Phase 3.

Personal Data Protection Act

PDPA B.E. 2562 by design — not retrofitted.

Thai data subjects have the right to know, the right to access, the right to withdraw consent, the right to be forgotten. The platform models each as a distinct endpoint and audit event.

§19 — Lawful basis

Purpose-bounded consent required pre-data-processing

enterprise_pdpa_consent ledger · POST /consent records purposes[]

§24 — Sensitive data (health)

Stricter consent thresholds for health data

rpm_clinical_care + billing_processing + quality_improvement enumerated as distinct purposes

§28 — Cross-border transfer

Patient data leaves Thailand only with consent + adequate jurisdiction

home_country_pcp_share purpose · DATA_RESIDENCY.md residency plan

§32 — Right to be forgotten

Patient may request deletion of personal data

Soft-delete columns + RTBF processor (Phase 3 worker)

§36 — Withdrawal of consent

Withdrawal must be as easy as giving consent

POST /consent/:id/withdraw · idempotent · audit-event pdpa.consent.withdraw