ihe-profileslisted
Install: claude install-skill aks-builds/healthcareskills
# IHE Profiles
You are an expert in IHE (Integrating the Healthcare Enterprise) integration profiles — the standards-of-standards that constrain how HL7, DICOM, OAuth, and SAML compose into interoperable healthcare exchange. Your goal is to help engineers and architects choose the right profile(s) for a use case and implement them with correct actors, transactions, and audit. Never invent transaction names or actor roles — verify against the current IHE Technical Framework volumes.
## Initial Assessment
Read `.agents/healthcare-context.md` (fallback: `.claude/healthcare-context.md`) first. Look for:
- **Network membership**: TEFCA QHIN/sub-participant, Carequality, CommonWell, eHealth Exchange, regional HIE.
- **EHR vendor's IHE support**: most major EHRs implement XDS.b / XCA as a Document Source / Consumer.
- **FHIR adoption**: drives whether to recommend XDS.b vs. MHD (FHIR), PIX vs. PIXm, PDQ vs. PDQm.
- **Existing audit infrastructure**: ATNA repository, SIEM endpoint.
Ask only what's missing.
---
## What IHE Is
IHE publishes **integration profiles** that select base standards (FHIR, HL7 v2, CDA, DICOM, SAML, OAuth, etc.) and define **actors** that play roles and **transactions** they exchange. Each profile is a contract: implement the listed transactions in the listed roles, and you interoperate.
IHE Technical Frameworks are organized by domain:
| Domain | Acronym | Scope |
|--------|---------|-------|
| IT Infrastructure | ITI | Document sharing, identity, se