Evidence
Where the judgment comes from.
Enterprise healthcare programs, described by the operating problem I was brought into and what I did about it. Prior authorization, utilization management, transformation recovery, and CMS interoperability carry the domain weight. RachelOS shows the implementation discipline.
Evidence record
Start with the case closest to your operating question.
Prior Authorization Workflow Design Experience
Administrative work and exceptions were being discussed as an automation problem before the review tiers and escalation paths were explicit.
My role: I contributed healthcare workflow, product, governance, and transformation experience inside enterprise operating environments.
Review the evidenceEnterprise Program Recovery
Local workstream status did not explain where enterprise delivery risk was accumulating.
My role: I worked across healthcare transformation strategy, delivery governance, dependency management, executive reporting, and cross-functional coordination.
Review the evidenceHealthcare Interoperability Modernization
Regulatory and interoperability requirements had to become working platform behavior rather than remain policy or documentation.
My role: I owned payer-facing product requirements and functional design for CMS Cures Act and FHIR interoperability work at ELLKAY.
Review the evidenceRachelOS: A Live Operating Environment
Follow-up, prioritization, and context reconstruction depended on the operator being available.
My role: I designed, built, operate, and audit the system myself.
Review the evidenceCRE Intelligence Model
Knowledge left with the analyst and could not be reused consistently across subsequent questions or decisions.
My role: I modelled the information and decision structure.
Review the evidenceHow to read this evidence
- Employment history demonstrates experience
- Roles and scope are verifiable and are presented as experience. No employer or client endorses this practice or its conclusions.
- Client outcomes are not published without permission
- Enterprise programs carry confidentiality obligations that outlast the engagement. Where a result cannot be published, the mechanism and my role are described and the number is left out rather than estimated.
- Each case supports a specific capability
- Healthcare cases establish domain and operating experience. RachelOS shows implementation discipline in an environment I built and run. They answer different questions and are not interchangeable.
Each case page carries the specific limits of its own evidence in a short expandable note at the end.
Does this apply here?
What transfers is the operating mechanism.
Healthcare transformation and the supporting environments above share one structure: work crosses systems and roles, exceptions depend on experienced staff, and leadership needs reliable evidence before changing the workflow.
What travels between them is the disciplined work of tracing a workflow, clarifying evidence and authority, designing controls, and measuring the change. Domain logic and performance results stay where they were earned. A real-estate system does not predict a healthcare result, and one enterprise program does not predict yours.
Program Recovery Conversation
Bring one program under pressure.
A structured 45-minute working conversation about one program that is behind, over budget, or about to fund automation on top of an unstable workflow.