Skill UI

PyHealth delivers a full-stack Python toolkit for building, evaluating, and deploying clinical machine learning models, covering EHR datasets, medical coding systems, physiological signals, and healthcare-tailored architectures such as RETAIN, SafeDrug, and Transformer-based pipelines.

A comprehensive guide detailing architectural patterns for developing robust Electronic Medical Record (EMR) and Electronic Health Record (EHR) systems. Covers critical areas like patient safety protocols, structured clinical workflows, drug interaction checking, audit trail implementation, and WCAG accessibility standards. Essential for building highly reliable and compliant healthcare IT solutions.

An automated verification system designed for critical healthcare application deployments (EMR/EHR). This harness enforces stringent patient safety standards by running multiple mandatory test gates, including Clinical Decision Support System (CDSS) accuracy, Protected Health Information (PHI) leakage prevention, and data integrity checks. A single failure in critical gates automatically blocks deployment, ensuring regulatory compliance and optimal patient safety in the CI/CD pipeline.

Build clinical and healthcare deep learning pipelines with PyHealth: load EHR, signal, and imaging datasets, define prediction tasks, instantiate models, train, and evaluate using a modular five-stage workflow.

A comprehensive troubleshooting guide for Abridge clinical documentation integration. Covers common errors in authentication, EHR connectivity, audio streaming, note generation, and FHIR validation. Essential for developers and technical users debugging AI-powered clinical workflows.

This workflow implements Abridge's end-to-end clinical documentation pipeline. It captures ambient audio from patient encounters, performs real-time transcription, utilizes generative AI to structure the medical notes (e.g., SOAP, H&P), generates required medical codes (ICD-10, CPT), and finally inserts the structured data directly into the EHR system. Designed for primary clinical encounters, minimizing manual charting time.

This minimal working example demonstrates Abridge's ambient AI clinical documentation capabilities. It simulates a complete patient encounter session, allowing users to submit transcripts and receive a highly structured clinical note. Ideal for testing EHR connectivity, verifying AI workflow, or learning how structured medical data (SOAP notes, ICD/CPT codes) is automatically generated from free-text conversation.

This guide details the process of setting up authentication and integration credentials for the Abridge clinical AI platform. It covers prerequisites for connecting to major EHR systems (Epic, Athena) using FHIR R4 APIs and implements OAuth 2.0 (SMART on FHIR) flows, ensuring secure, HIPAA-compliant data handling for ambient documentation.

This workflow establishes a comprehensive local environment for developing and testing clinical AI integrations. It simulates an Electronic Health Record (EHR) using a local HAPI FHIR server and utilizes synthetic patient data. Developers can iterate on complex encounter workflows and API connections safely, without ever using real Protected Health Information (PHI).

A comprehensive readiness checklist for deploying clinical AI systems, such as Abridge, within regulated healthcare environments. It covers critical aspects including HIPAA compliance, Business Associate Agreements (BAA), EHR integration validation (FHIR R4), robust infrastructure security (TLS 1.3, secrets management), and provides structured scripts for pre-launch validation and post-launch rollback planning.

Provides a comprehensive architectural blueprint for integrating ambient AI solutions (Abridge) into multi-site health systems. It guides the full process from ambient audio capture to structured note generation, covering data flow, component design, FHIR R4 standards, HIPAA compliance, and integration patterns with major EHRs like Epic and Athena.

A comprehensive guide detailing procedures for upgrading Abridge API versions and migrating between disparate Electronic Health Record (EHR) systems. It covers zero-downtime API versioning strategies (e.g., canary rollout) and outlines high-risk, multi-step procedures for ensuring seamless clinical documentation data continuity during EHR cutovers.