Exchanging Imaging Documents Within a Specific Health Information Exchange Domain

Printer Friendly, PDF & Email
Type Standard Implementation/Specification Standards Process Maturity Implementation Maturity Adoption Level Federally required Cost Test Tool Availability
Standard
Final
Production
Feedback Requested
No
Free
No
Implementation Specification
Final
Production
Rating 1
No
Free
Yes
Implementation Specification
Final
Production
Rating 4
No
Free
Yes
Implementation Specification
Final
Production
Rating 4
No
Free
Yes
Emerging Implementation Specification
Balloted Draft
Pilot
Rating 1
No
Free
No
Emerging Implementation Specification
Balloted Draft
Pilot
Rating 1
No
Free
No
Limitations, Dependencies, and Preconditions for Consideration Applicable Security Patterns for Consideration
  • IHE-PIX and IHE-PDQ are used for the purposes of patient matching and to support this interoperability need.
  • See IHE projects in the Interoperability Proving Ground.
  • Secure Communication – create a secure channel for client-to-server and server-to-server communication.
  • Secure Message Router – securely route and enforce policy on inbound and outbound messages without interruption of delivery.
  • Authentication Enforcer – centralized authentication processes.
  • Authorization Enforcer – specifies access control policies.
  • Credential Tokenizer – encapsulate credentials as a security token for reuse  (e.g., – SAML, Kerberos).
  • Assertion Builder – define processing logic for identity, authorization and attribute statements.
  • User Role – identifies the role asserted by the individual initiating the transaction.
  • Purpose of Use - Identifies the purpose for the transaction.