healthcare_ai_consulting.exe
    Healthcare AI Consulting

    Someone on your clinical floor is already using AI. Healthcare AI consulting for the teams who have to make that safe.

    Nobody approved it, but the drafts are already coming out of a chatbot, the ambient scribe pilot is in month four, and nobody can say with confidence what went in, what came out, or whether PHI touched a server you have no agreement with. That is where most of our healthcare work starts. We find out what is actually happening, name what is worth fixing, and build or train toward it, with the human checkpoints, the PHI boundaries, and the audit trail built in so a wrong output never becomes a clinical event.

    For hospitals, payers, digital health startups, and clinical AI vendors. HIPAA-aware, audit-ready, and honest about what AI should and should not be doing inside a regulated workflow. Engagements run on the Build ladder, so Discovery is $875 for one clinic or team and a $4,500 Audit for an org-wide program, and both credit toward what follows.

    why_healthcare_ai_stalls.txt
    The pattern we keep seeing

    Healthcare AI projects don't fail in production. They fail before they ever get there.

    A clinical team gets handed a tool. The vendor demo was crisp, the leadership memo was confident, and the pilot was approved with a 90-day window. Then three things happen in this order:

    • Compliance review surfaces questions nobody scoped for. PHI handling, model logging, vendor BAAs, FDA classification, state-level rules. The legal lift triples.
    • The clinical workflow turns out to be three workflows in a trench coat. The model fits one of them and breaks the other two.
    • The people who were supposed to use the tool never got training that respected how they actually work. Adoption flatlines.

    The fix is not a better model. It is a better system around the model. That is what we do.

    who_we_work_with.txt
    Who this is for

    For teams where a wrong output is a clinical event.

    Hospitals & health systemsAdopting clinical or operational AI inside an existing EHR and compliance stack.
    Digital health startupsBuilding AI-native products that need to clear procurement, security review, and clinical buy-in.
    Payers & health plansBringing AI into utilization review, claims, and member-facing workflows without violating the rules that govern them.
    Clinical AI vendorsShipping models into hospitals and pharmacies where one wrong output is a safety event, not a UX bug.
    Healthcare-adjacent regulated teamsPharmacy benefits, medical device, lab informatics, and public health groups working under federal oversight.
    Investors & boardsDiligencing healthcare AI bets where the technical risk and the regulatory risk are the same risk.
    engagements.exe
    Engagements

    Four ways we work with healthcare teams.

    Engagement 01Discovery or AuditThe diagnosis. We sit with clinical, IT, compliance, and ops, map the real workflow, the real data, and the real risk, and say plainly what is broken and whether the fix is a build, a workflow change, training, or oversight work. For a single clinic or team that is the Discovery session. For an org-wide program it is the Audit. Either way you leave with a written assessment that names every blocker before procurement does.
    Engagement 02Blueprint for Regulated AIWhich tools, which model, where a person has to sign off, what gets logged, where PHI may and may not go, and how it connects to your EHR or core systems. Designed to survive a Joint Commission visit, not just a sprint review. Delivered as a Blueprint you own.
    Engagement 03Build and Clinician TrainingHands-on rollout with the people who will use the system. Documentation that does not assume a CS degree. Prompt libraries, escalation paths, and a deprecation plan for the day the model gets it wrong.
    Engagement 04Vendor and Product AdvisoryFor clinical AI builders. Positioning, hospital procurement strategy, compliance posture, and how to talk to a CMIO without losing the room. Often paired with a redesign of how the product handles verification and audit. Billed hourly, no retainer.
    proof_of_work.exe
    Proof of work · Orinyx

    We do not just consult on clinical AI safety. We built one.

    Orinyx is an independent pre-deployment verification platform for clinical AI. Phase 1 runs in a sandbox on synthetic data, with no PHI and no EHR connection, and every AI assertion is checked against authoritative sources instead of another model's judgment. Each verdict is deterministic and arrives with a citation showing what was checked, and findings are documented for governance review.

    Building it forced us to live the same questions our healthcare clients live. What does HIPAA actually require versus what people assume it requires. Where the FDA SaMD line really is. How to keep a model fast enough to use at the point of care without keeping PHI at rest. The patterns from Orinyx show up in every healthcare engagement we run.

    Learn more about Orinyx ↗
    what_we_do_not_do.txt
    Boundaries

    Things we will tell you not to do.

    • Put a general-purpose LLM in front of a clinician with no verification layer.
    • Buy an AI scribe before the documentation workflow it is replacing is actually understood.
    • Sign a BAA you have not had reviewed by counsel who knows healthcare specifically.
    • Move PHI into a vendor environment to save two weeks of integration work.
    • Pilot a model in a high-acuity unit because that is where the data is most interesting.
    • Ship anything that cannot be audited line by line after the fact.
    faq.txt
    Questions we get every week

    Healthcare AI consulting, plainly answered.

    We already have a big consulting firm. Why would we need you?

    Big firms staff with generalists and bill for change management. charmthirteen is one practitioner with a clinical, EHR, and healthcare data product background, and engagements are only taken where a working system can be handed back, not a deck.

    We are a hospital, not a startup. Is this for us?

    Yes. Hospitals need help adopting AI safely, and most engagements have one foot in clinical operations and one in the technology supporting them.

    Our compliance team asks about a BAA before anything else. Can you sign one?

    Yes. We default to zero-PHI engagements where possible. When PHI is required, we sign a BAA and scope the data access narrowly. In our experience zero-PHI is almost always achievable.

    We do not want another strategy deck. Do you build it?

    Yes. The Build and Clinician Training engagement includes hands-on build of the workflow, the prompts, the integrations, and the audit log. Delivery is done in house.

    What does it cost, and is there anything free to start?

    Discovery is $875 for a single clinic or team and a $4,500 Audit for an org-wide program, and both credit toward what follows. A Blueprint is $2,000 in the Small Business lane and quoted from the Audit org-wide. Builds start at $3,250. Support is $175 per hour. The full ladder is on the Build page, and the Vibe Check is free and the right place to start.

    related.txt
    Start here

    Bring us in before the pilot, not after.

    Free 20-minute Vibe Check. Bring the problem, not the diagnosis.

    AI Systems Assessments →