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

Difference between revisions of "November 13, 2018 Security Conference Call"

From HL7Wiki
Jump to navigation Jump to search
 
Line 56: Line 56:
  
 
'''Meeting Minute Approval''' - November 6, 2018
 
'''Meeting Minute Approval''' - November 6, 2018
* (Motion to approvle (Suzanne/Kathleen): Vote: objections/abstentions: none;  
+
* (Motion to approve (Suzanne/Kathleen): Vote: objections/abstentions: none;  
 
((Suzanne to add harmonization proposal link))
 
((Suzanne to add harmonization proposal link))
  
  
 
'''Update on PASS Audit reconciliation
 
'''Update on PASS Audit reconciliation
* last understood was that reconciliation comments were completed and we could ask for withdrawal
+
* last understood was that reconciliation comments were completed, and we could ask for withdrawal
 
* Kathleen brought up that Bernd B wants to see corrections in the document before he withdrawals
 
* Kathleen brought up that Bernd B wants to see corrections in the document before he withdrawals
 
** as far as Mike is concerned we should push forward and request withdrawal of negative
 
** as far as Mike is concerned we should push forward and request withdrawal of negative
* e-mail from LynnL; there was materialdue in order to allot TF4FA; she has listed that one and two have not been publsished?  was this a new requirement...Kathleen asked if this was a new rule? which could be a show stopper...
+
* e-mail from Lynn Laakso; there was material due in order to ballot TF4FA; she has listed that one and two have not been published?  was this a new requirement...Kathleen asked if this was a new rule? which could be a show stopper...
 
** we will wait and see what her answer is before proceeding. Current answer is we don't know.
 
** we will wait and see what her answer is before proceeding. Current answer is we don't know.
  
 
'''Harmonization codes
 
'''Harmonization codes
* all three proposals were approved; kathleen is deferring the codes that were not completed to next harmonization
+
* all three proposals were approved; Kathleen is deferring the codes that were not completed to next harmonization
 
* policy codes have been brought into v2
 
* policy codes have been brought into v2
 
* next harmonization  
 
* next harmonization  
* there were changes in the xx ballot to update confidentidential
+
* there were changes in the xx ballot to update confidentiality
  
 
V2.9 HL7 access proposal
 
V2.9 HL7 access proposal
 
* in chapter 4; want clarification.  security labels content is different than found in orders
 
* in chapter 4; want clarification.  security labels content is different than found in orders
* two sections which are talking about kind of labs--they were using vocabulary that was close to vocab in v3; which we changed years ago because of a mix of sensitivity and confidentializty--kathleen proposes that the codes be retired
+
* two sections which are talking about kind of labs--they were using vocabulary that was close to vocab in v3; which we changed years ago because of a mix of sensitivity and confidentiality--Kathleen proposes that the codes be retired
* recommentions is that they use the ARV segment be used which can point to any part of the lab order for results--removing table from both segements where they currently occur; avoiding conflict, note this is not a controversial issue...strictly clean-up.  Riki Merrick is trying to get into OO agenda to get in publishing of v2.9 clean-up
+
* recommendation is that they use the ARV segment be used which can point to any part of the lab order for results--removing table from both segments where they currently occur; avoiding conflict, note this is not a controversial issue...strictly clean-up.  Rikki Merrick is trying to get into OO agenda to get in publishing of v2.9 clean-up
  
* question on harmoanization - MIke.. this is a vocabulary--where does hl7 specifcy where these marking are optional or mandatory?... <Kathleen response> no, there is a specific policy; it says what is in the law; so its still an intepretaiton of the law.  
+
* question on harmonization – (Mike) this is a vocabulary--where does Hl7 specify where these marking are optional or mandatory?... <Kathleen response> no, there is a specific policy; it says what is in the law; so, it’s still an interpretation of the law.  
**mike - part of the law 7332; has to do with what we've determined are the handling instructions... HII of the law; he has it from the legal folks, that their interepations that ist a requirement on the receipient not of the VA--or to tell them that such a restriction exists
+
**mike - part of the law 7332; has to do with what we've determined are the handling instructions... HII of the law; he has it from the legal folks, that their interpretations that its a requirement on the recipient not of the VA--or to tell them that such a restriction exists
**if 7332 hadn't been speifieid for just health; there is something in the law (if specified)… then  
+
**if 7332 hadn't been specified for just health; there is something in the law (if specified)… then  
 
(listen to recording)
 
(listen to recording)
** in otherwords its up to the implementer to decide on the lange
+
** in other words, it’s up to the implementer to decide on the language
  
  
 
HL7 2 to FHIR PSS'''
 
HL7 2 to FHIR PSS'''
* standares approach mapping from v2 to FHIR
+
* standards approach mapping from v2 to FHIR
* each on eof the datatypes;
+
* each of the datatypes;
* effort is underway (QOweek); the mapping between chapter 9 con segment and the fhir concent and contract
+
* effort is underway (meetings every other week); the mapping between chapter 9 con segment and the FHIR consent and contract
** in particular important in regard to the transform; having capapbility from going from one set to another.. i.e. get get transform set into FHIR (confirm)
+
** important in regard to the transform; having capability from going from one set to another. i.e. get transform set into FHIR (confirm)
  
  
Line 101: Line 101:
 
* current build is frozen
 
* current build is frozen
 
* because of HIMSS several subjects are up in the air
 
* because of HIMSS several subjects are up in the air
* September care pallnning are not going to be at himmss--and not be at the January WGM--this will lower about ability to move with security and consent--we will still be able to do work with break glass
+
* September care planning are not going to be at HIMSS--and not be at the January WGM--this will lower about ability to move with security and consent--we will still be able to do work with break glass
  
  
Line 107: Line 107:
 
additional agenda items?
 
additional agenda items?
  
NOne
+
None
  
Motion t adjorn (Kathleen)
+
Motion t adjourn (Kathleen)
 
Meeting adjourned at 1320 Arizona Time  --[[User:Suzannegw|Suzannegw]] ([[User talk:Suzannegw|talk]]) 15:20, 13 November 2018 (EST)
 
Meeting adjourned at 1320 Arizona Time  --[[User:Suzannegw|Suzannegw]] ([[User talk:Suzannegw|talk]]) 15:20, 13 November 2018 (EST)
 
Temporary Recording: https:fccdl.in/yN1FTQeUV
 
Temporary Recording: https:fccdl.in/yN1FTQeUV

Latest revision as of 20:53, 13 November 2018

Back to Security Main Page

Attendees

Back to Security Main Page

x Member Name x Member Name x Member Name x Member Name
. John Moehrke Security Co-chair x Kathleen Connor Security Co-chair x Alexander Mense Security Co-chair . Trish Williams Security Co-chair
x Christopher Shawn Security Co-chair x Suzanne Gonzales-Webb x Mike Davis . David Staggs
x Diana Proud-Madruga . Johnathan Coleman x Francisco Jauregui x Joe Lamy
. Theresa Ardal Connor . Greg Linden . Grahame Grieve x Dave Silver
. x Beth Pumo . Jim Kretz . Peter Bachman x Peter VanLiesdonk]

Back to Security Main Page

Agenda

  1. (2 min) Roll Call, Agenda Approval
  2. (5 min) Review and Approval of Minutes November 6, 2018
  3. (5 min) Update on revision of PASS Audit - Is reconciliation spreadsheet ready for upload? - Mike
  4. (5 min) Security Harmonization proposal codes approved Some value sets will be proposed in March - Kathleen
  5. (5 min) v2.9 Change Request related to Confidentiality codes - Kathleen
  6. (5 min) HL7 v2 to FHIR PSS, v2 to FHIR Spreadsheet for Security - Kathleen
  7. (5 min) GDPR whitepaper on FHIR Update, reminder of new call schedule - Alex
  8. (5 min) FHIR Security call update - John

Back to Security Main Page

Meeting Minutes

Meeting Chair - Chris Shawn

Meeting Minute Approval - November 6, 2018

  • (Motion to approve (Suzanne/Kathleen): Vote: objections/abstentions: none;

((Suzanne to add harmonization proposal link))


Update on PASS Audit reconciliation

  • last understood was that reconciliation comments were completed, and we could ask for withdrawal
  • Kathleen brought up that Bernd B wants to see corrections in the document before he withdrawals
    • as far as Mike is concerned we should push forward and request withdrawal of negative
  • e-mail from Lynn Laakso; there was material due in order to ballot TF4FA; she has listed that one and two have not been published? was this a new requirement...Kathleen asked if this was a new rule? which could be a show stopper...
    • we will wait and see what her answer is before proceeding. Current answer is we don't know.

Harmonization codes

  • all three proposals were approved; Kathleen is deferring the codes that were not completed to next harmonization
  • policy codes have been brought into v2
  • next harmonization
  • there were changes in the xx ballot to update confidentiality

V2.9 HL7 access proposal

  • in chapter 4; want clarification. security labels content is different than found in orders
  • two sections which are talking about kind of labs--they were using vocabulary that was close to vocab in v3; which we changed years ago because of a mix of sensitivity and confidentiality--Kathleen proposes that the codes be retired
  • recommendation is that they use the ARV segment be used which can point to any part of the lab order for results--removing table from both segments where they currently occur; avoiding conflict, note this is not a controversial issue...strictly clean-up. Rikki Merrick is trying to get into OO agenda to get in publishing of v2.9 clean-up
  • question on harmonization – (Mike) this is a vocabulary--where does Hl7 specify where these marking are optional or mandatory?... <Kathleen response> no, there is a specific policy; it says what is in the law; so, it’s still an interpretation of the law.
    • mike - part of the law 7332; has to do with what we've determined are the handling instructions... HII of the law; he has it from the legal folks, that their interpretations that its a requirement on the recipient not of the VA--or to tell them that such a restriction exists
    • if 7332 hadn't been specified for just health; there is something in the law (if specified)… then

(listen to recording)

    • in other words, it’s up to the implementer to decide on the language


HL7 2 to FHIR PSS

  • standards approach mapping from v2 to FHIR
  • each of the datatypes;
  • effort is underway (meetings every other week); the mapping between chapter 9 con segment and the FHIR consent and contract
    • important in regard to the transform; having capability from going from one set to another. i.e. get transform set into FHIR (confirm)


GDPR whitepaper

  • no meeting this week
  • next meeting is 11/19 - noon (Monday)


FHIR Security call update

  • Short call today; went over v2 FHIR
  • current build is frozen
  • because of HIMSS several subjects are up in the air
  • September care planning are not going to be at HIMSS--and not be at the January WGM--this will lower about ability to move with security and consent--we will still be able to do work with break glass


additional agenda items?

None

Motion t adjourn (Kathleen) Meeting adjourned at 1320 Arizona Time --Suzannegw (talk) 15:20, 13 November 2018 (EST) Temporary Recording: https:fccdl.in/yN1FTQeUV


Back to Security Main Page