Action Items
#
Date
Action
Status
Owner
Due Date
1
3/26/2010
Next time we will do a better job to prep everyone with pointers to all of the necessary information
2
3/26/2010
Read over material that has been created to date



3
3/26/2010
Propose 2-3 topics of discussion that we can focus on for next week



4
3/31/2010
Arien will formalize proposal on table in draft spec
Complete
Arien

5
3/31/2010
Group will review with goal of calling for consensus next meeting
Open
All

6
4/7/2010
Move example sections off to a separate example section of and just having one normative section describing what a health internet address looks like
Completed
Arien
4/14/10
7
4/7/2010
Review revised document and vote on whether this can be moved to the larger implementation group
Open
All
4/14/10
8
4/16/2010
Amend Health Domain Name sentence read:
Closed
Arien
4/20/2010
Organizations that manage Health Domain Names MUST maintain directory NHIN Direct HISP Address Directory entries for the Health Domain Name, as specified by the Abstract Model , and corresponding to the rules established for concrete implementations. For example, for a REST implementation, organizations will include implementations of the Abstract Model. Organizations that manage Health Domain Names MUST ensure that transactions are available for Health Endpoint Names, either A through proprietary means or CNAME DNS RRs, for an SMTP-based implementation, the following the Destination role transactions of the Abstract Model. Organizations may take on the HISP role or assign this function to another organization will maintain at least one MX DNS RR. playing the HISP role.
9
4/16/2010
Ensure REST/IHE and SMTP concrete implementation Straw Cases to use health information exchange mapping
Open
Arien
4/20/2010
10
4/16/2010
Ensure that the Health Endpoint Name is responsible for routing the end the transaction is received to the endpoint
Closed
Arien
4/20/2010
11
4/16/2010
Insert Version Number
Closed
Arien
4/20/2010
12
4/16/2010
Workgroup will vote for consensus
Open
Arien
4/20/2010
13
4/21/2010
All WG Members will vote on “Implementation Group Endorsements” here: http://nhindirect.org/Addressing+Specification+Implementation+ Group+Endorsements
Open
All
4/27/10
14
4/21/2010
Arien/Karen will write in a revised wording for the text under Health Domain Name
Open
Arien/Karen
4/27/10
15
4/21/2010
Arien or Honora will send a definitive email on Mondays as to whether or not a Thursday Addressing WG meeting will be held
Open
Honora/Arien
Ongoing












Key Decisions



#
Date
Decision



1
3/31/2010
Wes is WG Leader



2
3/31/2010
We want to use only the most commonly used and well supported features of any standard



3
3/31/2010
The addressing spec needs three components:



1. End point receiver (ex: wesj)



2. Domain name -- business organization (ex: Rishel.com) associated with the end point



3. Mapped through an external routing organization or technology organization (ex: Google or Gmail)



4
3/31/2010
Treat patient address in the same way (has the same three parts) as above