MediChatApp Technical Architecture

How MediChatApp connects to Greenway Intergy and other enterprise EHRs, routes PHI safely, and powers patient access, messaging, and virtual assistants without disrupting your core system of record.

View architecture overview Security & compliance details
MediChatApp technical architecture

High-level architecture

MediChatApp sits between your EHR and your patients/staff, acting as a secure orchestration layer for messaging, check-in, portal access, virtual assistants, payments, and operational automation.

Today, MediChatApp is deeply integrated with Greenway Intergy. For health systems on other EHRs, we can connect via HL7 v2, FHIR, SFTP/flat files, and VPN-based interfaces to support migrations or parallel-run scenarios.

  • System of record: your EHR (e.g., Greenway Intergy; future support via standards for others).
  • MediChatApp: messaging, check-in, portal, automation, and VA workflows.
  • Edge channels: web, mobile, SMS, email, and call-center / VA consoles.
  • Security boundary: VPN, private network paths, role-based access, and audited events.
Textual diagram

1. Core EHR layer

Greenway Intergy (and, for larger health systems, other EHRs via HL7/FHIR/SFTP) remain the clinical and billing system of record.

2. Integration layer

Interfaces (HL7 v2, APIs, FHIR, batched files) sync schedules, demographics, balances, documents, and events into MediChatApp’s secure application layer.

3. MediChatApp application layer

Messaging, portal, check-in, virtual assistant task queues, and automation engines operate on controlled subsets of data with full auditing.

4. Channels & workforce

Patients access the system via web, mobile, SMS, and email; staff and virtual assistants access via authenticated dashboards, with VPN/MFA enforced for remote users.

Data flows & integration options

Designed for Greenway Intergy today, with patterns that extend to other enterprise EHRs using established healthcare standards.

Greenway Intergy integration
  • Schedules and appointments for messaging, check-in, and VA task queues.
  • Patient demographics for accurate outreach and portal access.
  • Balances and financial data for reminders and payment workflows.
  • Document links and results surfaced in portal and messaging workflows where appropriate.
Interfaces for other EHRs

For health systems running different EHR platforms, MediChatApp can connect via:

  • HL7 v2.x – ADT, SIU, ORM and related feeds.
  • FHIR APIs – where available and scoped appropriately.
  • SFTP / flat files – scheduled exports for rosters, schedules, or balances.
  • Custom interfaces – defined collaboratively with your integration team.
Inbound → MediChatApp
  • Patient and guarantor demographics.
  • Appointments and provider schedules.
  • Insurance and eligibility status (where available).
  • Balance and financial events for outreach and automation.
Outbound → EHR / partners
  • Structured check-in data and questionnaires routed back into your workflows.
  • Scheduling events, confirmations, and cancellations.
  • Task completion and outreach results (e.g., “patient confirmed,” “rescheduled”).
  • Payment confirmations from Stripe and related financial events.

Security & network boundaries

MediChatApp is designed with a defense-in-depth model, where PHI is only accessed within tightly controlled contexts and every action is auditable.

  • VPN & private networking for EHR and internal system connectivity.
  • Role-based access control with least-privilege principles.
  • MFA & device controls for staff and virtual assistants.
  • Application-level audit logging for key actions and PHI access.
  • Encrypted in transit & at rest for all PHI within MediChatApp’s scope.

For more details on encryption, logging, and incident response, see our Security and Legal & Compliance pages.

MediChatApp in your network
  • MediChatApp runs in a hardened cloud environment with network segmentation.
  • Connectivity to on-prem or hosted EHRs is typically via VPN, private link, or whitelisted IPs.
  • Optional isolation for test, staging, and production environments.
  • Subprocessors are limited, documented, and covered via BAAs where appropriate.
Virtual assistant access model
  • VAs operate as workforce members under MediChatApp, with documented policies.
  • Access is typically via VPN + named accounts + MFA.
  • Per-role access to PHI is restricted to what is needed for assigned workflows.
  • Activity is monitored and logged in MediChatApp and, where applicable, your EHR.

Deployment patterns & EHR migrations

Start with Intergy today, support migrations or parallel operations tomorrow.

Single-practice or multi-site group
  • Multi-tenant aware architecture for multiple locations and provider groups.
  • Per-practice configuration of branding, messaging rules, and VA programs.
  • Central reporting across locations for operations leadership.
Health system scenarios
  • Parallel operations during EHR transitions (e.g., Intergy → another EHR) using interfaces.
  • Ability to keep MediChatApp as the engagement and automation layer while core EHR changes.
  • Phased rollouts by site, specialty, or region with shared templates and playbooks.
Environment strategy
  • Dedicated test / staging environments for interface and workflow validation.
  • Change management around releases, with coordination for critical workflows.
  • Support for sandbox data and anonymized datasets where appropriate.
Monitoring & observability
  • Application health and queue monitoring.
  • Error and exception tracking for integrations and workflows.
  • Status page at /status/ for transparency with customers.

Want to review architecture with your IT & security team?

We’re happy to walk through diagrams, data flows, and interface options with your architects and compliance leads.

Schedule a technical review


💬 Ask a Question Schedule a meeting