healthcareskills
Listed91 production-grade healthcare engineering skills for AI agents — FHIR, HL7v2, HIPAA, clinical AI, EHR integration, telehealth, revenue cycle, and more. MCP-ready. Real-world clinical constraints. No hallucinated dosing.
Bundles
Everything this plugin ships — skills, agents, commands, hooks, and MCP servers it bundles.
Skills (39)
21-cfr-part-11
When the user is building, validating, or auditing a computer system that creates, modifies, maintains, archives, retrieves, or transmits electronic records or applies electronic signatures in an FDA-regulated (GxP) context. Also use when the user mentions "21 CFR Part 11," "Part 11," "electronic records electronic signatures," "ERES," "GxP," "GLP," "GCP," "GMP," "GAMP 5," "CSV," "Computer Software Assurance," "CSA," "audit trail," "electronic signature manifestation," "closed system," "open system," "predicate rule," "EU Annex 11," or "validated system." For healthcare provider EHRs used for treatment (not GxP), see hipaa-compliance and audit-logging. For HITRUST or HIPAA generally, see hipaa-compliance.
accessibility-healthcare
When the user wants to design, build, audit, or remediate accessibility for healthcare apps and patient-facing systems. Also use when the user mentions "WCAG," "WCAG 2.2," "WCAG 3.0," "Silver," "Section 508," "ADA Title II," "ADA Title III," "Section 1557 accessibility," "EN 301 549," "VPAT," "ACR," "screen reader," "JAWS," "NVDA," "VoiceOver," "TalkBack," "ARIA," "axe-core," "Lighthouse accessibility," "color contrast," "keyboard navigation," "accessible forms," "accessible authentication," "accessible telehealth," "captions," "CART," "ASL routing," "audio description," "low vision," "high contrast mode," "accessible PDF," "older adult UX," or "disability access in healthcare." For plain language and reading level, see health-content-writing. For outreach orchestration, see patient-engagement.
billing-claims
When the user wants to design or build software that handles US healthcare claims — submission, adjudication, remittance, denials, or appeals. Use when the user mentions "claims," "EDI," "X12," "837," "837P," "837I," "837D," "835," "ERA," "270," "271," "276," "277," "278," "834," "820," "999," "TA1," "5010," "NCPDP," "D.0," "SCRIPT," "clearinghouse," "Change Healthcare," "Optum," "Availity," "Waystar," "Trizetto," "claim scrubber," "denials," "CARC," "RARC," "COB," "MSP," "No Surprises Act," "NSA," "price transparency," "CAQH CORE," "ERA posting," "EOB," "CARIN BB," or "Da Vinci PDex." For coding the claim, see medical-coding. For prior auth (278/Da Vinci PAS), see prior-authorization. For VBC contract economics, see value-based-care.
cda-ccda
When the user wants to author, parse, validate, or transform Clinical Document Architecture (CDA) or Consolidated CDA (C-CDA) documents. Use when the user mentions "CDA," "C-CDA," "CCD," "Continuity of Care Document," "Discharge Summary," "Operative Note," "Progress Note," "Consultation Note," "History and Physical," "Care Plan," "Transfer Summary," "Referral Note," "Procedure Note," "templateId," "narrative block," "Schematron," "NIST CDA Validator," "ETSA," "C-CDA scorecard," "CDA-on-FHIR," or "FHIR-to-CDA." For non-document FHIR data, see fhir-integration. For HL7 v2 documents transported via MDM, see hl7-v2.
clinical-ai-ml
When the user wants to build, evaluate, deploy, or monitor machine learning models for clinical or operational healthcare use cases. Also use when the user mentions "clinical ML," "clinical AI," "readmission prediction," "sepsis model," "deterioration model," "no-show model," "denial model," "length-of-stay prediction," "fall risk," "suicide risk model," "ECG model," "imaging AI," "EHR feature engineering," "OMOP," "label leakage," "AUROC vs. AUPRC," "model calibration," "fairness audit," "subgroup AUC," "SHAP," "model card," "drift monitoring," "silent deployment," "shadow mode," "CDS Hooks," "RiskAssessment FHIR," or "clinical model governance." For FDA SaMD pathway see fda-samd. For health chatbots / LLMs see health-chatbots. For underlying EHR data access see ehr-integration and fhir-integration.
clinical-decision-support
When the user wants to design, build, deploy, or evaluate a clinical decision support (CDS) tool. Also use when the user mentions "CDS," "CDS Hooks," "patient-view hook," "order-sign hook," "order-select hook," "encounter-start," "appointment-book," "CDS card," "alert fatigue," "interruptive alert," "5 rights of CDS," "order set," "clinical pathway," "CQL," "Clinical Quality Language," "BPA," "best practice advisory," "HHS CDS exemption," "Cures Act CDS criteria," or "FDA SaMD CDS." For SMART app OAuth, see smart-on-fhir. For order entry plumbing, see cpoe-orders. For SaMD regulatory pathway, see fda-samd.
clinical-documentation
When the user wants to design clinical documentation workflows, templates, or note ingestion. Also use when the user mentions "clinical note," "progress note," "H&P," "history and physical," "SOAP note," "APSO," "discharge summary," "consult note," "op note," "operative note," "SmartPhrase," "SmartForm," "dot phrase," "structured data capture," "clinical NLP," "cTAKES," "MedSpaCy," "Amazon Comprehend Medical," "HealthLake," "ambient scribe," "DAX," "Nuance DAX," "Suki," "Abridge," "Augmedix," "DeepScribe," or "AI scribe." For underlying FHIR resources, see fhir-integration. For order entry, see cpoe-orders. For HIPAA implications of recording encounters, see hipaa-compliance.
clinical-research
When the user wants to design, build, or operate clinical research informatics tools and workflows. Use when the user mentions "clinical trial," "clinical research," "RCT," "observational study," "registry study," "pragmatic trial," "real-world evidence," "RWE," "decentralized clinical trial," "DCT," "EDC," "REDCap," "Medidata Rave," "Veeva Vault EDC," "Castor," "OpenClinica," "CDISC," "CDASH," "SDTM," "ADaM," "Define-XML," "SEND," "eSource," "eCRF," "IRB," "single IRB," "sIRB," "Common Rule," "Belmont Report," "21 CFR Part 50," "21 CFR Part 56," "GCP," "ICH E6," "ICH E2B," "SAE," "SUSAR," "IWRS," "IRT," "randomization," "eConsent," "ePRO," "eCOA," "CTMS," "Veeva CTMS," "Florence eBinders," "ClinicalTrials.gov," or "FDAAA 801." For HIPAA Authorization vs. waiver mechanics, see hipaa-compliance. For 21 CFR Part 11 e-records / e-signatures, see 21-cfr-part-11. For trial-related FHIR integration with EHRs, see fhir-integration.
cpoe-orders
When the user wants to design, build, or integrate with computerized provider order entry (CPOE). Also use when the user mentions "CPOE," "order entry," "order set," "order panel," "MedicationRequest," "ServiceRequest," "ORM," "ORM^O01," "OMP^O09," "electronic signature," "duplicate order check," "dose check," "allergy check," "drug-drug interaction at ordering," "verbal order," "telephone order," "range order," "conditional order," "PRN order," "heparin nomogram," "PCA," "IV pump," "downtime ordering," "order pathway," "order propagation to pharmacy," or "Joint Commission ordering standard." For ambient scribe note write-back, see clinical-documentation. For CDS at the moment of ordering, see clinical-decision-support. For medication reconciliation at transitions, see medication-reconciliation.
dicom-imaging
When the user wants to design, integrate, or troubleshoot DICOM medical imaging systems. Use when the user mentions "DICOM," "PACS," "VNA," "modality," "C-STORE," "C-FIND," "C-MOVE," "C-ECHO," "DIMSE," "DICOMweb," "WADO," "QIDO," "STOW," "UPS-RS," "MWL," "Modality Worklist," "MPPS," "Structured Report," "SR," "SOP Class," "AE title," "transfer syntax," "DICOM anonymization," or specific modalities like CT/MR/CR/DX/US/NM/PT/MG. For non-imaging clinical data exchange, see fhir-integration or hl7-v2. For AI on imaging, see medical-imaging-ai.
ehr-integration
When the user wants to integrate with a specific EHR vendor's APIs, app program, or sandbox. Also use when the user mentions "Epic," "App Orchard," "Connection Hub," "Cerner," "Oracle Health," "Millennium," "CareAware," "Code Console," "Ignite APIs," "HealtheLife," "Athenahealth," "athenaOne," "MDP," "More Disruption Please," "Meditech," "Greenfield," "eClinicalWorks," "NextGen," "Allscripts," "Veradigm," "OpenEMR," "EHR sandbox," "vendor app review," "Care Everywhere," "Hyperdrive," "Chronicles," "Interconnect," "DocumentReference write-back," or "MDM message." For FHIR-resource-level work, see fhir-integration. For SMART OAuth specifics, see smart-on-fhir. For HL7 v2 messaging, see hl7-v2.
fda-samd
When the user wants to determine if their software is FDA-regulated, plan a submission pathway, design under quality systems, or maintain a regulated device post-market. Also use when the user mentions "SaMD," "Software as a Medical Device," "FDA," "510(k)," "De Novo," "PMA," "CDS exemption," "21st Century Cures," "Cures Act 3060," "Predetermined Change Control Plan," "PCCP," "Good Machine Learning Practice," "GMLP," "QSR," "QMSR," "21 CFR Part 820," "ISO 13485," "FDA cybersecurity," "premarket cybersecurity," "MDR reporting," "medical device reporting," "FDA software documentation," "IMDRF," or "ML-enabled device." For building the ML model itself see clinical-ai-ml. For chatbot regulatory framing see health-chatbots.
Show all 39 bundled skills Showing all 39 bundled skills
fhir-integration
When the user wants to design, implement, debug, or review FHIR integrations. Use when the user mentions "FHIR," "FHIR R4," "FHIR R5," "FHIR resource," "FHIR bundle," "FHIR search," "CapabilityStatement," "US Core," "USCDI," "CARIN BB," "Da Vinci," "mCODE," "IPS," "bulk data," "$export," "OperationOutcome," or names specific resources like Patient/Encounter/Observation/Condition/MedicationRequest. For SMART OAuth flows, see smart-on-fhir. For HL7 v2 pipe-delimited messages, see hl7-v2. For terminology services and code systems, see terminology-services. For CDA documents, see cda-ccda.
gdpr-health-data
When the user is processing health, genetic, or biometric data of people in the EU/EEA, UK, or other GDPR-aligned jurisdictions, or designing controls for special-category health data. Also use when the user mentions "GDPR," "Article 9," "special category data," "Article 6," "lawful basis," "explicit consent," "controller," "processor," "joint controller," "DPA," "data processing agreement," "DPIA," "DPO," "Article 30," "records of processing," "72 hour breach," "SCCs," "Standard Contractual Clauses," "Schrems II," "Transfer Impact Assessment," "TIA," "Recital 26," "UK GDPR," "EHDS," or "European Health Data Space." For US HIPAA, see hipaa-compliance. For operational PHI controls applicable globally, see phi-handling. For audit-log design, see audit-logging.
genomics-precision-medicine
When the user wants to design, build, or integrate genomics and precision-medicine informatics. Use when the user mentions "genomics," "precision medicine," "VCF," "gVCF," "BAM," "CRAM," "FASTQ," "variant calling," "variant annotation," "HGVS," "ACMG," "AMP/CAP/ASCO," "ClinGen," "ClinVar," "PharmGKB," "CPIC," "pharmacogenomics," "PGx," "GA4GH," "VRS," "Phenopackets," "FHIR Genomics," "mCODE," "molecular tumor board," "liquid biopsy," "ctDNA," "MRD," "polygenic risk score," "PRS," "incidental findings," "ACMG SF," "GINA," "GRCh38," or "T2T-CHM13." For broader clinical AI lifecycle, see clinical-ai-ml. For SaMD on genomic algorithms, see fda-samd. For the EHR integration of orders/results, see ehr-integration and fhir-integration.
health-chatbots
When the user wants to design, build, evaluate, or deploy a conversational AI / chatbot in a healthcare setting. Also use when the user mentions "health chatbot," "symptom checker," "triage bot," "mental health chatbot," "medication reminder bot," "appointment booking bot," "post-discharge follow-up bot," "AI scribe," "ambient scribe," "clinical conversational AI," "LLM in healthcare," "HIPAA-eligible LLM," "Azure OpenAI BAA," "Bedrock BAA," "Vertex AI BAA," "Anthropic BAA," "suicide safety classifier," "988," "self-harm detection in chat," "retrieval-grounded healthcare," or "patient-facing AI." For underlying ML modeling see clinical-ai-ml. For FDA pathway analysis see fda-samd.
health-content-writing
When the user wants to write, edit, or audit patient-facing health content. Also use when the user mentions "patient education," "after-visit summary," "AVS," "patient portal copy," "OpenNotes," "plain language," "health literacy," "readability," "Flesch-Kincaid," "SMOG," "FRY," "Dale-Chall," "teach-back," "condition page," "discharge instructions," "secure-message tone," "medication instructions," "informed-consent plain language," "CLAS standards," "Section 1557 language access," "translation," "transcreation," "back-translation," "icon array," or "numeracy in healthcare." For accessibility of the surrounding UI, see accessibility-healthcare. For program-level outreach orchestration, see patient-engagement. For clinical-documentation written for other clinicians (not patients), see clinical-documentation.
health-data-lake
When the user wants to design, build, or operate a clinical / healthcare data lake, lakehouse, or warehouse. Use when the user mentions "health data lake," "clinical data warehouse," "healthcare lakehouse," "OMOP," "PCORnet CDM," "Sentinel CDM," "i2b2," "CMS BCDA," "OHDSI," "ATLAS," "HADES," "Athena vocabulary," "FHIR Bulk Data," "$export," "flat FHIR," "SQL-on-FHIR," "Pathling," "Epic Clarity," "Caboodle," "Cerner Millennium ETL," "EMPI," "data quality dashboard," "Achilles," "tokenization vault," "Delta Lake," "Iceberg," "bronze/silver/gold," "Unity Catalog," "Lake Formation," "Snowflake healthcare," "Databricks Lakehouse for Healthcare," or "HIPAA-eligible warehouse." For analytics on top of curated data, see population-health-analytics or clinical-research. For raw FHIR API integration, see fhir-integration. For HL7 v2 ingestion specifics, see hl7-v2.
healthcare-context
When the user wants to create or update their healthcare context document, or whenever any other healthcare skill needs to understand the organization, patient population, regulatory jurisdiction, EHR/clinical systems, terminology in use, and security posture. Also use when the user mentions "healthcare context," "healthcare profile," "organization context," "covered entity," "business associate," "regulated jurisdiction," "EHR vendor," or "we are a [hospital/clinic/payer/digital health/etc]." Read this file first before any other healthcare skill — it controls assumptions every other skill makes (HIPAA vs. GDPR, FHIR vs. HL7 v2, Epic vs. Cerner, etc.).
healthcare-cybersecurity
When the user wants to design, assess, or harden a healthcare cybersecurity program — covering threat-aligned safeguards, medical device security, ransomware readiness, network segmentation, supply chain, and incident response. Also use when the user mentions "HHS 405(d)," "HICP," "Health Industry Cybersecurity Practices," "NIST CSF healthcare," "NIST SP 800-66," "medical device cybersecurity," "FDA premarket cybersecurity," "FDA postmarket cybersecurity," "SBOM," "SPDX," "CycloneDX," "MDS²," "IEC 80001," "IEC 62443," "zero trust healthcare," "network segmentation clinical," "ransomware playbook," "MFA healthcare," "PAM," or "phishing healthcare." For the regulatory basis, see hipaa-compliance. For operational PHI controls, see phi-handling. For audit-log design, see audit-logging.
hitrust-csf
When the user is preparing for, scoping, scoring, or maintaining a HITRUST CSF assessment or certification. Also use when the user mentions "HITRUST," "HITRUST CSF," "e1," "i1," "r2," "MyCSF," "PRISMA," "control maturity," "CAP," "corrective action plan," "validated assessment," "interim assessment," "readiness assessment," "inheritance," "CSP inheritance," "authoritative sources," or "HITRUST audit." For HIPAA itself, see hipaa-compliance. For cybersecurity program design, see healthcare-cybersecurity. For audit logs, see audit-logging.
hl7-v2
When the user wants to design, parse, generate, or troubleshoot HL7 v2.x pipe-delimited messages. Use when the user mentions "HL7 v2," "HL7 2.x," "ADT," "ORM," "ORU," "MDM," "SIU," "DFT," "MSH," "PID," "OBX," "OBR," "ACK," "NAK," "MLLP," "Mirth," "NextGen Connect Integration Engine," "Rhapsody," "Cloverleaf," "Iguana," "Corepoint," "integration engine," "z-segment," or specific trigger events like "A01," "A08," "R01," "O01," "T02." For modern REST/JSON exchange, see fhir-integration. For DICOM imaging messages, see dicom-imaging. For CDA clinical documents, see cda-ccda.
ihe-profiles
When the user wants to design, deploy, or troubleshoot IHE (Integrating the Healthcare Enterprise) integration profiles. Use when the user mentions "IHE," "XDS," "XDS.b," "XDR," "XDM," "XCA," "PIX," "PDQ," "ATNA," "BPPC," "CT (Consistent Time)," "DSUB," "MHD," "PIXm," "PDQm," "IUA," "MHDS," "mCSD," "Cross-Enterprise Document Sharing," "ITI Technical Framework," "PCC profile," "RAD profile (SWF, XDS-I.b)," or "actors and transactions." For FHIR-native exchange, see fhir-integration. For TEFCA-level policy and QHIN structure, see tefca-hie. For audit details, see audit-logging.
medical-coding
When the user wants to design or build software that touches medical coding — computer-assisted coding (CAC), autocoders, NLP for clinical coding, code-set validation, audit support, HCC/risk-adjustment capture, or revenue-cycle pipelines. Use when the user mentions "ICD-10," "ICD-10-CM," "ICD-10-PCS," "CPT," "HCPCS," "HCPCS Level II," "J-codes," "CDT," "NDC," "DRG," "MS-DRG," "APC," "modifiers," "NCCI edits," "MUE," "PTP," "LCD," "NCD," "E/M coding," "MDM," "computer-assisted coding," "CAC," "autocoding," "coding audit," "RAC," "ZPIC," "UPIC," "OIG audit," "problem list," "HCC capture," or "RAF coding." For end-to-end claim submission/remittance, see billing-claims. For HCC risk score modeling and VBC programs, see value-based-care. For prior auth, see prior-authorization. This skill is for engineers building coding systems — it does not assign codes for real patient encounters.
medical-imaging-ai
When the user wants to design, build, validate, deploy, or monitor AI/ML on medical images. Use when the user mentions "medical imaging AI," "radiology AI," "imaging ML," "DICOM AI," "PACS AI," "CAD," "computer-aided detection," "computer-aided diagnosis," "AI triage," "worklist prioritization," "U-Net," "nnU-Net," "MONAI," "MedSAM," "BiomedCLIP," "RadFM," "MIMIC-CXR," "CheXpert," "TCIA," "LIDC-IDRI," "ChestX-ray14," "DICOM SR for AI results," "AI orchestrator," "Nuance Precision Imaging Network," "Blackford," "Calantic," "DeepHealth," "GE Edison," "Philips ISP," or asks how to wire imaging AI into the reading workflow. For pure DICOM transport without AI, see dicom-imaging. For SaMD regulatory work, see fda-samd. For general clinical AI lifecycle, see clinical-ai-ml.
medication-reconciliation
When the user wants to design, build, or improve medication reconciliation workflows at transitions of care. Also use when the user mentions "med rec," "medication reconciliation," "BPMH," "best possible medication history," "admission med rec," "discharge med rec," "transfer med rec," "Surescripts medication history," "pharmacy fill history," "RxNorm," "RxCUI," "SCD," "SBD," "NDC," "DDI," "drug-drug interaction," "First Databank," "Medi-Span," "Multum," "RxNav DDI," "ISMP high-alert," "MedicationStatement vs MedicationRequest," "MedicationDispense," "MedicationAdministration," "NPSG 03.06.01," or "MIPS med rec measure." For order entry plumbing, see cpoe-orders. For RxNorm + ATC terminology depth, see terminology-services.
patient-engagement
When the user wants to design, build, or evaluate a patient engagement program. Also use when the user mentions "patient engagement," "patient outreach," "patient activation," "patient retention," "appointment reminders," "no-show reduction," "care gap closure," "preventive screening outreach," "chronic care management outreach," "post-discharge follow-up," "PAM," "patient activation measure," "CAHPS," "NPS," "omnichannel patient communication," "SMS healthcare," "TCPA," "HIPAA texting," "secure messaging," "behavior change," "stages of change," "Health Belief Model," "COM-B," "BJ Fogg," "Salesforce Health Cloud," "Twilio healthcare," "Innovaccer," "Notable," "Memora," "Conversa," "mPulse," "Unite Us," "Findhelp," "NowPow," or "closed-loop SDOH referral." For the content of messages, see health-content-writing. For accessibility of touchpoints, see accessibility-healthcare. For the underlying portal, see patient-portal.
patient-portal
When the user wants to design or build a patient portal, patient mobile app, or patient-facing API. Also use when the user mentions "patient portal," "MyChart," "FollowMyHealth," "NextMD," "Patient Gateway," "patient access," "CMS Patient Access Rule," "Information Blocking," "USCDI," "OpenNotes," "open notes," "proxy access," "caregiver access," "adolescent confidentiality," "minor portal," "secure messaging," "online scheduling," "results release," "patient identity proofing," "IAL2," "ID.me," "CLEAR," "Persona," "Stripe Identity," "Socure," or "patient mobile app." For provider-facing SMART apps see smart-on-fhir. For telehealth video flows see telehealth-platform.
phi-handling
When the user is designing or reviewing the operational controls around PHI — how to de-identify, anonymize, pseudonymize, encrypt, mask, minimize, or securely retain Protected Health Information across structured data, free text, images, audio, and biometrics. Also use when the user mentions "Safe Harbor de-identification," "Expert Determination," "limited data set," "DUA," "k-anonymity," "l-diversity," "t-closeness," "differential privacy," "encryption at rest," "TLS 1.2," "KMS," "HSM," "RBAC," "ABAC," "break the glass," "minimum necessary in practice," "DICOM PHI," "burned-in PHI," "audio PHI," "biometric PHI," "secure deletion," "retention schedule," or "cross-border PHI." For the regulatory backdrop, see hipaa-compliance. For audit-log design, see audit-logging. For EU rules, see gdpr-health-data.
population-health-analytics
When the user wants to design, build, or evaluate a population health analytics platform. Use when the user mentions "population health," "pop health," "risk stratification," "HCC," "CMS-HCC," "ACG," "DxCG," "LACE," "rising risk," "high cost members," "care gaps," "HEDIS," "eCQM," "attribution," "value-based care analytics," "SDOH," "Z-codes," "Gravity Project," "HRSN," "PRAPARE," "AHC-HRSN," "OMOP," "PCORnet," "registry," "patient registry," "FHIR Bulk Export," "longitudinal patient record," "patient master," "MPI for analytics," "network leakage," "outreach prioritization," "uplift modeling," "PAM," or "patient activation measure." For VBC contract design, see value-based-care. For FHIR Bulk Export mechanics, see fhir-integration. For the upstream clinical and claims feeds, see ehr-integration and billing-claims.
prior-authorization
When the user wants to design, build, integrate, or automate prior authorization workflows. Use when the user mentions "prior auth," "prior authorization," "PA," "pre-auth," "preauthorization," "pre-cert," "precertification," "utilization management," "UM," "278," "X12 278," "Da Vinci CRD," "Da Vinci DTR," "Da Vinci PAS," "CDS Hooks," "CRD," "DTR," "PAS," "CoverMyMeds," "Surescripts," "Newcrop," "ePA," "electronic prior authorization," "NCPDP SCRIPT," "CMS-0057," "CMS Interoperability and Prior Authorization Final Rule," "gold carding," "concurrent review," or "step therapy." For claim submission after PA is obtained, see billing-claims. For coding the service being authorized, see medical-coding. For VBC delegation of UM, see value-based-care.
public-health-reporting
When the user wants to design, build, or troubleshoot reporting from clinical systems to public health authorities. Use when the user mentions "public health reporting," "ELR," "Electronic Laboratory Reporting," "eCR," "electronic case reporting," "eICR," "Reportability Response," "RR," "immunization registry," "IIS," "VXU," "syndromic surveillance," "BioSense," "NSSP," "cancer reporting," "NAACCR," "NPCR," "SEER," "birth registry," "EBR," "death registry," "EDR," "EDRS," "reportable conditions," "RCKMS," "CSTE," "APHL AIMS," "NEDSS," "ONC g.10," "Promoting Interoperability public health," "state HIE submission," or "COVID case reporting." For the underlying HL7 v2 message mechanics, see hl7-v2. For FHIR resources used by these IGs, see fhir-integration. For terminology bindings (LOINC, SNOMED CT, ICD-10-CM, CVX), see terminology-services.
remote-patient-monitoring
When the user wants to design, build, or bill a remote patient monitoring (RPM) program. Also use when the user mentions "RPM," "remote patient monitoring," "RTM," "remote therapeutic monitoring," "CPT 99453," "99454," "99457," "99458," "99091," "98975," "98976," "98977," "98980," "98981," "16-day rule," "BP cuff integration," "glucometer integration," "CGM," "pulse oximeter," "weight scale," "ECG patch," "smart inhaler," "peak flow," "device telemetry," "FHIR Observation ingest," "cellular device," "BLE device," or "patient device pairing." For consumer wearables (Apple/Google/Fitbit/Garmin/Oura/Whoop) see wearables-integration. For video visits paired with RPM see telehealth-platform.
smart-on-fhir
When the user wants to build a SMART on FHIR app, configure OAuth against an EHR's FHIR API, or implement Backend Services. Also use when the user mentions "SMART," "SMART on FHIR," "SMART App Launch," "EHR launch," "standalone launch," "well-known/smart-configuration," "smart-configuration," "launch context," "launch/patient," "launch/encounter," "SMART scopes," "patient/*.read," "user/*.write," "system/*.read," "SMART v2 scopes," "fhirUser," "PKCE," "JWT assertion," "Backend Services," "client credentials FHIR," or "Bulk Data Access." For deeper FHIR resource work, see fhir-integration. For vendor-specific OAuth quirks, see ehr-integration. For CDS Hooks integration, see clinical-decision-support.
tefca-hie
When the user wants to plan, join, or build against TEFCA or other US health information exchange networks. Use when the user mentions "TEFCA," "Common Agreement," "QHIN," "QTF," "QHIN Technical Framework," "ONC TEFCA," "Carequality," "CommonWell," "eHealth Exchange," "Health Gorilla," "Epic Nexus," "KONZA," "MedAllies," "Velatura," "Direct messaging," "HISP," "IAS," "Individual Access Services," "Required Information for Coverage," "regional HIE," "query-based exchange," "treatment payment operations," or "patient matching across networks." For the underlying technical profiles, see ihe-profiles. For FHIR mechanics, see fhir-integration. For identity controls, see healthcare-cybersecurity.
telehealth-platform
When the user wants to design, build, or evaluate a telehealth platform. Also use when the user mentions "telehealth," "telemedicine," "virtual care," "video visit," "asynchronous care," "store-and-forward," "e-visit," "tele-ICU," "tele-stroke," "tele-behavioral," "tele-psychiatry," "WebRTC video," "SIP video," "Doxy.me," "Zoom for Healthcare," "Microsoft Teams EHR," "originating site," "distant site," "IMLC," "PsyPACT," "Nurse Licensure Compact," "telehealth parity," "Ryan Haight," "DEA telemedicine," "controlled substances by telemedicine," or "RPM video." For wearables/RPM device telemetry, see remote-patient-monitoring. For consent and PHI flow, see hipaa-compliance and phi-handling.
terminology-services
When the user wants to choose, map, validate, or serve healthcare code systems and value sets. Use when the user mentions "SNOMED CT," "ICD-10-CM," "ICD-10-PCS," "ICD-11," "CPT," "HCPCS," "LOINC," "RxNorm," "NDC," "UCUM," "CVX," "terminology server," "ValueSet," "ConceptMap," "$expand," "$lookup," "$validate-code," "$translate," "VSAC," "UMLS," "OMOP Athena," "RxNav," or "code mapping." For FHIR resource modeling generally, see fhir-integration. For coding for billing workflow, see medical-coding.
value-based-care
When the user wants to design or build software for value-based care (VBC) — risk adjustment, quality measurement, ACO/REACH analytics, capitation reconciliation, bundled payments, MIPS/QPP, HEDIS, Star Ratings, attribution, network performance. Use when the user mentions "value-based care," "VBC," "ACO," "MSSP," "REACH," "ACO REACH," "PCF," "AHEAD," "CKCC," "KCC," "OCM," "EOM," "CJR," "BPCI-A," "DCE," "DSO," "MIPS," "QPP," "APM," "HEDIS," "Star Ratings," "HCC," "CMS-HCC," "v28," "RAF," "RADV," "MEAT," "attribution," "shared savings," "capitation," "bundled payment," "eCQM," "CQL," "MIPS measure," "TIN/NPI hierarchy," "leakage," or "network steerage." For coding mechanics that feed risk adjustment, see medical-coding. For claims and remittance reconciliation, see billing-claims. For PA delegation under VBC, see prior-authorization.
wearables-integration
When the user wants to integrate consumer wearables or fitness devices into a clinical or health-app workflow. Also use when the user mentions "Apple HealthKit," "HKQuantityType," "HKSampleType," "Apple Health Records," "Health Connect," "Google Health Connect," "Google Fit," "Fitbit Web API," "Garmin Health API," "Oura," "Whoop," "Dexcom," "Abbott LibreView," "Medtronic CareLink," "Withings," "CGM integration," "BLE health profile," "GATT," "Heart Rate Profile," "Blood Pressure Profile," "Glucose Profile," "Body Composition Service," "Health Device Profile," "HDP," or "consumer wearable BAA." For clinical-grade RPM with billable CPT codes see remote-patient-monitoring. For FHIR Observation modeling see fhir-integration.
Quality Score: 51/100
Details
- Author
- aks-builds
- Repository
- aks-builds/healthcareskills
- Created
- 1 months ago
- Last Updated
- yesterday
- Language
- JavaScript
- License
- MIT