A useful first review does not commit a team to a trial
The current starting point is a checked public-data brief and a discussion of whether the question is relevant. The five service activities are: interpret public signals and validate relevance; review information you agree to share; prototype one agreed workflow; test and decide; and operate and improve under a separate commitment.
Local-data review, workflow testing and ongoing operation are still being developed. They require their own scope and readiness. The method below is a proposed way to test one operational change, not a report of a delivered customer trial.
A public HRRP signal can earn a useful conversation. It cannot specify the workflow to change, establish that a hospital needs another platform or predict the result of an intervention. The practical conclusion of this series is a bounded way to test whether a clearer execution record helps the people responsible for one transition job.
The first output should be a scope the team can use to make a decision. A quality owner can explain the public evidence. A care-transition leader can describe the handoff. A technology owner can identify existing capabilities. Together they decide whether there is an unresolved problem worth examining. Private data access is not the starting requirement.
Start with one obligation and a real owner
Use the synthetic referral example from Articles 2, 3, 5 and 9 as a discussion aid. A referral has been transmitted, but acceptance remains unconfirmed. The candidate job is to establish an accepted handoff or an explicitly owned exception. It is not to automate every discharge activity or guarantee a completed clinical outcome.
First ask whether the existing EHR, referral platform or local process already provides the necessary state. If it does, the better decision may be to improve configuration or operating practice. An adjacent Lime Health evaluation is appropriate only where the team can name a gap and explain how a shared execution record would help.
Write the scope before choosing the integration
| Agreement | What the team records |
|---|---|
| Job boundary | Opening event, completion criterion and excluded activities |
| Ownership | Operational sponsor, coordinator, exception reviewer and closure authority |
| Evidence | Required receipts, source systems, missing-data treatment and approved fields |
| Operating limits | Local deadlines, escalation choices and actions that require human judgment |
| Evaluation scope | One workflow, agreed population and observation period |
| Reversal | Conditions for stopping, restoring the prior process and retaining required evidence |
Scheduling completion is not proof of attendance. Attendance is not proof of clinical benefit. Define separate events and measures where those questions matter; do not allow a convenient system status to silently broaden the claim.
Establish a baseline that the team can reproduce
Begin with approved interviews, process walkthroughs and aggregate evidence where sufficient. Record how the sample was selected, what was excluded and how many obligations have missing or ambiguous evidence. Any later access to hospital or patient-level information requires its own purpose, field and environment approval.
| Proposed measure | Definition to agree locally | Interpretation boundary |
|---|---|---|
| Acceptance visibility | Eligible obligations with documented acceptance status divided by eligible obligations | Better visibility does not prove more completed care |
| Time to resolution | Elapsed time from the agreed opening event to accepted closure or disposition | Open cases and late evidence must remain visible |
| Repeated contacts | Additional status-seeking contacts per eligible obligation | Contact type and recording coverage must be consistent |
| Coordinator reconstruction time | Time spent assembling the status of an obligation | Use an agreed sampling method; do not invent time savings |
| Unresolved exceptions | Number and age of exceptions still open at the checkpoint | An exception may be appropriately open |
| Added review burden | Time or steps introduced by the new process | An essential balancing measure |
Readmission outcomes may be important longer-term context, but a small operating trial cannot establish that Lime Health caused a change. Public payment percentages also do not establish recoverable revenue. Keep the initial value claim close to the process actually observed.
Decide what would justify continuation
Set decision criteria before inspecting the result. The hospital should choose acceptable evidence completeness, useful changes in the selected measures and tolerable added burden; this article supplies no universal success threshold.
Continue within scope when the team can reproduce the evidence, sees useful operational improvement and accepts the burden. Revise when the problem is meaningful but the workflow or measurements are incomplete. Stop when ownership remains unresolved, controls cannot be met, existing capabilities already solve the problem or the trial adds work without sufficient value.
Expansion is a separate decision. A successful referral-acceptance evaluation does not authorize new patient fields, another service line, autonomous action or a public customer claim. Preserve the result and its limitations. Record the decision owner so the next proposal starts from what was learned.
Leave with something useful even if no implementation follows
A bounded review should produce an obligation map, an evidence-gap list, a measurement sheet and a documented next decision. Those artifacts can help the hospital improve its current process regardless of whether it proceeds with Lime Health.
Public intelligence remains available as a separate point of value. Readers seeking only facility context or source methodology need not enter a paid project. For readers who do want an operating discussion, the next step is to bring one workflow and its accountable owner.
For transparency about Lime Health account research, see why scores should order research but never authorize outreach. That methodology governs Lime Health prospect research; it does not authorize hospital actions.
A scenario can justify discovery without becoming the outcome
Public payment and materiality context can help select a facility and a bounded care-transition question. The workflow trial must replace proxy assumptions with authorized evidence where appropriate, establish a reproducible baseline, and measure execution and balancing outcomes. Estimated exposure is neither the success metric nor a promise of recoverable revenue.
Sources and boundary
This is a proposed evaluation method, not a report of customer results or a live deployment. See CMS HRRP program information for the payment-program boundary and Lime Health disclosures for reference implementation and publication limits. All referral examples in this series are synthetic.