Medical Data Standards
EDH supports storage and display of medical data across multiple standards, enabling efficient interoperability with various healthcare systems. All data is end-to-end encrypted and stored on EVFS, giving patients full control over access to their own data.
FHIR (Fast Healthcare Interoperability Resources)
EDH supports the FHIR R4 standard for structured health data. FHIR data is stored in JSON format on EVFS.
Supported FHIR Resource Types
| Resource | Description | Example Usage |
|---|---|---|
| Patient | Patient information | Personal details, address, emergency contacts |
| Observation | Measurements and findings | Blood pressure, blood glucose, weight |
| DiagnosticReport | Diagnostic reports | Blood test results, urinalysis results |
| MedicationRequest | Prescriptions | Medications prescribed by a physician |
| AllergyIntolerance | Allergy and intolerance history | Penicillin allergy, seafood allergy |
| Condition | Diagnoses | Diabetes, hypertension |
| Encounter | Clinical encounters | Records of each physician visit |
| Immunization | Vaccination history | COVID-19 vaccine, influenza vaccine |
| Procedure | Procedures | Surgeries, medical procedures |
| DocumentReference | Document references | Links to PDF files, DICOM images |
FHIR File Viewer
Ever has developed components for rendering data in FHIR format, enabling medical records to be displayed across Ever's systems such as Health Wallet, OMA, HIS, and HIE. These components support human-readable rendering of FHIR Resources along with a timeline of medical events.
DICOM (Digital Imaging and Communications in Medicine)
EDH supports storage and display of medical images following the DICOM standard, the international standard for medical imaging.
Capabilities
- Image storage: CT Scan, MRI, X-ray, and Ultrasound images stored on EVFS with encryption
- DICOM Viewer: Displays medical images with measurement tools and brightness/contrast adjustment
- Metadata: Stores DICOM header information such as patient info, study info, and series info
- Privacy: Patient-identifying information in DICOM headers is encrypted alongside the file, preventing personal data leakage
VCF (Variant Call Format)
EDH supports VCF files for genomic data, which is a key component of the BIA (Biological Identity Attestation) system.
VCF Usage in EDH
- Genomic data storage: VCF files are encrypted and stored on EVFS just like any other file
- SNP Identity Panel: The BIA system extracts SNP markers from VCF files to create a genomic identity profile
- HLA Genes: Extracts HLA gene data for medical matching purposes
- Poseidon Commitment: SNP and HLA data are hashed using the Poseidon hash function to generate a commitment for registration on the BioAnchorRegistry
Raw VCF data is never uploaded to the blockchain. Only the Poseidon commitment is recorded on-chain, and it cannot be reversed to recover the original genomic data.
Documents and General Files
EDH supports document and image files for storing unstructured medical data.
| File Type | Extension | Example Usage |
|---|---|---|
.pdf | Laboratory results, prescriptions, physician reports | |
| JPEG | .jpg, .jpeg | Wound photographs, skin photographs |
| PNG | .png | Device-captured images, test result charts |
| TIFF | .tiff | High-resolution medical images |
| Plain Text | .txt | Physician notes, clinical remarks |
Healthcare System Integration
EDH can connect to existing healthcare systems through multiple channels.
EDH Adaptor (PHR Integration)
The EDH Adaptor is a service that connects a hospital's Personal Health Record (PHR) system with EDH.
Hospital HIS → PHR Adaptor → EDH Account Service → Smart Contract + EVFS
↓
Google Cloud Pub/Sub
(async processing)
- Receives health data from the hospital's HIS
- Automatically creates EDH accounts for new patients
- Uses Google Cloud Pub/Sub as a message queue for asynchronous processing
- Stores PHR data with CID references on EVFS
Integration Methods
| System | Description | Integration Method |
|---|---|---|
| HIE (Health Information Exchange) | Health data exchange platform | EDH API Service + FHIR |
| HIS (Hospital Information System) | Hospital information system | PHR Adaptor + Pub/Sub |
| OMA | Ever's medical administration system | Direct EDH SDK |
| Health Wallet | Ever's health wallet | ever-edh-core SDK |
Regulatory Compliance
EDH's architecture is designed to comply with health data security requirements across multiple regulatory frameworks.
HIPAA (United States)
| Requirement | EDH Support |
|---|---|
| Encryption at rest | Files are encrypted with NaCl secretbox before storage |
| Encryption in transit | E2E encryption — data is encrypted before transmission |
| Access controls | Smart contracts govern access permissions |
| Audit trails | Blockchain records immutable transactions |
GDPR (European Union)
| Requirement | EDH Support |
|---|---|
| Right to erasure | Key revocation = logical deletion (encrypted data is unreadable without the key) |
| Data portability | FHIR data can be exported in a standardized format |
| Consent management | Patients control data sharing through cryptographic access control |
| Data minimization | Poseidon commitment does not expose raw genomic data |
PDPA (Thailand)
| Requirement | EDH Support |
|---|---|
| Data localization | EDH nodes can be deployed within Thailand |
| Consent | Patients control all data sharing |
| Data subject rights | Sovereign wallet gives patients true ownership of their data |
| Data breach prevention | E2E encryption ensures the server cannot read data |
See Also
- File Storage — EVFS and Cryptree encryption
- BIA Developer Quickstart — Biological Identity Attestation system
- BioAnchorRegistry — Smart contract for genomic commitment
- Ever Services — Ever's supplementary services