Role-based access
Manage staff access levels and permissions across facilities and care teams.
How does PCL Health protect patient data? PCL Health provides role-based access, consent management and audit logs to support patient-data protection. Administrators manage staff permissions across facilities and care teams. PCL Health records activity for internal review and supports consent collection during intake and ongoing care, alongside care plans, notes and patient documentation.
Last updated:
SECURITY AND PRIVACY
HIPAA-compliant. US-hosted.
Built into the workflow.
Role-based access, consent management and audit logs support the way your teams manage patient information.
Book a demo
PLATFORM FEATURES
Controls for collaborative care.
Consent management
Collect and manage patient consent as part of intake and ongoing care.
Audit logs
Review logged activity for internal review.
HIPAA and BAA
HIPAA-compliant platform. US patient data is hosted in the United States on AWS and encrypted in transit and at rest. BAA available.
Certifications
ISO 27001 and Cyber Essentials Plus.
BUYER QUESTIONS
Frequently asked questions
How does PCL Health protect US patient data?
PCL Health supports role-based access, consent management and audit logs. The HIPAA and BAA card on this page describes PCL Health’s US data hosting, encryption and BAA availability.
How does PCL Health manage role-based access?
PCL Health administrators manage staff access levels and permissions across facilities and care teams. PCL Health also supports staff and clinician management.
How does PCL Health support patient consent?
PCL Health supports consent collection and management as part of intake and ongoing care. PCL Health consent information can be reviewed alongside the patient record.
What are PCL Health audit logs used for?
PCL Health records activity for internal review. PCL Health teams can review logs alongside care plans, notes and documentation.
LET’S CONNECT
Put the platform to work for your team.
FROM INSIGHTS
Explore the RPM workflow.
White-label RPM: build, license or buy a platform
White-label RPM buyers should compare building, licensing and acquisition by the rights, responsibilities and operating work each option creates. Choose a model after testing the patient-to-clinician workflow and reviewing the contract scope. A branded interface alone does not answer questions about clinical staffing, data access or ongoing platform maintenance.
Read article
RPM billing requirements: current rules and what CMS has proposed
RPM billing requirements depend on the service delivered, the applicable code and the records supporting that service. Practices should apply current requirements and treat the CY 2027 staffing and initiating-visit changes as proposed, not effective policy.
Read article
The 2027 proposed RPM rule: a checklist for practice managers
Practice managers should prepare a staffing map, an onboarding review and a final-rule update plan for the proposed 2027 RPM changes. The proposal is not a reason to treat future requirements as effective today.
Read article