← All case studies

Community Medical Supply

Project Focus
DME Website AI Document Intake RingCentral Fax Online Payments Healthcare UX

Community Medical Supply

THE PROVIDER CAN SEND THE ORDER. THE PATIENT CAN PAY THE BILL.

Strategy

  • DME Website
  • AI Document Intake
  • RingCentral Fax
  • Online Payments
  • Healthcare UX
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.

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.

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.

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.

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.

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.

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.

Public Site
Provider Resources
Extracted Field Review
Online Bill Pay
Payment Confirmation

The same site handles provider paperwork and patient payment without mixing the two workflows.

By the numbers

Visit live site
1973
Established
Fredericksburg and the Texas Hill Country
AI Review
Provider Intake
Extract, correct, generate
RingCentral
Fax Delivery
Referral plus completed order
Paragon
Online Payments
Hosted card entry

Tools & platforms

Next.jsReactTypeScriptTailwind CSSAWS BedrockRingCentral APIParagon Payment SolutionsParachute Healthpdf-libReact PDFZodResendVercel

If you'd like results like these,
start a conversation.

Start a conversation