Evidence Library / Engage in Change Artifact Family

Quiet cards for the moment before the call.

These are not technical documents. They are anxiety-reduction artifacts: official enough to forward, simple enough to read, and bounded enough to explain why Engage in Change became the front door.

One Concern Each artifact handles one anxiety, not a whole implementation manual.

Boundaries Minimum, typical, and not required are visible in the first scan.

Forwardable The card should survive being sent to IT, compliance, or leadership without context.

Proof Path Each card becomes a proof object connected to Engage in Change, Questions, and the Evidence Library.

Point of Care / Engage in Change Artifact

The Gap

The first proof names the signal the field keeps inheriting without testing.

What if what someone says and what they do are not the same signal?

Said

The person sounds ready, cooperative, and able to name what they want to change.

Done

Follow-through reveals whether readiness became action after the conversation ended.

Cost

When the gap stays invisible, the record can begin defending a call that was never going to hold.

Thesis

The gap between what someone says and what they do is the expensive, invisible thing. Point of Care makes that gap visible while it can still change what an operator does next.

Point of Care / Readiness Artifact

What We Need From You

The beginning should feel bounded. This card names the smallest practical ask before Point of Care becomes a pilot conversation.

What do you need from our organization to begin?

Minimum

One service line, one workflow owner, and enough record visibility to inspect continuity.

Typical

A supervisor, compliance or billing contact, and an EHR/data contact for read-only access planning.

Not Required

No system migration, no write-back access, no organization-wide rollout to start.

Operational Note

The first readiness conversation should clarify what can be seen safely, who can explain the workflow, and what decision the pilot is meant to support.

Point of Care / Readiness Artifact

Stakeholder Map

A calm view of who needs to be involved before, during, and after a Point of Care pilot.

Who needs to be in the room, and when?

Before Pilot

Executive or pilot sponsor
Workflow lead
IT or EHR contact

During Pilot

Pilot owner
Supervisor or care lead
Compliance or billing contact

After Pilot

Internal owner
Decision maker
Point of Care review lead

Boundary

Not everyone is involved in everything. Stakeholders enter when their domain is touched, so implementation does not become a standing committee.

Point of Care / Readiness Artifact

EHR Access Boundaries

This card separates what Point of Care needs to observe from what people fear another system might change.

Do you need full access to our EHR?

Read-Oriented

The readiness path starts with record visibility, exports, reports, or scoped review access.

No Write-Back To Start

The pilot does not require Point of Care to alter your source record.

Scoped Data

The access conversation is tied to the service line and continuity question being examined.

Least Privilege

Permissions should match the pilot purpose, not create broad access by default.

Trust Line

Your EHR remains the system of record. Point of Care examines whether the work, timing, documentation, and follow-through hold together.

Point of Care / Readiness Artifact

Time To Decision-Grade Signal

Time-to-value should mean more than seeing a dashboard. It should mean the organization can make a better decision.

How quickly would we see something meaningful?

Meaningful Means

You can identify whether continuity is holding, where it breaks, and what would prevent recurrence.

Not Meaningful Yet

A dashboard exists, but nobody can tell what changed, what matters, or what decision follows.

Minimum

A bounded workflow review with a clear question.

Typical

A short pilot readout with observations, risks, and next steps.

Maximum

A broader service review when scope, data, or leadership questions expand.

Readiness Standard

The pilot should produce decision-grade clarity, not just activity. The organization should know what it learned and what to do next.

Use this set as a forwardable readiness artifact: restrained enough to avoid big-project energy, specific enough to help the next person ask the right question.