1. Remote Patient Monitoring
  2. Integrations
Reference

Integrations

Plan patient, device, invoice and payment handoffs with clear source ownership.

  • Remote Patient Monitoring
  • Patient source
  • Device source
  • Invoice service
  • Payment source
  • Identity service

Systems to connect

  • Patient source. Agree where patient numbers and contact updates originate, and reconcile duplicates before monitoring.
  • Device source. Map device identifiers, metric types, units, observed times and source events to enrollments and readings.
  • Invoice service. Reconcile an authorized invoice against the approved service charge in the billing system, then mark the charge invoiced.
  • Payment source. Supply received date, amount and reference for a confirmed patient payment; reconcile it to the invoice outside the patient payment record.
  • Identity service. Link each active user identity to the corresponding staff record.

How connections are governed

Name the system of record for each value and the staff member who resolves rejected or repeated events. Test a late device reading, replaced device, repeated invoice callback and duplicate payment confirmation. The sending system must retain event identity so the team can compare it with the recorded value before retrying. Limit billing access to the encounter billing projection and keep clinical narrative within the care team.

Set up Remote Patient Monitoring your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started