faq.png

Frequently Asked Questions

RoundingWell strives for transparency and clarity in how our platform works and who uses it. If anything remains unclear or you still have questions not covered here, send us a message. We’re happy to answer your questions.

Who are the primary users of RoundingWell?

Organizations have deployed RoundingWell for multidisciplinary care teams–navigators, care coordinators, nurses, pharmacists, social workers, support specialists, etc. Oftentimes care teams are distributed across multiple locations, rely on a combination of dedicated and shared resources, and are involved in remote care delivery.

We already have an EMR. Why would I need RoundingWell?

RoundingWell is complementary to your EMR. We meet the extraneous needs of your care teams not being met by EMRs. Our customers tell us three main reasons for “Why RoundingWell?”

  • The ability to aggregate multiple sources of data, such as claims, roster files, deprecated systems, etc.

  • The ability to quickly replace outdated, disconnected tools (including paper and spreadsheets) with a shared workspace and standardized workflows

  • The ability to track and easily report on the data in RoundingWell at the per patient level and at the population level in aggregate

Over time, the EMR is used for its primary purpose–a record of the patient’s health history. RoundingWell becomes the primary tool to initiate, manage, and track forward-looking plans of care that care teams can work on together as they execute dynamic workflows that EMRs were never built to enable.

Can RoundingWell integrate with our other sources of data?

Yes. RoundingWell is architected to integrate with other health IT systems. We believe your data is your’s. The goal with any integration is to streamline workflows in RoundingWell and streamline reporting/analytics from RoundingWell to your other health IT systems. Our customers typically integrate roster/eligibility files, pharmacy or medical claims, and EMR data into RoundingWell. We have multiple integration methods depending on the source system and the use case.

  • HL7

  • Secure FTP

  • API

  • Integration partners, such as Redox Engine