follow-up-task-generator

Generate FHIR Task resources with urgency and ownership from patient data.

53|12|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/langcare/langcare-mcp-fhir --skill follow-up-task-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: follow-up-task-generator
Source: https://github.com/langcare/langcare-mcp-fhir/tree/main/skills/core/care-coordination/follow-up-task-generator
Command: npx skills add https://github.com/langcare/langcare-mcp-fhir --skill follow-up-task-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Analyzes recent encounters, condition updates, and lab results to generate prioritized FHIR Task resources for required follow-ups with urgency classification and responsible party assignment. This streamlines clinical workflows by turning scattered data into actionable tasks.

Core Features & Use Cases

  • Analyze encounters, conditions, labs, and medications to identify necessary follow-ups.
  • Generate FHIR Task resources with urgency, owner, and due dates, then deliver actionable tasks to providers.
  • Use case: after a patient visit, automatically produce follow-up tasks for abnormal labs, new diagnoses, and medication changes.

Quick Start

Instruct the system to generate follow-up tasks for a given patient after a specific encounter.

Frequently Asked Questions about follow-up-task-generator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate FHIR tasks for clinical follow-ups after a patient encounter?

To generate FHIR follow-up tasks, analyze patient encounters, conditions, labs, and medications to identify pending items and create prioritized tasks with urgency, owner, and due dates. This streamlines clinical workflows by turning scattered patient data into actionable care coordination items.

What patient data is needed to automate follow-up task generation?

Automated follow-up task generation requires reading Encounter, Condition, Observation, Procedure, MedicationRequest, and DiagnosticReport data. Analyzing these FHIR resources identifies necessary follow-ups for abnormal labs, new diagnoses, and medication changes to trigger actionable tasks.

How does urgency classification work for care coordination tasks?

Urgency classification for care coordination tasks assigns priority levels and responsible parties to generated FHIR Task resources based on analyzed clinical data. This ensures providers receive actionable follow-up items with appropriate due dates for pending patient care items.

Can I use FHIR Task resources to track abnormal lab result follow-ups?

Yes, you can use FHIR Task resources to track abnormal lab result follow-ups by analyzing Observation and DiagnosticReport data. The system generates tasks with urgency and ownership assignments, enabling automated actioning of pending clinical items after a patient visit.

Does follow-up task generation work with new diagnoses and medication changes?

Follow-up task generation works with new diagnoses and medication changes by analyzing Condition and MedicationRequest FHIR resources. It produces automated follow-up tasks with urgency classification and responsible party assignment for care coordination scenarios.

What are the limitations of automating clinical workflow tasks from patient data?

Automating clinical workflow tasks relies on reading specific FHIR resources including Encounter, Condition, Observation, Procedure, MedicationRequest, and DiagnosticReport. Task generation is limited to analyzing these inputs to identify follow-ups, meaning incomplete patient data records may restrict task creation.