Bring your history forward.
Map legacy exports and document collections into an agreed destination. Review duplicates, field mappings, record counts, attachments and exceptions before an accepted cutover.
Move the records.
Improve the work around them.
Software, data and operating support for DME companies and referring offices. Select the services that fit your current systems, team and priorities.
Make incomplete records actionable.
Organize existing documents and permitted reference information into a clearer patient account. Preserve source provenance, flag conflicts and put uncertain matches in a human review queue.
Find records that deserve billing review.
Review an agreed historical population for potentially unbilled delivered items, unresolved claims, incomplete evidence and missed follow-up. Reconcile prior billing and payment before pursuing an opportunity.
Explain where the money stops.
Analyze intake holds, documentation delays, rejections, denials, aging and payment posting. Deliver a prioritized findings register with responsible owners and measures for follow-up.
Help the right people find you.
Set up service-area and modality pages, local business information, product discovery, inquiry routing and campaign measurement. Align the promise on the website with what the operation can fulfill.
Give every referral a clear handoff.
Set up a referral-source directory, office contacts, territories, relationship owners, outreach tasks and status follow-up. Track missing information and responsiveness so referring offices know the next step.
Put policy into daily practice.
Policy-and-procedure setup for DME suppliers across all DME accrediting bodies, tailored to the selected accreditor, current standards, product categories, locations and actual operating practices.
Explore policy & procedure setup ↗Useful deliverables.
Clear acceptance.
An agreed engagement can include a data map, trial import, reconciliation report, exception queue, workflow configuration, staff walkthrough and follow-up dashboard. Deliverables, source access and ongoing management are scoped before work begins.
Evidence comes before an opportunity.
Patient-data enrichment does not create clinical facts, signatures or medical necessity. Claim discovery does not mean automatic billing or guaranteed recovery. Review payer rules, filing limits, documentation, duplicate billing and prior payment before action.
PHI work requires the applicable BAA and approved access arrangements. Do not upload records to this public site.
A manual your team
can put to work.
SoFloAI offers policy-and-procedure setup across DME accrediting bodies. Each engagement maps the supplier’s selected accreditation program and applicable CMS DMEPOS Quality Standards to its services, modalities, locations and staff responsibilities.
Define the requirements.
Review the current standards supplied or licensed for the engagement, existing policies and the actual operation. Identify gaps and build a requirements-to-policy checklist for the agreed scope.
Build usable procedures.
Scope written policies, work instructions, forms and logs for relevant areas such as patient rights and complaints, staff training, equipment handling, infection prevention, emergency planning, delivery, documentation and quality improvement.
Make implementation visible.
Assign policy owners, approval dates, version control, staff acknowledgements and review schedules. Organize evidence and corrective-action follow-up so the team can explain how its procedures are used.
Deliverables may include a customized manual, gap assessment, forms and logs, staff orientation and a survey-readiness review. The final scope follows the chosen accreditor’s current requirements and the supplier’s services. Accreditation decisions remain with the accrediting organization; setup does not guarantee approval or imply accreditor affiliation.
Onboarding in
under 45 days.
Start from an agreed kickoff once your scope, agreements and required access are ready. Your onboarding plan connects setup, any agreed data import, staff training and acceptance to a clear launch decision.
Agree the starting point.
Confirm locations, modalities, modules, contacts, source systems and responsibilities. Complete the applicable agreements and define the acceptance checklist.
Configure and prepare.
Set up the agreed workflows, permissions, reference materials and integrations. Reconcile any scoped data import and resolve exceptions with the responsible team.
Train, verify and launch.
Walk staff through their roles, check the agreed workflows and confirm support and escalation paths before activation.
The written plan defines included work and customer dependencies. Review scope changes or missing access together before revising the schedule. The free 14-day pilot starts on its confirmed activation date.
Plan my onboardingThe right starting setup.
An accountable next step.
Task management
Configure staff assignments, due dates, recurring work, priorities and escalation paths around intake, documentation, delivery, billing and quality review. Agree the enabled task workflows and verify them before customer activation.
State & federal requirements
Preload the agreed reference materials, checklists and workflow requirements for the customer’s operating states, locations, product categories and applicable federal programs. Identify source, effective date and a responsible review owner; validate applicability during setup.
Applicable fee schedules
Load the agreed fee-schedule references for the relevant payer, locality, code and effective period, using authorized sources. Review modifiers and purchase or rental context. Schedule amounts are reference values; actual reimbursement depends on the claim, coverage and payer terms.
Implementation includes agreeing which references are included, how revisions are reviewed and who maintains them. Customer-specific configuration is accepted before use; a preloaded reference does not establish automatic compliance or guarantee payment.
CMS DMEPOS fee-schedule reference ↗Keep a path to help
open after hours.
SoFloAI offers 24/7 phone service and help-desk support as part of the agreed service scope. Define call handling, request intake, issue categories, ticket ownership, escalation contacts and follow-up so after-hours requests have a clear route.
Support for the agreed operation.
Scope software assistance, business phone handling and service-request routing around the customer’s needs. Specify any AI-assisted handling, human coverage, supported channels and data permissions before activation.
Set clear service expectations.
The service agreement defines response targets, escalation coverage and resolution responsibilities. Around-the-clock availability does not imply immediate human resolution, clinical advice or emergency dispatch.
Bringing DME into a pharmacy?
Explore a focused add-on or broader conversion plan, complementary modalities, revenue-cycle planning and payer-facing portfolio preparation.
Portfolio & LOA/LOI support
Scope the required business materials, recipient-specific paperwork and authorized review process.
Explore pharmacy-to-DME services ↗A PRACTICAL START
Discuss my service scope Explore real-world scenariosChoose the handoff that needs attention.
Start with a discovery conversation about one workflow, one source system or one defined historical cohort.
Services are scoped separately from the limited 14-day software pilot. No fixed price, recovery amount, lead volume or referral outcome is promised.