jubalMED is not a search box with a chat window. The model is the researcher: it reformulates your question, reads the authorities in full, and composes an answer only from text it retrieved — with the provenance to prove it.
You ask in the words you'd use with a colleague — “can we tie the patient down,” “the SNF says we owe them personal care.” The corpus speaks in terms of art: “restraint or seclusion,” “coordination of services,” “professional management.” jubalMED translates your question into several regulatory-vocabulary probes and runs them across the corpus, federal and state together.
Search hits are only candidates. Before anything is cited, the full section text is read — including the neighboring subsections where the controlling language often lives — and provenance is pulled for every authority that will appear in the answer: official source, version, retrieval time, content hash.
A regulation rarely stands alone. The answer shows the statute it hangs from, the regulation that requires, and the survey guidance that tells inspectors what to check — each quoted verbatim, each dated, guidance always badged as non-binding. One card, three layers, nothing from memory.
This is a real answer to a real question — what must be in a hospice plan of care. The statute authorizes, the regulation requires, and the survey guidance shows what inspectors are told to check, down to the page range in the CMS manual.
The statutory authority for everything below.
Condition of participation: interdisciplinary group, care planning, and coordination of services.
What surveyors are told to check for §418.56 compliance.
Some hospice questions are controlled by sources beyond the corpus — a MAC coverage determination, a Medicaid provider manual. When that happens, jubalMED says exactly what is on file, names where the controlling authority likely lives, and stops. It will not present an adjacent section as if it controlled, and it will not invent a citation.
Every miss is logged. That record decides what gets added to the corpus next, so coverage grows along the questions operators actually ask.
Point-in-time means the corpus knows what a section said on a given date — so an answer about last quarter cites last quarter’s text.
Medicare/Medicaid conditions of participation — hospice (418), hospitals (482), long-term care (483)
HIPAA privacy and security (Parts 160, 164)
FDA regulations
Social Security Act statutes (§§ 1395, 1396 families)
State Operations Manual incl. Appendix M hospice survey procedures — served as guidance, never as law
CCR incl. CDPHE facility standards (6 CCR 1011-1) and Medicaid rules (10 CCR 2505-10)
jubalMED is tested against a fixed set of operator questions with known answers. Three gates apply: did it find the controlling authority, is every citation faithful to the retrieved text, and does it say “not on file” instead of guessing when the answer lives outside the corpus.
Answers your team flags in the product join that set — so the questions that matter to your operation become part of the bar every release has to clear.
Invite-only, with founding rates for early members. When someone tells you what the rules say, jubalMED shows you what the rules actually require.