Insights
A point of view about healthcare operations software.
These are the positions the platform is built from. Each is stated briefly here and argued at length on the page it links to.
Essays
Start here.
What survey readiness actually means
A survey does not begin when the surveyor walks through the door. What state and accreditation surveys actually test, why binders fail, and what it takes for readiness to be how an agency operates.
Read the essay →Why home infusion nursing is an underserved software problem
The independent infusion nursing agency sits across four software categories, each built around a different center of gravity.
Read the essay →Why clinical, administrative and compliance work belong in one system
An agency’s clinical record, its administration and its survey readiness are the same facts seen by different people.
Read the essay →Positions
Eight things we hold to.
Compliance should be continuous, not episodic
A binder assembled before a survey describes the agency on one day. An agency is safer, and calmer, when each requirement is an obligation with evidence that is checked as the work happens, and a gap is an owned item rather than a discovery.
Continuous compliance →Regulation should be dated data, not annual forms
Payment rates, assessment data sets, code sets and survey guidance change on published cycles. Software that writes a year into its screens has to be rewritten every year, and cannot say which rule applied to an older record. Rules belong in data, each with its effective date and source.
Medicare home health →A staff record and a login are different things
A person can be on the roster, employed and scheduled without ever signing in, and a login can outlive a job. Treating the three as one creates accounts nobody uses and hides staff who have none. Identity, employment and access should be separate records.
The platform →A patient need should be able to start a workforce search
The clinical record already knows the therapy, the place and the timing. Asking a coordinator to describe them again in a recruiting tool wastes the hour in which a referral is won or lost.
Clinical demand meets workforce supply →Revenue cycle starts before the claim
Denials and unbilled work are usually caused upstream: an unsigned order, an unreviewed note, an unrecorded rate. A billing system that reads the operational record can show the cause before the invoice exists.
Revenue cycle →Evidence should follow the workflow that created it
A signature, a review and a correction belong to the record they were made on. Evidence gathered afterwards into a separate folder is a copy, and copies drift. A correction should preserve the original and say who changed what, and when.
The True North →A label does not establish a credential
A license number typed into a form, a document someone uploaded and an answer from the licensing authority are three different levels of assurance. Software should say which one it has.
Interoperability →Imports are not integrations
Mapping a spreadsheet into a system is useful and honest work. Calling it a connector is neither. Buyers should be told which kind of connection they are getting.
Interoperability →Paloma Cares
See it in Paloma Cares
These positions are not only opinions. They are how Paloma Cares is built, and you can see them at work in the demo agency.
The products
The software doing it.
Use either independently. Use them together when you want patient demand and workforce supply to work from the same context.