Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

Other discussion on VUHID and other health
-          VUHID is an attribute that comes in thru these other systems
-          Mike Kirkwood – sees it as joining Patient access and federal interoperability.  Could be used for routing patient ID between systems.
 
Fraser’s asked if OpenID and SAML2.0 are in conflict?
-          Brett McDowell – OpenID only does Level 1.  Need InfoCards or PKI to get to higher levels.  Work at Concordia Group, with Paul Madsen, is trying to move OpenID to these higher levels.
-          Fraser thought that Level 3 assurance is needed in this project and agreed to in earlier calls?
-          Adrien:  Why aren’t we working with Concordia?
-          Barry: Is Concordia working with patient access to NHIN?
-          Adreien:  Concordia is working on joining OpenID to get to level 3 to get compatible.
-          Barry: Concordia should be leaned on, and Adrian was in agreement on that.
-          Mike: Answers aren’t know, but can learn options from Concordia.
 
Fraser – asked Dan to add the Concordia Group liaison as part of the project plan.
Dan – many other groups want to participate as well.
Joni – will put Dan in touch with Paul Madsen at Concordia.
 
Dan – said he would add VUHID, and the Concordia liasoning to plan.
 
Dan then asked for input on the Project Description
 
Barry – put use case in italics.
Fraser – the Use Cases should support the patient meaningful use needs as recommended by Ray Campbell, MHDC.
Bob – question, does NHIN support this use case?
Dan – technically, no, but it must for meaningful use.
Bob – do we have to worry about if NHIN will do this, or we design?
Fraser – we should “worry” and include it in the project.
Dan – Provider to provider is already covered by NHIN.  Adding in patients adds them as a “user” in this process.
 
Discussion around a “lock-box” approach to patient control of their information to share with providers:
Barry – lock-box is one mechanism, but there could be others.
Kickwood – these questions are good for talking to funders.
 
Adrian – need a “problem” statement in the plan.
Dan – obvious we should add that.  Agreement to re-use older slides to add back.
 
Dan then ask for input on the Project Management section:
 
Discussion about senior Kantara people getting involved.  Decided to add Roger Martin, Executive Director, to project management section as a resource.
-          Fraser indicated that Roger has been involved to help on the fundraising process.
 
Schedule and Deliverables Section:
-          General agreement to add scheduled times
 
Value and Benefits Section:
Agreement to add the connection to the problem statement that will be added above.
Kirkwood – code releases, etc. should be announced as an outputs.
 
NEXT STEPS:
Group will edit plan online.  Plan will be put on the Wiki so changes can be monitored.
-          Dan will be editor and people should send him updates, or get his permission to bigger changes.
-          Once on the wiki, the group should be told so they can read/edit it.
-          Deadline for final changes will be a week out.
-          Next call will be to review and approve (we’ll have to get quorum!)

3. Other Business

None

Next Meeting

  • Date: Thursday, April 15, 2010
  • Time: 10am PST | 1pm EST | 5pm UTC | 7pm CEST (Time Chart)
  • Dial-In: Skype: +9900827044630912 - North American Dial-In: +1-201-793-9022
  • Code: 4630912

NOTE: Do not follow the code with a "#" symbol as it may cause the code not to be recognized.