MCP server for generating clinical SOAP notes from ambient conversation transcripts with HIPAA compliance, ICD-10 coding, and EHR integration
Critical failures across all dimensions. The single tool 'execute_skill_action' has a minimal description (89 chars, below the 194-char baseline) that lacks WHEN/WHY context. Input schema is present but parameters lack descriptions entirely, 'patient_encounter_id' and 'audio_transcript_snippet' have no guidance on format, constraints, or dependencies. Output schema is completely undocumented; the client.py mock returns a complex object with 9 fields (subjective_summary, objective_metrics, assessment_icd10_codes, etc.) but no schema is declared to the MCP server. No error handling, no recovery guidance, no validation rules. The tool name 'execute_skill_action' is generic and violates verb_noun clarity, 'generate_clinical_soap_note' would be far more specific. No security considerations (HIPAA data handling, credential injection, audit logging) despite clinical/sensitive context. Tool composition is monolithic, should split SOAP generation, ICD-10 coding, and EHR sync into separate tools for agent composability.
Execute clinical SOAP note generation from patient encounter data and audio transcripts
Tool name 'execute_skill_action' is generic and violates verb_noun convention. Should be 'generate_clinical_soap_note' to clearly signal SOAP generation intent.
Input parameters lack descriptions entirely. 'patient_encounter_id' and 'audio_transcript_snippet' have no guidance on format, length, encoding, or constraints. LLMs cannot infer parameter meaning from names alone.
Output schema is completely undocumented. The client.py mock returns 9 fields (subjective_summary, objective_metrics, assessment_icd10_codes, plan_interventions, ehr_epic_cerner_fhir_json_synced, physician_documentation_time_saved_pct, etc.) but no schema is declared to the MCP server. LLMs cannot plan downstream calls without knowing return structure.
No error handling or recovery guidance. Tool description does not explain failure modes, retryability, or what to do if SOAP generation fails or HIPAA validation rejects input.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 23 | 2026-07-28+ | v2 |
Tool is monolithic and violates single-responsibility principle. Combines SOAP generation, ICD-10 coding, objective metrics extraction, and EHR sync into one tool. Should split into separate tools (generate_soap_subjective, extract_objective_metrics, assign_icd10_codes, sync_to_ehr) for agent composability.