This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

May 21, 2013 Security Working Group Conference Call

From HL7Wiki
Jump to navigation Jump to search

Security Working Group Meeting

Back to Security Main Page

Attendees

Back to Security Main Page

Agenda

  1. (05 min) Roll Call, Approve Minutes & Accept Agenda
  2. (15 min) Approval of the Atlanta WGM Minutes Draft posted for your review
  3. (15 min) DS4P Doodle Poll update...
  4. (05 min) Other Business

Meeting Minutes

Roll Call, Approve Minutes & Accept Agenda

Motion: Kathleen/ Second: Adrianne, 0 Abstentions, 0 objections, Motion Passes

HL7 WGM - Atlanta, Georgia, USA Security WG - AGENDA Motion: Kathleen/ Second: Suzanne, 0 Abstentions, 0 objections, Motion Passes

Motion: Tony / Second: Adrianne, 0 Abstentions, 0 objections, 'Approval: 8, Motion Passes'

DS4P Scope Statement Presented at the TSC by Mike Davis Updates made at today's meeting: Motion: Kathleen/ Second: Adrianne, 0 Abstentions, 0 objections, 'Approval: 8, Motion Passes'

Updates made will be brought forth to TSC for approval

Other Business

e-mail from Lynn Laasko regarding DS4P project (to TSC):

Dear Co-chairs and Affiliate Chairs, This email is to inform you of new requests that will considered by the TSC at their upcoming teleconference on 2013-06-03 or in an e-vote.

Project Approvals

HL7 Data Segmentation for Privacy (DS4P) Implementation Guide, Project Insight TBD at TSC Tracker 2634, for Security WG of FTSD and cosponsored by CBCC WG of DESD. The project scope is the publication of a U.S. realm DS4P normative specification as an exemplar for an IG that could be used by other realms. The Office of the National Coordinator DS4P Implementation Guide (IG) will provide the core input into the HL7 DS4P IG project. This will entail: • Developing: o A U.S. profile of the DS4P content for email/XDM, SOAP/XDR and CDA transport. o Conformance statements and constraint mechanisms required for publication are included in the HL7 DS4P IG • Ensuring that: o The IG identifies the normative standards that it constrains, and a description of how the IG is compliant with its base normative standards o The US realm constrained IG is clearly derived from the current or updated ONC DS4P IG and IG derivatives per exchange architecture. o The IG includes adequate implementation guidance to developers o All IG non-HL7 standards (including vocabulary) are identified and any gaps addressed, e.g., as future harmonization proposals or as requests to appropriate SDOs o • Alignment with: o Other HL7 Security, CBCC, Structured Documents, and SOA Work Group standards is specified as appropriate, e.g., relationship to the:  Security Work Group HL7 Security and Privacy DAM and Healthcare Privacy and Security Classification System  CBCC Work Group Privacy Consent Directive and CDA R2 Implementation Guide DSTU/Normative  Structured Document Work Group CDA, CCDA, and where appropriate to CDA R3 as an emerging standard  SOA Work Group PASS artifacts o Applicable IHE standards in addition to the base XD* metadata and exchange protocols, such as ATNA and XUA o Applicable ONC Standards & Interoperability standards, such as Direct exchange protocol

See scope statement at http://gforge.hl7.org/gf/download/trackeritem/2634/10493/HL7PSSv20131DataSegmentationforPrivacy_WGApproved.doc.

Action Items

Back to Security Main Page