Collectively not rare: 300 million people, years to a name.
Clinical · Full PHI · Every specialtyA rare-disease flag is a rule family in the Rules engine — a set of rules evaluated together at one decision point over the findings the record holds, raising a flag for review — and that engine already exists as an API (POST /rules/definitions with a family, POST /rules/evaluate), with no screen of its own. No code was added for this idea, because the raising is already done. What is left of it is the part that needs data the product does not hold: the combinations of findings that should trigger the question are reference data nobody has supplied, so no rare-disease rule family is loaded, nothing matches a patient into a registry or a trial, and no registry link exists.
It does not pronounce a diagnosis or suggest one — no phenotype criteria are typed here — and it does not match anyone to a registry or a trial: no such link exists in this product.
Every app page carries this section. A listing with only benefits is an advertisement.RareFind reads the patient record, through the Rules engine and writes nothing. Its data class is Full PHI. Every app works on the same patient record — nothing is copied into a silo.
It does not pronounce a diagnosis or suggest one — no phenotype criteria are typed here — and it does not match anyone to a registry or a trial: no such link exists in this product.
Every record stays; only the workflow leaves.
RareFind is in design: the surface exists and the platform underneath is ready. Join the waitlist and it moves up the build order.
Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.