ihe-profiles

Provides IHE integration profile information including actors, transactions, and FHIR equivalents.

1|1|Updated May 16, 2026
One-click install
npx skills add https://github.com/aks-builds/healthcareskills --skill ihe-profiles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ihe-profiles
Source: https://github.com/aks-builds/healthcareskills/tree/main/skills/ihe-profiles
Command: npx skills add https://github.com/aks-builds/healthcareskills --skill ihe-profiles

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides in-depth knowledge and expert guidance on IHE integration profiles, helping healthcare professionals design, deploy, and troubleshoot interoperable healthcare systems.

Core Features & Use Cases

  • IHE Profiles Overview: Comprehensive information on various IHE profiles, including their purpose, use cases, and FHIR equivalents.
  • Actor and Transaction Analysis: Detailed explanations of actors and transactions in key profiles like XDS, XDR, XCA, and PIX.
  • Use Case Consultation: Expert consultation on choosing the right profiles and actors for specific use cases, such as document sharing, patient identity resolution, and audit logging.

Quick Start

Use the ihe-profiles skill to get an overview of the XDS.b profile and its key actors and transactions.

Frequently Asked Questions about ihe-profiles

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

FAQPage Schema
What are IHE integration profiles and how do they enable healthcare interoperability?

IHE integration profiles define standardized workflows by grouping actors and transactions to solve specific healthcare interoperability use cases like document sharing and patient identity resolution across disparate systems.

How do I choose the right IHE profile for a clinical document sharing use case?

To choose an IHE profile for document sharing, evaluate the required actors and transactions within profiles like XDS, XDR, or XCA against your specific network topology and exchange requirements to determine the correct architectural fit.

What is the difference between IHE XDS, XDR, and XCA transactions?

XDS handles centralized document registry and repository sharing, XDR supports direct point-to-point document transmission, and XCA enables cross-community document query and retrieval across federated healthcare enterprises.

Can I map IHE integration profiles to their equivalent FHIR resources?

Yes, IHE integration profiles map to FHIR equivalents by translating traditional actors and transactions into corresponding FHIR RESTful operations and resource interactions for modern healthcare interoperability implementations.

Do I need prior knowledge of IHE standards to use these healthcare integration workflows?

Yes, understanding IHE standards and healthcare workflows is required. This guidance targets advanced system design, assuming baseline knowledge of interoperability transactions and clinical data exchange mechanisms.

How does the PIX profile handle patient identity resolution across different healthcare systems?

The PIX profile resolves patient identity cross-referencing by defining specific actors and transactions that maintain and query a master patient index to correlate patient identifiers across disparate healthcare applications.