Clinical conversations, fully reviewed.

Multi-clinician case conferences, M&M reviews, and patient-safety meetings need a record that survives scrutiny. Felarity provides it under a BAA.

What clinical teams use Felarity for

Healthcare organizations operate on a continuous stream of high-stakes conversations. Most leave no usable record. The ones that do are usually scribbled notes that nobody trusts a year later when the case is being re-litigated. Felarity sits in those rooms and produces a record that holds up.

• Case conferences. Who said what across the attending, the resident, the fellow, and the consult — diarized down to the speaker, with timestamps. When the cardiology fellow proposed the alternate workup and the attending overrode it, that is in the record exactly as it happened.
• M&M and morbidity & mortality review. Post-session forensic re-analysis runs the clinical council against the full transcript: contradictions between the prospective rationale and the retrospective explanation surface as evidence, not opinion. The Quality Improvement Lead persona flags process gaps; the Clinical Risk Officer flags safety posture.
• Patient-safety committees. Each session produces a hash-chained record suitable for a regulator-facing file. The 8-node SHA-256 Merkle attestation chain and Ed25519 signature mean a state board, a Joint Commission surveyor, or your own counsel can verify the record was not altered post-hoc.
• QA and utilization review. Surface clinically inconsistent rationales across encounters — the same physician justifying admission on Monday with criteria that contradict their denial on Thursday, for example. Felarity does not adjudicate. It shows the contradiction with the audio receipts attached.

The Healthcare council

When you run a case conference or an M&M through Felarity, four specialist analysts review the transcript independently. Each writes in their own voice; a synthesis layer reconciles them into a final intelligence report. You see all four perspectives — disagreements included.

• Attending Physician. Clinical reasoning lens. Reads the discussion for differential coherence, evidence weighting, and the gap between what was said and what the literature supports for that presentation.
• Clinical Risk Officer. Patient-safety posture. Flags moments where risk was acknowledged but not mitigated, where escalation paths were unclear, or where consent and capacity language was thin.
• Quality Improvement Lead. Process angle. Looks at handoffs, documentation references, and whether the team is repeating a pattern that has surfaced in prior sessions in the workspace memory.
• HIPAA Privacy Officer. Compliance angle. Notes any PHI handling concerns raised in the conversation, references to records access, and disclosure language that should be tightened.

HIPAA posture

Healthcare is a regulated environment and our posture reflects that. We do not ask clinical leaders to take our word for any of this — every line below maps to a control documented in /trust/compliance/.

• Business Associate Agreement. A BAA is available on the Professional and Enterprise tiers. Request the current version at /trust/baa/. The BAA is signed before any PHI-flagged workspace is provisioned.
• PHI workspace flag. Workspaces can be flagged as PHI-bearing at creation. The flag enables strict DLP on uploads and transcripts, encrypts session storage at rest with a workspace-scoped key, and disables all third-party LLM routing — the council runs only on infrastructure covered by the BAA.
• Configurable retention. Retention is set per workspace, from indefinite (default for legal-hold workspaces) down to process-and-delete (audio purged on session close, transcript purged on report acceptance). Retention policy is recorded in the attestation chain so the choice itself is auditable.
• Patient rights. Right of access, right of correction, and breach notification procedures are documented in /trust/compliance/. Breach notification timelines follow the HIPAA Breach Notification Rule and any stricter state requirements your workspace specifies.
• SOC 2 Type II. In observation, expected delivery Q1 2027. A penetration test is scheduled. The full trust posture lives at /trust/.

What Felarity is not

We want this on the page in plain language because clinical leaders ask it on every call. Felarity is not an EHR. We do not write to your chart. We do not replace your documentation workflow. Felarity is not a clinical decision support system in the regulatory sense — we do not diagnose, do not recommend treatments, and do not produce outputs intended to direct patient care. Felarity is not a substitute for clinician judgment. Everything the council produces is decision support for the people in the room and the people who review the room afterward. The clinicians remain the clinicians.

Workflow example

A typical deployment for a hospital quality department looks like this:

1. Sign the BAA and provision a PHI-flagged workspace for the patient-safety committee. Retention is set to ninety days for audio, indefinite for signed reports.
2. Record case conferences and M&M sessions through the meeting capture. Diarization separates speakers in real time. Live contradiction detection runs against the clinical council during the session.
3. On stop, the eleven-stage post-session pipeline runs: concatenation, full-session diarization, acoustic markers, confrontation classification, speaker attribution, NLI re-scoring, topology analysis, deep council re-analysis, and the 8-node Merkle attestation chain.
4. Review the report through the Clinical Risk Officer persona for safety posture, then the Quality Improvement Lead for process findings. Both write in their own voice and cite the transcript moments they are referencing.
5. Export the signed report for the patient-safety committee file. The Ed25519 signature and Merkle root are embedded; the public verify endpoint at /verify/ lets any reviewer confirm the record was not altered.

Last updated: June 7, 2026.