Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

DRAFT CHATER SUBJECT TO FURTHER REVISION AND APPROVAL

(1) WG NAME (and any acronym or abbreviation of the name): _The WG name, acronym and abbreviation must not include trademarks not owned by the Organization, or content that is infringing, harmful, or inappropriate.
_Potential Names:

  1. One Login for Health Work Group
  2. Single Health Login Work Group
  3. Health Login Work Group
  4. EZ Login Work Group
  5. Simple Health Login Work Group
  6. Single Health SignOn Work Group
  7. Health Identity and Assurance


(2) PURPOSE: Please provide a clear statement of purpose and justification why the proposed WG is necessary.

The <INSERT NAME> Work Group shall design, implement and test reference applications for secure access to health information. Two use cases are proposed that would be developed and supported as part of the work group. One is for consumers to be able to access their health records with a standardized login system, and secondly, a way for emergency workers to access critical health information during emergencies or natural disasters.

The goal of this activity is to engage the broadest community participation to facilitate the adoption of the reference implementations and specifications by the healthcare industry, worldwide.Specific goals of this group are to:

  • Develop a reference implementation for consumer access, using open source solutions.
  • Develop a reference implementation for emergency health care workers access to critical health information using open source solutions.
  • Recommend, if appropriate, all or parts of these systems to be integrated with the emerging US Nationwide Health Information Network (NHIN) being developed by the US Department of Health and Human Services and the Offices of the National Coordinator.
  • Educate the community on how the system should operate and how such a system should function.
  • Work with the vendor community to ensure interoperability between systems.

(3) SCOPE: _Explain the scope and definition of the planned work.
_The <INSERT NAME> WG is chartered to:

...

(4) DRAFT TECHNICAL SPECIFICATIONS: List Working Titles of draft Technical Specifications to be produced (if any), projected completion dates, and the Standards Setting Organization(s) to which they will be submitted upon approval by the Membership.

Draft Technical Specifications
Develop a draft specification of our consumer connectivity to their health care records, and a similar draft specification for emergency access to health information.

(5) OTHER DRAFT RECOMMENDATIONS: Other Draft Recommendations and projected completion dates for submission for All Member Ballot.

Develop appropriate White Papers, Technical Reports, Guidelines as needed.

(6) LEADERSHIP: Proposed WG Chair and Editor(s) (if any) subject to confirmation by a vote of the WG Participants.

John Fraser, MEDNETWorld.comPete com
Pete Palmer, Wells Fargo

(7) AUDIENCE: Anticipated audience or users of the work.

The audience for this work group includes but is not limited to: Health Information Exchanges (HIEs), open-source developers and industry vendors and similar groups

(8) DURATION: Objective criteria for determining when the work of the WG has been completed (or a statement that the WG is intended to be a standing WG to address work that is expected to be ongoing).

The Kantara Initiative Leadership Council charters the <NewName> Work Group for five years. It may be amended from time to time, with changes approved by the Leadership Council. This charter will expire on <INSERT DATE>.

(9) IPR POLICY: The Organization approved Intellectual Property Rights Policy under which the WG will operate.

<CHOOSE> Kantara IPR Policy - Liberty option with request for consideration of adoption of a Creative Commons Option

(10) RELATED WORK AND LIAISONS: Related work being done in other WGs or other organizations and any proposed liaison with those other WGs or organizations.

...