Medicine

Your AI drafts, summarizes and triages. The record shows who reviewed it.

When a regulator, a payer or your own quality committee asks how the health system supervised its clinical AI, a written policy is a promise. A sealed record of who reviewed what is evidence.

One model change, one receipt
Boundary

Model change

Check

Your change-control review

Guard

The clinical AI review owner

Receipt

Sealed

The duty

The supervision duty is the health system's.

Clinical AI runs under rules your compliance office already works from.

RuleWhat it asks
HIPAAKeep patient health information private and confidential.
FDA PCCP / SaMDPlan and document changes to AI medical-device software in advance.
HHS §1557No discrimination by AI tools used in patient-care decisions.
ONC HTI-1Certified health IT shows 31 source attributes for each predictive decision-support intervention.

Build your frame

Your health system's rules, not ours.

Planisphere doesn't ship a health system's policy. You name the boundary, the check you already trust, the person who guards it and what happens at the crossing.

BoundaryWhere clinical AI changes or data moves

Patient context sent to an outside model, a model change going live.

CheckThe review you already run

Your privacy screen or change-control review, recorded with its answer.

GuardA named person

The privacy office, the clinical AI review owner, the quality committee.

ResponseWatch, Flag, Hold or Wall

Watch records every crossing today; Hold and Wall run through the gate API.

For your developers

Four calls around the model change.

Gate the change, record the reviewer's decision, export the trail, verify it.

planisphere-sdk · TypeScript
const ps = new Planisphere("ps_live_YOUR_KEY");
// 1. Gate the model change
const d = await ps.gate({ pack: "medicine",
  action_type: "medicine:model_change_evidence",
  proposed_action: "Deploy the updated documentation-summary model.",
  context: { care_setting: "ambulatory", phi_boundary: "internal",
    clinical_review_owner: "clinical-ai-review", device_or_workflow_type: "documentation-summary" },
  regime_refs: ["FDA SaMD", "PCCP"] });
// → decision: "needs_review"
// 2. The reviewer's decision, sealed as its own receipt
await ps.recordReview({ pack: "medicine", action_key: d.action_key,
  reviewer: "clinical-ai-review-owner", decision: "approved" });
// 3. Export the trail · 4. Verify, no trust required

Verifying a receipt needs no account. A record is not a legal finding or a certification.

Questions.

Does Planisphere give medical advice or certify HIPAA compliance?+

No. It keeps records of what your clinical AI tools and reviewers did. A record can support your compliance office's evidence; it isn't medical advice, HIPAA certification, FDA clearance or clinical safety validation.

Do you see PHI?+

Your workspace decides how much readable detail a record keeps. Ask us about keeping details on your side before you connect a clinical system.

Who can check a receipt?+

Anyone you give it to: a regulator, a payer or your quality committee. Verifying needs no account and no trust in the health system.