How to Choose a HIPAA-Compliant Remote Patient Monitoring Company
Choosing a remote patient monitoring (RPM) company involves more than checking whether it advertises HIPAA compliance. You need to assess how the service protects protected health information (PHI), fits your clinical workflows, supports your devices, and handles incoming readings.
Use the questions below to compare vendors. Treat claims about security, integrations, staffing, and service levels as items to verify in writing—not as substitutes for your practice’s own risk assessment.
Which HIPAA safeguards should a remote patient monitoring company use?
If an RPM company handles electronic PHI on your behalf, it will generally be a business associate. The HIPAA Security Rule calls for appropriate administrative, physical, and technical safeguards to protect the confidentiality, integrity, and availability of electronic PHI. Ask how the vendor’s safeguards address your practice’s risks, not just whether it has a general security policy. See the HHS Security Rule overview.
Ask the company to explain how it conducts risk analysis, manages workforce access, responds to security incidents, and protects data across its systems and devices. Practical controls to discuss include:
- Encryption at rest and in transit: Ask which data is encrypted, where encryption applies, how encryption keys are managed, and what safeguards protect data when a device or connection is lost. Under the Security Rule, encryption is an addressable implementation specification: the organization must assess whether it is reasonable and appropriate, document its decision, and use an appropriate alternative measure when warranted. HHS explains addressable specifications.
- Role-based access controls: Find out whether each user has a unique account and whether access can be limited by job function. Ask about multifactor authentication, prompt removal of access when staff leave, and controls for vendor support personnel.
- Audit controls: Ask what events are recorded, such as viewing or changing patient records, exporting data, and administrative access. Clarify how you can review or obtain logs and the vendor’s audit log retention period. The Security Rule requires mechanisms to record and examine activity in systems containing or using electronic PHI; it does not set one universal retention period for every audit log. See the technical safeguards at 45 CFR § 164.312.
- Backups and recovery: Ask how the company handles outages, data loss, ransomware, and recovery testing, and how your staff can access essential information during downtime.
- Incident response: Confirm who at the vendor will notify your practice about a suspected security incident, how quickly, and what details and cooperation you can expect during an investigation.
HIPAA safeguards are risk-based; a vendor’s checklist alone cannot establish that the overall arrangement is appropriate for your practice. Review the vendor’s responses alongside your own security policies and risk analysis.
What should a Business Associate Agreement cover?
If the company is a business associate handling PHI for your practice, put a Business Associate Agreement (BAA) in place before permitting it to create, receive, maintain, or transmit that information on your behalf. The BAA should match the services you are buying and clearly define the vendor’s permitted uses and disclosures of PHI. HHS describes the required provisions in its business associate contract guidance.
Check that the agreement addresses safeguards, reporting of security incidents and breaches, cooperation with your privacy obligations, and the vendor’s obligations when the relationship ends. It should also explain what happens to PHI at termination, including return or destruction where feasible, and authorize termination for a material breach.
Review how the BAA covers subcontractors that handle PHI for the vendor. HIPAA requires the business associate to obtain appropriate written assurances from such subcontractors; the agreement should make those responsibilities clear. HHS also notes that a business associate’s obligations do not disappear just because it uses a cloud service. See HHS guidance on HIPAA and cloud computing.
Compare the BAA with the service agreement, privacy terms, and any service-level agreement. Check that their provisions on data use, security responsibilities, incident notice, availability, backups, and data return do not conflict. Ask a qualified legal or privacy professional to review terms that are unclear or inconsistent.
How can you verify vendor and subcontractor security practices?
Ask for evidence that helps you assess the vendor’s security program. Depending on your practice’s needs, that may include a recent independent assessment or audit report, a summary of penetration testing, security policies, incident-response procedures, and details about workforce training and access reviews. Clarify the report’s scope, date, limitations, and whether it covers the product and services you will use.
Ask which subcontractors may create, receive, maintain, or transmit PHI, what functions they perform, and how the vendor confirms they are contractually required to protect that information. This is especially important for cloud hosting, analytics, messaging, device connectivity, and technical support. HHS explains that business associates must obtain appropriate assurances from subcontractors handling electronic PHI in its Security Rule summary.
Do not treat a “HIPAA-certified” label or a training certificate as proof that the organization is compliant. HHS states that HIPAA does not provide for business associates to self-certify or be certified by a third party as compliant. Ask instead for relevant evidence, review the BAA, and assess the responsibilities and controls that apply to your arrangement. See the HHS Business Associates FAQs.
Your review should be proportionate to the PHI involved and the service’s risks. Document what you reviewed, what the vendor is responsible for, and any gaps you need to address before launch.
How will the platform integrate with your EHR and existing workflows?
Ask the vendor to demonstrate how patient enrollment, readings, alerts, notes, and follow-up tasks move between the RPM platform and your electronic health record (EHR). Confirm whether information flows automatically, requires staff review, or must be entered manually. A connection described as an “integration” may not support every workflow your team needs.
Discuss patient matching, duplicate-record prevention, data mapping, user permissions, and how corrections are handled. Ask whether the connection is based on an application programming interface (API), a standard such as HL7 FHIR, or another method. FHIR is an API-focused standard for representing and exchanging health information, as described by the Office of the National Coordinator for Health Information Technology.
Before rollout, test the full workflow with your EHR and staff: enrollment, device pairing, incoming readings, alert routing, documentation, and downtime procedures. Ask who configures and supports the connection, what changes may disrupt it, and how the parties will troubleshoot failed or delayed data transfers.
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free TodayWhich devices and readings does the service support?
Make a list of the readings your program needs, such as blood pressure, blood glucose, weight, oxygen saturation, temperature, or heart rate. Then verify that the vendor supports the specific device models, connectivity methods, patient population, and measurement schedule you plan to use. Do not assume that support for one device or reading means the platform supports all models or clinical use cases.
Ask how devices are shipped, paired, replaced, and supported when patients have limited internet access, low technical confidence, or accessibility needs. Clarify what happens when a device disconnects, a reading is missing, or a value appears implausible. Confirm that the data displayed in the platform includes enough context—such as units, time stamps, and patient identity—for staff to interpret it safely.
For measurements that depend on device accuracy, check the device’s intended use and applicable FDA status. For example, the FDA warns that unauthorized blood-pressure-measuring devices may produce inaccurate readings and recommends using an appropriate FDA-authorized device when care depends on the measurement. See the FDA safety communication on blood-pressure devices.
How are patient readings reviewed and escalated?
Ask who reviews readings, during which hours, and what happens when a reading crosses a threshold. The vendor should help you define a written escalation plan that identifies who receives alerts, who is responsible for clinical review, how urgent concerns are communicated, and what staff should do if the assigned reviewer is unavailable.
Confirm whether alerts are configurable and how the team can distinguish urgent readings from routine trends or technical issues. Ask how the platform handles repeated alerts, patient nonresponse, missing readings, and failed device connections. Determine whether the vendor’s staff are providing technical support, clinical monitoring, or both—and define those responsibilities clearly in the service agreement and operating procedures.
Set expectations for response times and after-hours coverage that fit your program. Test alert routing before enrolling patients, and document how staff will record review, outreach, clinical decisions, and escalation. Do not assume that an automated alert means a clinician has reviewed a reading or that the vendor is providing emergency monitoring.
How should you compare support, costs, and vendor reliability?
Compare the full cost of operating the program, not only the platform fee. Ask for written pricing that itemizes setup, devices, connectivity, shipping, replacements, integration work, training, technical support, and any per-patient or usage-based charges. Check minimum terms, renewal and price-change provisions, cancellation fees, and costs for exporting or migrating your data.
Evaluate support by asking who your staff and patients can contact, when support is available, how urgent problems are escalated, and what response times the vendor commits to. Request references from organizations with similar workflows or patient populations, and ask about service availability, outages, recovery practices, and product changes that could affect care.
Review the exit plan before signing. Confirm the data format and process for exporting records, how long the vendor will make data available after termination, and how PHI will be returned or destroyed as agreed. HHS identifies availability, backup and recovery, data return, security responsibility, and retention limits as topics that may be addressed in a service-level agreement with a cloud service provider. See HHS cloud computing guidance.
Choose the company whose documented safeguards, subcontractor risk management, device support, escalation model, integration, and total costs fit your practice’s needs. Put responsibilities in writing, test the workflow before launch, and revisit the arrangement as your service or risks change.
FAQs
Should a Business Associate Agreement be signed before sharing patient data?
Generally, yes—if the RPM company is a business associate that will handle PHI on your practice’s behalf, put the required written agreement in place before permitting it to handle that information. The BAA should cover the services and data involved. HHS explains the contractual requirements in its business associate contract guidance.
How can a practice verify a remote monitoring vendor’s HIPAA safeguards?
Review the vendor’s security documentation and relevant independent assessment reports, ask about encryption, access controls, audit logs, incident response, backups, and subcontractors, and confirm that the BAA matches the service. A certification label alone is not proof of HIPAA compliance; HHS says HIPAA does not establish a third-party certification process for business associate compliance. See the HHS Business Associates FAQs.
Who is responsible for HIPAA compliance when using a monitoring company?
Responsibility depends on each party’s role and the specific HIPAA requirements that apply. Your practice remains responsible for its own obligations, such as conducting its risk analysis and managing its use and disclosure of PHI. A business associate also has direct obligations under HIPAA, including applicable Security Rule duties. A BAA defines contractual responsibilities but does not make the practice’s obligations disappear. See HHS guidance on covered entities and business associates.
What should a practice check before connecting an RPM platform to its EHR?
Confirm which data and workflows the connection supports, how patient records are matched, which staff can access or change information, how errors and outages are handled, and who supports the integration. Test enrollment, device readings, alerts, documentation, and downtime procedures before relying on the connection in routine care.
Table of Contents
- Which HIPAA safeguards should a remote patient monitoring company use?
- What should a Business Associate Agreement cover?
- How can you verify vendor and subcontractor security practices?
- How will the platform integrate with your EHR and existing workflows?
- Which devices and readings does the service support?
- How are patient readings reviewed and escalated?
- How should you compare support, costs, and vendor reliability?
- FAQs
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free Today