Software that understands whether the organization is operating as it should.

Built from inside healthcare operations

Paloma was not conceived by people looking at healthcare from the outside. It comes from more than 16 years of operating healthcare agencies across home health, home infusion, VA care, private duty, private pay, Medicaid and staffing. Its founder is a registered nurse who has performed admission assessments, infused patients in their homes, taken physician orders and chased the signatures, staffed cases and covered them when a clinician called off, run emergency preparedness for real events, and prepared agencies for state surveys and accreditation surveys and sat through them.

That history is not offered as a credential. It is the reason the architecture looks the way it does.

What running agencies reveals

Operating an agency teaches distinctions that software easily collapses. Each one, when blurred, eventually produces a denied claim, a survey finding or a risk to a patient.

• An order is not an authorization. A physician can order care a payer has not approved.
• An authorization is not payment authority. Approval of care and permission to bill can arrive as separate documents on different days.
• A credential recorded is not a credential verified. A copy shows what someone handed in; verification is a check with the source.
• A visit is not a billing unit. One encounter may be reported in fifteen-minute units and paid as part of an episode.
• A course of therapy is not today’s dose. A three-day order for a total amount is three administrations, and the nurse documents one of them.
• A completed note is not satisfied compliance. Work can be done well and still leave no record a surveyor or payer will accept.

It also teaches where the days go. The nurse documents in one place. Staffing is managed in another. Credentialing has its own files. Orders and authorizations live in inboxes and scanned pages. Billing is reconstructed later, and compliance staff assemble binders after the fact. The people in the agency become the integration: a coordinator re-keys a referral, a nurse is texted an order, a biller types an invoice from memory.

None of those people is doing anything wrong. The software has a model of a chart, or a claim, or a job posting. It has no model of the agency.

Why infusion first

Home infusion was not chosen because it was the nearest market. It was chosen because it exposes, in one business, what healthcare operations software gets wrong.

When a patient receives a specialty drug at home, a pharmacy dispenses it and a nursing agency sends the nurse. Very often that agency is independent and serves several pharmacies at once. Its customer is the pharmacy, not an insurer. It is paid under a contract, and every pharmacy has its own. Its work begins with a document it did not write, the pharmacy’s referral and order, and ends with one it must send back within hours, the nursing note, in the form that pharmacy expects.

Every decision depends on the one before it: whether there is a nurse with the right license and competency for this therapy, whether that nurse is within reach of the patient, which order governs today, when the patient must be seen, whether the note is complete, what the visit is worth under that pharmacy’s agreement, whether it was invoiced and whether it was paid.

This describes categories, not any one product, and many products do their own job well. The point is what each is organized around. To serve the agency in the middle, a platform has to get a long list of fundamentals right together: referrals, authoritative orders, clinicians matched by credential and geography, scheduling, documentation, clinical review, billing that follows a commercial relationship, evidence, permissions and audit trails.

Those are the foundations of every healthcare organization that delivers care outside a hospital. Infusion exercises them hard. How home infusion nursing actually operates →

Beyond infusion

Infusion is the first implementation of each engine and never the shape of the engine. Paloma is not building an infusion note system but a clinical documentation engine in which infusion nursing is the first mature documentation kind; not a pharmacy invoice calculator but a revenue-cycle engine in which pharmacy contracts are the first mature commercial model; not a nurse finder but a workforce engine in which an infusion patient’s location, therapy and credential requirements are the first mature demand signal.

A platform that launches every service line at once is shallow in all of them, and an agency needs the line it runs to work completely. So each line is taken to depth on engines designed from the start to carry more than one. The test applied to every design decision is whether it serves the line in hand without making the next one harder.

Two axes are kept apart throughout: what care an organization delivers, and who pays for it under what rules. Home infusion can be funded by a pharmacy under contract, a commercial plan, a government program or a family. Home health meets Medicare, Medicare Advantage, Medicaid and commercial payers. A payer is not a service line. Every service line, explained →   Who pays, and under what rules →