eMDs API
eMDs (now part of CompuGroup Medical, CGM) is an ambulatory electronic health record (EHR) and practice management platform used by clinics, provider groups, and billing services to run front office scheduling, clinical documentation, and revenue cycle processes end to end. With an unofficial API, y
What is eMDs?
eMDs provides EHR and practice management software for ambulatory practices. It spans charting and orders, e-prescribing, lab interfaces, scheduling, registration, charge entry, claims submission, remittance posting, reporting, and quality programs.
Core product areas include:
- EHR charting and orders (notes, problem lists, medications, allergies, labs, imaging)
- Practice management and scheduling (registration, appointments, reminders, waitlists)
- Billing/RCM (charge capture, claim generation, clearinghouse submission, ERA posting)
- Patient communications and portal (documents, messaging, intake forms)
- Reporting and compliance (MIPS/MACRA, operational reports)
Common data entities:
- Patients and insurance policies
- Providers, locations, and payer master data
- Appointments and schedules
- Encounters/visits, diagnoses (ICD-10), and procedures (CPT/HCPCS)
- Charges, claims (837P/I artifacts), and remittances (835 payments/adjustments)
- Documents (C-CDA, PDFs), tasks, and messages
The eMDs Integration Challenge
Organizations rely on eMDs daily, but turning portal-based EHR/PM workflows into automated pipelines is non-trivial:
- Deployment variety: Hosted vs. on-prem variants and version differences impact authentication and data access
- Strong enterprise security: SSO/MFA and network controls complicate headless automation
- Portal-first workflows: Registration, scheduling, charge entry, and claim review often live in web apps without unified public APIs
- Batch and clearinghouse coupling: EDI timing windows, batching constraints, and delivery confirmations must be respected
- Code set and payer rules: ICD/CPT mapping, modifiers, and payer-specific edits require normalization
- Compliance nuances: PHI handling, audit trails, and retention policies demand care
How Supergood Creates eMDs APIs
Supergood reverse-engineers authenticated browser flows, batch interfaces, and network interactions to deliver a resilient API endpoint layer.
- Handles username/password, SSO/OAuth, and MFA (SMS, email, TOTP) securely
- Maintains session continuity with automated refresh and change detection
- Normalizes patients, appointments, encounters, charges, claims, and remittances into consistent schemas
- Aligns with customer entitlements and licensing constraints to ensure compliant access
- Bridges HL7/C-CDA exports and SFTP/EDI flows with signed URL retrieval and delivery
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your eMDs deployment, licensing, and authentication model.
- Supergood Builds and Validates Your API
We deliver a hardened eMDs adapter tailored to your workflows and entitlements.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as eMDs evolves.
API Endpoints
Authentication
/sessionsEstablish a session using credentials. Supergood manages MFA (SMS, email, TOTP) and SSO/OAuth when enabled. Returns a short-lived auth token maintained by the platform.
Patients
/patientsRetrieve patients with demographics, coverage, and primary relationships. Use this to populate your CRM, registration, or intake workflows.
Appointments
/appointmentsRetrieve appointment schedules and statuses across providers and locations. Use this to drive reminders, pre-visit intake, or front desk dashboards.
Claims
/claimsAssemble a professional claim (837P) from diagnoses and procedure lines. Supergood normalizes service lines and can route the generated file to the configured submission channel (clearinghouse, payer portal, or file export).
Use Cases
EHR/PM Synchronization
- Push or pull patient demographics and coverage to keep registration in sync - Align provider/location rosters, payer lists, and plan mappings - Maintain a single source of truth for patient and insurance data
Eligibility-Aware Scheduling
- Validate insurance eligibility before or during scheduling - Surface copays, plan type, and coverage dates to front office staff - Reduce denied visits and downstream billing issues
Charge Capture and Coding QA
- Create encounters and attach diagnoses/procedures with correct POS and modifiers - Run payer-specific coding checks before claims are generated - Attach documentation and notes for audit readiness
Claims Generation and Reimbursement Automation
- Bundle charges and diagnoses into 837P claims with payer-specific formatting - Submit via the configured channel (clearinghouse, payer portal, or file export) - Track claim statuses and reconcile ERAs with automated posting rules
Audit and Compliance
- Export encounter packets with notes, diagnoses, procedures, and attachments - Maintain machine-readable audit trails by user and timestamp - Prove claim provenance with linked encounter and documentation records
Technical Specifications
Authentication
Username/password with MFA (SMS, email, TOTP) and SSO/OAuth where enabled; supports service accounts or customer-managed credentials
Response format
JSON with consistent resource schemas and pagination
Rate limits
Tuned for enterprise throughput while honoring licensing and usage controls
Session management
Automatic reauth and cookie/session rotation with health checks
Data freshness
Near real-time retrieval of appointments, encounters, claims, and remittance artifacts
Security
Encrypted transport, scoped tokens, and audit logging; respects eMDs entitlements and HIPAA requirements
Webhooks
Optional asynchronous delivery for schedule updates, claim generation, and remittance posting events
Latency
Sub-second responses for list/detail queries under normal load
Throughput
Designed for high-volume scheduling and claims pipelines
Reliability
Retry logic, backoff, and idempotency keys minimize duplicate actions
Adaptation
Continuous monitoring for UI/API changes with rapid adapter updates
Frequently asked questions
Supergood supports workflows across commonly used CGM eMDs EHR and practice management modules, subject to your licensing and entitlements. We scope coverage (e.g., patients, scheduling, encounters/charges, claim assembly, remittance retrieval) during integration assessment.
We support username/password + MFA (SMS, email, TOTP) and can operate behind SSO/OAuth when enabled. For batch flows, we manage SFTP/EDI timing windows, generate 837 files, and retrieve signed URLs or delivery confirmations programmatically.
Yes. You can assemble 837P/I claims from diagnoses and procedure lines with payer-specific formatting. We can route submissions via your configured channel (clearinghouse, payer portal, or file export) and return statuses and artifacts for reconciliation.