Privacy Policy — MedGraph

Operated by Vigilo Health LLC, Texas  ·  Effective: October 15, 2026  ·  Contact: security@vigilomd.com

MedGraph ("we", "our") builds clinical-intelligence software for nephrology practices. This policy explains what information MedGraph accesses, how it is handled, and your rights. It applies to the MedGraph application, demo sites, and this website. This policy covers pre-production operation on synthetic data only and will be reissued before any real patient data is processed.

1. What data MedGraph accesses

When a clinic connects MedGraph to its electronic health record (EHR), MedGraph reads clinical data through the EHR's standards-based FHIR API using SMART on FHIR backend-services authentication. Access is read-only: MedGraph never writes to, signs, or alters the medical record.

The data read is the minimum needed to produce the pre-visit brief: encounter and visit history, problem lists, medications, laboratory results, vital signs, allergies, procedures, imaging and consultant reports, and clinical notes. This is protected health information (PHI) and is treated as such at every step.

We do not access data from any clinic or patient that has not authorized the connection, and we do not combine patient data across clinics.

2. How AI processing works (disclosure)

MedGraph uses artificial-intelligence models to read the connected chart and generate a plain-language clinical brief for the treating physician. The AI processes the chart data described above to identify interval events, changes, and potential blind spots. The brief is a decision-support aid for a licensed clinician — it is not a diagnosis, and the treating physician remains solely responsible for all clinical decisions.

To be finalized before production launch: the specific model providers and subprocessors that will handle PHI, their data-retention terms, and executed Business Associate Agreements (BAAs). Prior to production launch, MedGraph operates only on synthetic demonstration data — no real patient information is processed, and no clinic pilot is engaged.

3. What we do NOT do

4. Retention and deletion

Chart data pulled for a brief is retained only as long as needed to serve the connected clinic. The planned production defaults are: chart extracts and derived briefs are deleted 30 days after the appointment date and purged from backups within a further 30 days; access audit logs are retained 6 years; backups rotate every 30 days. These defaults are confirmed in each clinic's agreement before launch. Current data is synthetic and contains no real PHI. A clinic may request deletion of its data at any time by writing to security@vigilomd.com; we will confirm deletion in writing.

5. Security

Access to MedGraph systems is restricted to authorized personnel. Connections to EHRs use OAuth2/SMART on FHIR with RSA-signed authentication assertions; API keys and private signing keys are stored with restricted access. A key-rotation procedure is documented; the first rotation will be exercised in non-production before go-live. We will notify affected clinics and individuals as required by law in the event of a data breach.

6. Your rights

Patients: your medical record remains with your clinic — requests to access, correct, or delete your health information should go to your clinic, which controls the record. If you contact us, we will route your request to the right clinic promptly.

Clinicians and clinic staff: you may request a copy of the personal information we hold about you, or ask us to correct or delete it, at security@vigilomd.com.

7. Website and demo data

This website collects no accounts and no analytics at this time. This website is served through Cloudflare, which processes visitor IP addresses and security signals as our hosting intermediary. If analytics or contact forms are added, this section will be updated before they go live. Demo briefs shown publicly use synthetic patients only.

8. Children's privacy

MedGraph is a professional clinical tool and is not directed at children. We do not knowingly collect information from children.

9. Changes to this policy

We will post any changes here with a new effective date. Material changes affecting PHI handling will be communicated to connected clinics in advance.

10. Contact

Privacy or security questions: security@vigilomd.com.
Vigilo Health LLC, 5900 Balcones Drive STE 100, Austin, TX 78731 (registered agent address).

Appendix — data categories and the registered Epic APIs

Section 1's categories map to MedGraph's registered Epic FHIR R4 Read APIs (app ID 62087, marked Production Ready in Epic's portal) as follows: patient identity and demographics — Patient (Demographics); the appointment schedule — Appointment (Read); allergies — AllergyIntolerance (Patient Chart); the standing care plan — CarePlan (Longitudinal); problems, encounter diagnoses, reasons for visit, and outside-record diagnoses — Condition (Problems, Encounter Diagnosis, Reason for Visit, Outside Record Encounter Diagnosis); laboratory results, vital signs, social history, social-determinants assessment, and advance-directive status — Observation (Labs, Vital Signs, Social History, SDOH Assessment, Advance Directive); medications — MedicationRequest (Signed Medication Order, Outside Record) and MedicationDispense (Verified Orders); clinical notes and report documents — DocumentReference (Clinical Notes, Labs, Radiology Results, Outside Record - Clinical Notes, Advance Directive, External CCDA); encounter history — Encounter (Patient Chart, Outside Record); procedures — Procedure (Orders, Surgeries, Outside Record). No other Epic APIs are registered, and no write access exists.