Core Concepts

Core Concepts

DELPHOS is a clinical intelligence platform that augments medical practice. Before diving into specific endpoints, it helps to understand the key ideas that shape how the platform works.

The Oracle Philosophy

DELPHOS is designed as an oracle — a system that observes, analyzes, and advises, but never decides. Every clinical decision remains with the physician.

This philosophy manifests in three ways:

1. Advisory, not prescriptive — DELPHOS provides recommendations, warnings, and safety checks. It never blocks a physician from acting on their clinical judgment.

2. Evidence-based intelligence — Every recommendation is grounded in the patient’s history, current medications, lab results, and validated medical knowledge.

3. Full transparency — When DELPHOS provides an analysis, it explains its reasoning. No black boxes.

Note

This design reflects Brazilian medical regulations (Lei 12.842/2013), which establish exclusive physician prescribing authority. DELPHOS alerts and informs — it never prevents or overrides clinical decisions.

---

Domains

DELPHOS organizes clinical capabilities into domains, each handling a distinct aspect of healthcare delivery:

Clinical Documentation

Consultation sessions, real-time transcription, SOAP note generation, and immutable medical records.

Prescriptions

Medication search, drug safety validation, interaction checks, and digital prescription signing.

Scheduling

Appointment booking, calendar management, slot optimization, and patient communication.

Voice

Voice-controlled clinical workflows — dictation, scheduling, and patient queries, all hands-free.

Platform

Contract management, pricing queries, TISS billing, and administrative operations.

Patient Intelligence

Patient context, clinical summaries, lab trends, and longitudinal health analysis.

Each domain exposes its own set of API endpoints under /v1/. Domains are independent — you can use scheduling without clinical documentation, or prescriptions without voice.

---

Safety Model

DELPHOS implements a multi-layered safety model for clinical operations. The most visible example is the prescription safety pipeline, which validates every prescription through six sequential gates:

Gate	Purpose
Structural Validation	Ensures all required fields are present and well-formed
Drug Verification	Confirms the medication exists in the regulatory database
Dosage Check	Validates dose, frequency, and duration against safe ranges
Interaction Screening	Checks for drug-drug, drug-allergy, and drug-condition interactions
Duplicate Therapy	Detects overlapping prescriptions for the same therapeutic class
Regulatory Compliance	Verifies controlled substance rules and documentation requirements

Each gate produces a result: pass, warning, or alert. Warnings are informational; alerts require physician acknowledgment before proceeding.

---

Tenant Isolation

DELPHOS is a multi-tenant platform. Each tenant (clinic, hospital, or organization) has complete data isolation:

• API keys are scoped to a single tenant
• Row-level security enforces isolation at the database layer
• No cross-tenant queries are possible, even with a valid key
• Audit logs track every data access by tenant, user, and action

This means your integration code never needs to worry about data leaking between tenants — the platform handles it automatically.

---

Patient Privacy

DELPHOS follows strict privacy principles aligned with LGPD (Brazil’s data protection law) and international standards:

• No patient names stored — DELPHOS stores a SHA-256 hash of the patient name for deduplication, but never the name itself
• External ID mapping — Patients are linked to your system via external identifiers (e.g., your EHR patient ID)
• Audit trail — Every access to patient data is logged with the API key, timestamp, and action performed
• Soft deletes — Patient records are never physically deleted; they are deactivated with a full audit trail

---

Identifiers

DELPHOS uses two types of identifiers:

Type	Format	Example
Internal ID	UUID v4	550e8400-e29b-41d4-a716-446655440000
External ID	Your system’s ID	PAT-5678, ATD-2024-001234

Internal IDs are assigned by DELPHOS and used in API paths. External IDs are your system’s identifiers, passed during resource creation, and used for cross-system linking.

Tip

When creating patients or consultations, always pass your system’s identifier as the external_patient_id or external_consultation_id. This makes it easy to correlate DELPHOS data with your EHR records.

---

Next Steps

• Consultation Lifecycle — Start a clinical session
• Authentication — Set up API access
• Drug Safety — Understand the safety pipeline