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

Difference between revisions of "HL7 FHIR Security 2017-10-03"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "==Call Logistics== Weekly: '''Tuesday at 05:00 EST''' (2 PM PST) Web conference desktop and VOIP https://www.freeconferencecall.com/join/security36 Online Meeting ID: secur...")
 
 
(One intermediate revision by the same user not shown)
Line 39: Line 39:
 
*Roll;  
 
*Roll;  
 
* approval of agenda  
 
* approval of agenda  
* approval of the [[HL7 FHIR Security 2017-9-26]] Minutes
+
* approval of the [[HL7 FHIR Security 2017-09-26]] Minutes
 
* All security open http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemBrowse&tracker_id=677&tracker_query_id=4967
 
* All security open http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemBrowse&tracker_id=677&tracker_query_id=4967
 
* Clarification that Resource.Identifier can hold ANY identifier even those that are not identifiers of FHIR Resources
 
* Clarification that Resource.Identifier can hold ANY identifier even those that are not identifiers of FHIR Resources
Line 58: Line 58:
  
 
=Minutes=
 
=Minutes=
 +
* John Chaired
 +
* Approval of last weeks minutes unanimous
 +
* Reviewed GF#11071 https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=11071
 +
** Try to create a valueset that is made up of the most used codes, not to imply that other codes are not used, just to focus discussion.
 +
*** Keep all Confidentiality codes as there are few and the are valuable
 +
*** PurposeOfUse -- Start with existing GeneralPurposeOfUse valueset, add HTEST, HQUALIMP, and LABELING
 +
*** Sensitivity - ETH, HIV, SDV, GDIS, PSY, SDV, SEX, and STD; ...
 +
**This is when we realized that there are differnet subsets that exist that are used in different ways. Some codes would appear on clinical data, but not on identity resources; where as others would only appear on identity resorurces and never appear on clinical data. And that those different uses are already valuesets, and FHIR already has catagorized FHIR.
 +
** See http://build.fhir.org/resourceguide.html
 +
* ACTION: Kathleen to start withthe FHIR resourceguide, put into WORD, and annotate with the existing HCS subsets that are appropriate for each, as discussed above.

Latest revision as of 21:51, 3 October 2017

Call Logistics

Weekly: Tuesday at 05:00 EST (2 PM PST)

Web conference desktop and VOIP https://www.freeconferencecall.com/join/security36 
Online Meeting ID: security36
Phone: +1 515-604-9567, Participant Code: 880898
 Please be aware that teleconference meetings are recorded to assist with creating the meeting minutes 

Back to HL7 FHIR security topics

Attendees

Member Name Member Name Member Name
x John Moehrke Security Co-Chair x Kathleen Connor Security Co-Chair . Alexander Mense Security Co-chair
. Suzanne Gonzales-Webb CBCC Co-Chair . Johnathan Coleman CBCC Co-Chair . Mike Davis
. Reed Gelzer RM-ES Lead . Glen Marshal x Joe Lamy
. Diana Proud-Madruga x Rob Horn . Beth Pumo
. Irina Connelly . Firstname Lastname . Firstname Lastname

Agenda

Minutes

  • John Chaired
  • Approval of last weeks minutes unanimous
  • Reviewed GF#11071 https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=11071
    • Try to create a valueset that is made up of the most used codes, not to imply that other codes are not used, just to focus discussion.
      • Keep all Confidentiality codes as there are few and the are valuable
      • PurposeOfUse -- Start with existing GeneralPurposeOfUse valueset, add HTEST, HQUALIMP, and LABELING
      • Sensitivity - ETH, HIV, SDV, GDIS, PSY, SDV, SEX, and STD; ...
    • This is when we realized that there are differnet subsets that exist that are used in different ways. Some codes would appear on clinical data, but not on identity resources; where as others would only appear on identity resorurces and never appear on clinical data. And that those different uses are already valuesets, and FHIR already has catagorized FHIR.
    • See http://build.fhir.org/resourceguide.html
  • ACTION: Kathleen to start withthe FHIR resourceguide, put into WORD, and annotate with the existing HCS subsets that are appropriate for each, as discussed above.