HIE via IHE whitepaper

Note: This is a draft.

Introduction

Purpose

To describe how health information exchange (HIE) communities may be built from the ground up based on IHE profiles.

Overview of HIEs

I think we should level-set the reader on what we mean by an HIE and also acknowledge that HIEs can operate at various levels...e.g., a local hospital enterprise to a state or country. We should also identify/acknowledge that HIEs can/do vary in scope of functionality....some will do basic exchange of information; and some will offer other services. I think we should acknowledge this but then narrow the focus to those use cases that we want to address in this paper.

Background on IHE

Explain high level IHE concepts such as profiles, actors, transactions, etc. [Chris K] Yes, I think this should include a *brief* overview of IHE (the organization) and the concept of profiling integration (i.e., the technical framework) ....which might include the concept of domains.....with a focus on the Infrastructure Domain profiles

Patient ID management

Explain the importance of managing patient IDs across the community.

PIX

Describe how IDs may be cross-referenced via PIX.

PDQ

Describe how patients may be discovered via demographics queries.

Document sharing

Publish and discover

XDS.b

Describe document sharing via XDS.b.

Also include mention of NAV here.

XCA

Describe cross-community sharing via XCA.

Push to specified recipient

Describe document sharing via XDR and XDM.

Security and privacy

• Explain how profiles like ATNA, XUA and CT help ensure patient privacy via various security measures.
• Explain the concept of HIEs needing to have policies in place that dictate and describe how providers "play" within the HIE.