How It Works

A guide to Force’s virtual care continuum and how the platform works.

Created with Sketch.


HIPAA Compliant logo


Increase in Patient Satisfaction


Reduction in Post-Acute Costs


Average Pre- & Post-Op Automated Outcomes Collection


Reduction in Hospital Length of Stay


Reduction in Hospital Readmissions

Technical Details

Force Intelligent Care Plan graphic


100% HIPAA & SOC2 compliant

Ad-Hoc Tasks graphic


Patient and provider accessibility from all hardware (desktop, tablet and mobile), software (Mac OS and Windows), and web browsers (Safari, Chrome, IE, etc.)

research platform

Cloud-Based Software

Cloud-based software, hosted by Amazon Web Services

registry integration for EHR integration

EHR Integration

Integration capabilities with all major EHR systems (Epic, Cerner, Allscripts, eClinicalWorks, athenahealth, etc.)

Real-Time Alerts graphic

Free Apps

Free apps available via App Store and Google Play, plus mobile responsive patient web design

Care Team Workflow Management

Ad-Hoc Tasks graphic

Case Scheduling

Scheduling involves building an outbound integration from the EHR to Force. When a patient is scheduled for surgery this integration allows the patient to be created in Force automatically. This increases efficiency because once it’s implemented, the clinical staff no longer has to manually create the patient in Force. Force establishes a connection with the client’s scheduling interface. Other options available if one does not exist.

Discrete Data and PROMs Collection graphic

Outcomes/ Observation

Outcome Scores data is sent from Force, back to the EHR. First, Patient Reported Outcomes scores are sent to the EHR through an ORU / Observation interface. This allows outcomes data to be stored discretely as results, so reporting from the EHR is made possible (reporting capabilities and enterprise analytics are also available within Force).

Publication & Abstract Support

Episode Summary/ Transaction

A complete synopsis of all the interactions the patient had on Force, sent as a PDF. This allows storage and review of each patient’s recovery episode from within the EHR. Can be delivered through an MDM/Transcription interface or through an SFTP to be picked up by an enterprise content management solution (e.g. OnBase).

Force Content Library graphic

Patient Single Sign On

Force supports SAML Single Sign-On as a Service Provider. As the Service Provider, Force can send the patient login links that initiate SSO and bring the patient to the patient portal to login. Once they successfully authenticate at the patient portal, they are immediately redirected and logged into Force, meaning a separate Force username and password is not required. For this integration, strategies are developed to drive up portal engagement and encourage portal use after patient recovery.

registry integration for EHR integration

Provider Single Sign On

For providers, Force supports an Identity Provider initiated SSO workflow, where a button is placed in the EHR that launches an internet browser window and automatically logs the provider into Force. This means a provider can seamlessly jump from EHR to Force quickly without a disruption in workflow

Force Intelligent Care Plan graphic

Force Intelligent Care Plan

An improvement to the current clinician experience of building a library of different pathways. The new program is found on a
rules-based engine composed of a singular master care plan with configurable rules that dynamically adjust remote patient care.

Bridge the outcomes gap at your organization. If you're a patient, please email for questions about your account.

* indicates required