DME Website + AI Document Intake + RingCentral Fax
THE PROVIDER CAN SEND THE ORDER. THE PATIENT CAN PAY THE BILL.
How we gave a Texas DME supplier a modern public site, AI-assisted provider intake, RingCentral fax delivery, and Paragon-hosted online payments.
01 / Context
Community Medical
Community Medical Supply is a family-run DME supplier founded in 1973 and based in Fredericksburg, Texas. The company works with clinicians, case managers, patients, and families across the Hill Country. Its site needed to respect a long local history while handling two practical jobs online: help providers submit complete orders and give patients a safe way to pay an invoice.
02 / Challenge
Two Offline Tasks, One Public Site
Provider paperwork and patient billing lived outside the website. Community needed online paths for both without putting medical records and card data into the same system.
03 / Approach
Provider Intake and Patient Payment
We rebuilt the public site around the two people most likely to arrive with a task. Providers can submit and fax order documents. Patients can pay an invoice through a hosted processor flow with clear return states.
04 / Background
Fifty-three years of local service, rebuilt for the way people work now.
Community Medical Supply has served Fredericksburg and the surrounding Hill Country since 1973. We used that history as the frame for the public site, then organized the product around what people arrive to do. A clinician needs to send an order. A patient needs supplies or has a bill to pay. Both should find the right path quickly.
05 / The public site
A clear front door for patients and providers.
The site explains the core catalog, the service area, insurance support, delivery, and the company story without turning the homepage into a product directory. Providers can go straight to Parachute Health or open the resources section. Patients can contact the team or pay a bill from the main navigation.
06 / Provider intake
The site does the first pass. The clinician checks it.
A provider can upload a facesheet, order sheet, or supporting record. The site combines multiple PDFs, sends the packet to AWS Bedrock, and pre-fills the standard order with the patient, insurance, provider, wound, and supply details it can read. The review screen keeps every field editable and leaves missing data visible.
07 / Fax delivery
The referral and completed order stay in the same packet.
Once the provider approves the fields, the app generates and flattens the order PDF. The confirmation step lists every attachment before RingCentral sends the completed form with the original referral documents.
08 / Online bill pay
Card details stay on Paragon.
Patients can start a payment from the Community site without creating an account. The app sends them to Paragon Payment Solutions for the invoice number, amount, and card entry, so card details do not pass through Community Medical Supply servers. Paragon returns the result to a dedicated route that sends the patient to a clear success or failure state.
09 / Payment confirmation
The patient always leaves with an answer.
An approved payment shows a confirmation number, amount, invoice reference, and masked card details. If the processor returns without a clear result, the site tells the patient that the payment may have succeeded and asks them to verify before trying again. The payment button disables after the first click, and a short-lived recent-payment warning catches another common route to an accidental duplicate.
10 / The result
The site now handles both sides of the transaction.
Providers can submit the documents that start an order. Patients can settle the invoice that follows. Community Medical Supply keeps its existing Parachute, RingCentral, and Paragon relationships, while the public site gives each system a clear place in the customer journey. No adoption, payment-volume, or processing-time result is published.
The same site handles provider paperwork and patient payment without mixing the two workflows.