One platform to coordinate every patient, facility, and procedure

Backend: PHP
Frontend: Vue.js
Infrastructure: Client-hosted (on PriceMDs' own servers)
PriceMDs runs a healthcare cost-containment business with a lot of moving parts: corporate clients, medical facilities, patients, and the coordination process that ties them together. The software meant to run all of it had never reached the point where the team could rely on it. We rebuilt the platform from the ground up so they could run the business on it.

The Client

PriceMDs is a US healthcare cost-containment company, founded in 2013 and based in Florida. It helps self-insured employers lower what they spend on elective surgery, diagnostic imaging, and specialty medications. The model is a "bolt-on": it works alongside an employer's existing plan, brokers, and administrators rather than replacing any of them, giving employees access to vetted surgeons and imaging centers at bundled, up-front prices.

The mechanics behind that are coordination-heavy. PriceMDs sits between its corporate clients and a nationwide directory of medical facilities. The facilities get a steady flow of patients, and in return they treat those patients at a reduced, pre-agreed rate. A registered-nurse team manages each patient's journey from first contact through to the completed procedure. That whole operation runs on internal software, and that software is what we were brought in to build.

The Challenge

PriceMDs came to us with an existing system that had never grown into what the business needed. They had a single in-house developer carrying it, and the scope had outgrown what one person could keep up with, so the software stayed incomplete and the team had largely stopped relying on it. They wanted to stop working around their tools and start working with them, and brought in a partner who could rebuild the platform properly and keep it moving.

What we were rebuilding was substantial. PriceMDs coordinates medical cases end to end, from the first contact with a patient through to a completed procedure, and every step has to be tracked, attributed, and recoverable later. Companies, their branches, individual patients, hospitals, physicians, procedure codes, pricing, case history: all of it lived in one platform, and all of it had to talk to the rest.

Our Approach

We rebuilt the system rather than patching the old one, and PriceMDs agreed to a ground-up rewrite without much resistance.

We worked module by module rather than scoping the whole system upfront. The old system served as a reference for what existed. It did not explain why any of it existed, and that part lived with the people who used it.

So PriceMDs put those people in front of us. A nurse, a coordinator, a manager. Each of them owned an area of the business, and each became the product owner for their part of the platform. Our developer sat with them one at a time.
Every module was built for one person and shaped around how that person actually worked. The nurse walked through the checklist she ran when a case opened. The coordinator explained what he needed to see before sending a request to a facility.

Once a module was understood, we designed the screens in Figma, agreed on them with the person who would use them, and handed it to development. While that module was being built, we scoped the next one with the next person. Calls ran twice a week, more often at the start. We delivered to their own server at the end of each cycle, demoed, and moved on.

The platform came together as a set of connected modules.

Client management

Every corporate client lived here, in one of three structures: a master company with branches, a direct client with no branches, or groups under a master. The system held company details, location, legal data, financial information, and the decision-makers, because an employee could not simply request a procedure on their own. That went through a defined approver on the company side.

Facilities and physicians

Each hospital was entered with the procedures it could perform, split into surgical and imaging (MRI, scans, and similar), used both to screen patients before a procedure and to track recovery after. Under each facility, PriceMDs kept the full roster of physicians with their specialties and contacts.

Procedure codes and pricing

Every procedure carried a CPT code, the national standard with one code per procedure across the country, alongside the average cost at a given facility. Differences between facilities existed but stayed small.

Communication and notifications

Under every case, staff could leave notes and tag other users with access to the platform, keeping a history of who did what and who approved what. An internal notifications module kept the right people informed as cases moved.

Case management

This was the core. A patient, an employee of a corporate client, had a case opened under a specific procedure, and that case was driven from start to finish through a checklist the nursing staff worked through: confirming signed HIPAA agreements, sending requests to facilities, recording which facility accepted the patient, and so on. Each completed step was checked off, building a clear record of where the case stood.

Reference data and reporting

Behind the workflow sat the reference data the system ran on: vendors, billing information, reasons a case might be declined, reasons a client relationship might end. A reporting module generated the documents the team needed, including the vouchers, or referrals, sent to patients.

Facility map

Facilities were plotted on a map with search built in. The team could look by specialty, or by radius from an address such as a patient's, and find the right hospital for a given case without digging through lists.

The Solution

By the end, PriceMDs could run their operation in one place: register companies, add patients, open and drive cases, enter every procedure and price, and record the full lifecycle of each case from first contact to completed treatment.

Outcome

The collaboration ran from January 2023 to summer 2024, about fourteen months. In that time the system went from a half-built tool people avoided to one PriceMDs used to manage their full workflow, from clients and facilities through to physicians, procedure codes and pricing, patients, and cases, with notifications, staff communication, reporting and vouchers, and a searchable facility map around them.

What changed for the team was clarity more than speed. Cases did not move faster after the rebuild, but they became easier to run. The system tracked who added each piece of information and when, and who set which flags, and the documents that staff used to assemble by hand were now generated automatically. Sensitive data was stored separately from ordinary records, fitting the HIPAA-compliant setup PriceMDs already ran.

The engagement ended for reasons outside the work itself. The client's investors pushed for a US-based vendor, and they left the door open to coming back.
Feel like your project would win from our work? Let's talk!
sales@smartificial-ai.com
Made on
Tilda