A streamlined prenatal chart management system for OB practices, integrated with Epic via FHIR R4 APIs. Read-only access to patient demographics and laboratory results — nothing more.
This application requests only the data it needs. All access is read-only. No patient data is written back to Epic.
Name, date of birth, medical record number, and contact information to identify and display the correct patient record.
Read OnlyPrenatal lab values including CBC, blood type, Rh factor, rubella immunity, HIV, hepatitis, RPR, and GBS to pre-populate chart fields.
Read OnlyInfluenza, Tdap, and COVID vaccination history to populate the vaccine section of the prenatal chart without duplicate data entry.
Read OnlyActive problem list items relevant to obstetric risk stratification, surfaced in the OB Risk Factors section of the chart.
Read OnlyA straightforward OAuth 2.0 SMART on FHIR flow — industry standard, no custom protocols.
Physician authenticates to the OB Chart system using their existing credentials managed by the practice.
Doctor enters a patient chart number. The system initiates an OAuth 2.0 token request to the hospital's Epic FHIR endpoint.
Authorized lab values, demographics, and vaccine records are retrieved from Epic and used to pre-populate the prenatal chart fields.
The doctor reviews, completes, and saves the chart locally. No data is written back to Epic. The Epic record is never modified.
Security is not an afterthought. The architecture is designed from the ground up around HIPAA requirements and Epic's developer guidelines.
Authentication follows the SMART on FHIR specification. No Epic credentials are stored by this application at any point.
Patient data in transit is encrypted via TLS 1.2+. Data at rest is stored only within the practice's own database environment.
This application has no write scopes. It cannot create, update, or delete any records in the Epic system under any circumstances.
Patient chart data is stored in a database controlled by the medical practice — not transmitted to any third-party cloud service.
Every data access and chart modification is logged with user identity, timestamp, and field-level change tracking for compliance review.
Only the four FHIR resources required for prenatal chart pre-population are requested. No behavioral, mental health, or financial data is accessed.
Last updated: April 2026 | Eskelson OB Chart System
This application accesses the following patient data from Epic via FHIR R4 APIs, solely for the purpose of pre-populating the OB prenatal chart:
Data retrieved from Epic is stored only within the medical practice's own database, hosted on servers controlled by the practice. This application does not transmit patient data to any external server, cloud service, or third party.
Retrieved data is used exclusively to pre-populate fields in the OB prenatal chart form, reducing manual data entry errors. Physicians review all pre-populated data before saving.
Data retention policies are determined by the medical practice in accordance with applicable state and federal regulations. This application does not independently retain patient data beyond what is stored in the practice database.
For privacy-related questions or requests, contact us at gehoustontexas@gmail.com
For hospital IT departments, Epic administrators, or practice managers interested in connecting this application to an Epic instance — please use the form or contact us directly.