Talk:HIE via IHE whitepaper

Notes from 12/15/2010 meeting:

• Add section to intro that provides our assumptions about the audience. We assume that the audience is anyone involved with HIEs. They could be from a nascent project or an established one. There are different entry points to the paper. But the paper is written to help even newbies.
• To top level sections, add:
  • Provider directory
  • Shared value system
• We need lots of diagrams. The idea would be that the diagrams would come from a library of components. At different points in the paper we create diagrams with different levels of detail but that use those components. At beginning we have an overview diagram that shows big picture of use cases but nothing about IHE. At end, we take that diagram and overlay IHE. In subsections, we carve up the big picture and add detail.
• Add to HIE overview section that this is not US centric. It's international.
• Eventually define a internationalized term for HIE community. HIE isn't good. Community, maybe. Say that XDS affinity domain = community = the term we use in the paper.
• Section in intro that says IHE doesn't have all the answers. I has components that you can plug in to solve certain things. We recommend that you start with a master plan (a master design or architecture) that will help guide you in the choices you make regarding use of the profiles.

Dnicholson 14:10, 5 April 2011 (CDT)

---

Notes from 1/13/2011 meeting:

• Much more detailed diagram with things like CT, UDDI, value set, etc. That fades into background as the bigger profiles come into focus.
• Let's just use "community" not "exchange community".
• Title: Using IHE profiles to build communities for health information exchange

Dnicholson 19:24, 13 January 2011 (UTC)

---

Icon set used by Daren: http://www.iconexperience.com/v_collections/purchase/

Dnicholson 08:48, 4 April 2011 (CDT)

---

Notes from 4/11/2011 meeting:

• Change "master plan" to "architecture" in section 1.4.
• Add language to section 1.4, last paragraph, about doing a standards-based approach to community creation.
• Add to purpose section a guide that points out which sections are detailed and which are high-level.
• Add to PDQ section that the main use of it is to get the global ID based on demographics, rather than based on a cross-referenced local ID. In some cases the local ID doesn't exist or is not cross-referenced.
• Remove PAM.
• Add to XDS section the list of advantages mentioned in the XDR section (add longevity of records to this).
• At end of paper, list well-known initiatives that use IHE.
• To XDM, add email as an example.
• Section 3.1.1, XDS isn't the heart of exchange. Instead, create a top-level (under 3) description of document sharing that points to IHE's 3 models and includes a diagram (supplied by Karen). 3 models are pub/discover, push and cross-community.
• In the NAV section, remove the language about "gulf". Instead, explain that NAV is a way to make pull be a push.
• Add DSUB and XCPD sections.
• Diagrams will have to rely on basic images. We cannot obtain custom icon sets for diagrams (as previously proposed.)

Dnicholson 17:24, 11 April 2011 (CDT)