Remote monitoring
Connected-device readings, qualifying transmission days, review queues, interactive communication and treatment-management records.
Connected-care platformOne patient context.
One patient context.
A coordinated care program.
Connect clinical eligibility, patient engagement and service delivery with the records your practice already uses. InstaMD brings monitoring, care coordination and billing evidence into a shared workflow for your team and qualified contracted providers.
Program configuration
A shared foundation for different care needs.
Configure each patient’s services around clinical need, practitioner responsibility and payer requirements. Shared records reduce repeated work while preserving program-specific evidence.
Care-plan management
Disease-specific or comprehensive plans, patient goals, medication and referral follow-up, and separate activity and time records.
Primary-care coordination
Support the responsible primary-care practitioner’s care plan, access and continuity arrangements, transitions and population review.
Barrier resolution and navigation
Document initiating assessments, patient needs, community referrals and navigation follow-through with qualified personnel.
Qualified-provider workflows
Coordinate behavioral care and nutrition referrals, assessments and follow-up. Retain the appropriate professional roles and service requirements.
Benefits support
Track screening, application assistance, eligibility decisions and effective dates so the care team and billing staff share current benefit information.
Patient and program workflow
From identification to a documented monthly review.
Build the eligible population
Review available rosters, diagnoses, utilization and scheduled encounters. Route potential candidates to clinician review.
Establish clinical and coverage fit
Capture medical-necessity evidence, required visits and authorizations, payer checks and consent. Confirm existing care-management services.
Assign the care team
Activate appropriate programs, establish care goals and name responsible practitioners, coordinators and contracted providers.
Act on readings and care needs
Prioritize readings, missed engagement, symptoms and outstanding referrals. Escalate concerns under the practice’s approved protocols.
Keep evidence attached to the service
Record actual work, staff identity and time where required. Maintain orders, referrals, consent, plan updates and clinical decisions.
Review care progress and billing readiness
Check missing evidence, concurrent services and payer requirements before preparing billing output. Track exceptions and follow-up.
Integration options
Connect through the path your environment supports.
Integration scope depends on the EHR, licensed interfaces, customer permissions and implementation agreement. Confirm supported data, read/write capabilities and operational ownership during discovery.
Epic embedded workflows
Extend the existing RPM and kidney-transplant workflow approach into the agreed enterprise deployment. Define which chart context, orders, consent and program data can be accessed or written back.
FHIR and SMART on FHIR
Where the EHR supports them, use authorized patient-context launch and FHIR resources for demographics, conditions, observations and other agreed records. Confirm resource versions, scopes and write access.
HL7 interfaces
Connect supported clinical messages through the organization’s interface engine. Agree message types, field mappings, patient identifiers, acknowledgements and error handling.
Web-based EHR layer
Use a browser extension or workflow layer for approved chart tasks. Validate compatibility, user permissions and supported actions for each EHR and version.
Desktop workflow companion
Support approved tasks in non-browser environments through a lightweight companion. Confirm environment compatibility, deployment permissions and the scope of automation.
Files and chart intake
Define roster and document intake using agreed file formats and approved transfer routes. Review imported data and extracted clinical information before it drives care or billing.
Physiologic data feeds
Connect supported cellular devices and vendor feeds to the patient record. Validate device assignment, timestamps, units, duplicate readings and transmission status.
APIs, reporting and billing exchange
Use available APIs or agreed exports for program status, reporting and billing handoff. Confirm payer or billing-system connectivity, acknowledgements and reconciliation needs.
Data and workflow controls
An integration is complete when the team can use the result.
The right information in the right chart
Agree identifier matching and review ambiguous records. Keep the source and timing of information visible to the care team.
Consistent clinical meaning
Validate units, code mappings and required fields. Route incomplete or conflicting information for review before downstream use.
Visible handoffs
Define how successful receipt, rejected records, retry handling and unresolved interface issues are tracked for each connection.
Clear permissions and responsibility
Define authorized access, contracted-provider responsibilities, record retention and audit requirements as part of the deployment.
Practice and enterprise views
See what needs attention across the program.
Patient review and escalation
Review current goals, monitoring trends, open concerns and the status of follow-up. Clinical decisions stay with the responsible practitioner.
Outreach and coordination
Track enrollment progress, missing readings, upcoming tasks, referral status and care-team workload.
Service evidence and exceptions
Review qualifying work, missing documentation and program overlap. Separate clinical-staff time from practitioner time and non-time-based services.
Performance over time
Review patient engagement, escalation closure, care-plan progress and operational measures by practice, provider or agreed cohort.
Implementation
Define scope, validate the workflow, then expand.
- Confirm the care model
Select programs, clinical ownership, contracted providers and the first patient cohort.
- Map data and permissions
Agree source systems, patient identifiers, interfaces, access, fields and write-back requirements.
- Validate representative cases
Check record matching, clinical meaning, documentation flow, escalation handling and billing exports.
- Launch and review
Start with the agreed cohort, review exceptions and performance, then expand the approved scope.