Public reference · Adoption barrier map
Illustrative public reference—not client work or a results claim.
From evidence to responsible adoption: where a promising innovation can stop.
A milestone attracts attention. Adoption depends on whether evidence, authority, workflow, infrastructure, economics, trust, and operating capacity can support a specific use.
Method
Name the blocking barrier—not the most visible symptom.
Use one working sentence: [Actor] cannot yet make [decision] because [evidence or operating requirement] is missing, owned by [role], and must be resolved by [date or trigger].
| Barrier domain | Failure pattern | Evidence needed | Accountable owner | Decision |
|---|---|---|---|---|
| Evidence and claims | The outcome, population, comparator, uncertainty, harms, or applicability is unclear. | Fit-for-purpose evidence package and claims table tied to source, version, and use. | Clinical or evidence lead. | What can be said, tested, or relied upon now? |
| Regulatory and policy fit | The product, service, intended use, clinical responsibility, or governing pathway is ambiguous. | Current authorization, guidance, policy, model, contract, and escalation record. | Regulatory, legal, compliance, or policy lead. | Is the proposed use permitted and governable? |
| Clinical workflow and ownership | No one owns identification, review, action, follow-up, exception handling, or patient communication. | Workflow map; role definitions; workload; escalation; training; clinical oversight. | Clinical operations owner. | Can the work be performed safely and consistently? |
| Data and infrastructure | Identity, interoperability, provenance, privacy, security, reliability, or support cannot meet the use case. | Architecture and data-flow record; technical validation; access controls; incident and continuity plans. | Technology, data, privacy, and security owners. | Can the system exchange and protect usable information? |
| Payment and economics | The buyer, budget, payment rule, unit economics, or distribution of cost and benefit is unresolved. | Coverage/payment source; contracting path; total cost; utilization; staffing; budget-impact scenarios. | Finance, payer, contracting, or service-line owner. | Can delivery be funded without distorting the care model? |
| Usability, accessibility, equity, and trust | People cannot use, access, understand, afford, or trust the intervention—or burdens fall unevenly. | User research; accessibility testing; language and digital-access support; subgroup performance; burden and grievance data. | Product, experience, accessibility, equity, and community owners. | Who can participate, who cannot, and what must change? |
| Implementation and learning | A launch occurs without readiness criteria, monitoring, feedback, or stop rules. | Phased plan; baseline; process and outcome measures; safety signals; failure modes; continue/adapt/pause/stop criteria. | Executive sponsor and implementation lead. | Should the institution continue, adapt, pause, stop, or scale? |
Worked public-source example
One digital-health pathway, multiple separate decisions.
CMS’s Medicare App Library requirements illustrate why a single “ready” label is inadequate. A patient-facing app may need a qualifying use case, CMS-approved identity assurance, FHIR-based CMS Aligned Network connectivity, applicable privacy and security compliance, third-party review, CMS review access, and launch assets. Any distinct ACCESS relationship or payment statement needs its own evidence. None of those requirements alone establishes clinical effectiveness or FDA status.
Pathway fit
Does the app meet at least one published use case and the current technical, identity, review, and listing requirements?
Clinical and institutional fit
Does evidence support the intended population, workflow, decision, claims, burden, and safeguards?
Separate payment decision
Is there current source evidence for the specific ACCESS designation, participation, coverage, or payment being claimed?
Barrier record
- Decision
- The specific choice that cannot yet be made.
- Blocking requirement
- The missing evidence, authority, capability, or agreement.
- Owner
- One role accountable for resolution.
- Acceptable proof
- The dated source, test, result, approval, or operating evidence required.
- Next review
- A date or external trigger.
Close the loop
- Confirm the barrier with the decision owner.
- Separate facts, assumptions, and unknowns.
- Assign the smallest work package that can resolve it.
- Test safety, access, burden, workflow, economics, and failure modes.
- Record continue, adapt, pause, or stop—with rationale.