imedicalxc-doctor-extend-scope

Categorize third-party system integration needs into hospital information system teams and generate handover documents.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/SkylerCook/imedical.agents --skill imedicalxc-doctor-extend-scope
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: imedicalxc-doctor-extend-scope
Source: https://github.com/SkylerCook/imedical.agents/tree/main/plugins/imedicalxc-doctor-extend-engineer/skills/imedicalxc-doctor-extend-scope
Command: npx skills add https://github.com/SkylerCook/imedical.agents --skill imedicalxc-doctor-extend-scope

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the process of determining the team responsible for third-party system integration, categorizing it into the doctor station group, hospital information platform group, or basic platform group, and producing a handover document.

Core Features & Use Cases

  • Scope Analysis: Determines the appropriate team for third-party system integration needs.
  • Decision Document Output: Generates a handover document for team transition.
  • Use Case: For instance, when a new third-party system needs to be integrated with the hospital information system, this Skill can quickly identify the responsible team and provide a handover document.

Quick Start

Analyze the integration scope of the new third-party system using the imedicalxc-doctor-extend-scope skill.

Frequently Asked Questions about imedicalxc-doctor-extend-scope

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

FAQPage Schema
How do I determine the correct team for third-party system integration in a hospital information system?

Third-party system integration scope analysis categorizes integration needs into doctor station, hospital information platform, or basic platform groups to identify the correct team. It evaluates workflow embedding, data transformation, and technical compatibility to allocate responsibilities accurately.

What is included in a handover document for hospital IT operations team transition?

A handover document for team transition details the integration scope analysis, including workflow embedding, data transformation requirements, and technical compatibility. It ensures the receiving team understands the categorized responsibilities for the hospital information system.

When do I need to analyze integration requirements for a hospital information platform?

You need to analyze integration requirements when a new third-party system requires workflow embedding, data transformation, or technical compatibility checks within the hospital information system. This analysis determines whether the doctor station, hospital information platform, or basic platform team handles it.

How do I analyze technical compatibility for third-party system integration?

Analyzing technical compatibility for third-party system integration involves evaluating workflow embedding and data transformation needs against the hospital information system's capabilities. This process categorizes the integration scope into the appropriate team group for seamless system operations.

Can I use this approach for basic platform group allocation in IT operations?

Yes, this approach supports basic platform group allocation by analyzing third-party system integration requirements. It evaluates technical compatibility and workflow embedding to determine if the basic platform team is the appropriate recipient for the handover document.