Difference between revisions of "ITI Minutes Feb 2016 Face to Face"

From IHE Wiki
Jump to navigation Jump to search
 
Line 1: Line 1:
='''DAY 3: Minutes Feb 17th'''=
 
 
=='''Participants:'''==
 
 
Elliot Silver (McKesson),
 
 
Gila Pike (Cognaissance),
 
 
Daniel Berenzeanu (Ready Computing),
 
 
John Moherke (GE Healthcare)
 
 
Raphael Oliveira (Porto Univeristy),
 
 
Nader Cheaib (Asìp Santè),
 
 
Sylvie Colas (Asip Santè),
 
 
Sensmeier Joyce (Himss),
 
 
Mauro Zanardini (consorzio Arsenàl.IT),
 
 
Jens Kristian Villadsen (Region Midtjylland),
 
 
Lynn Felhofer (ITI Tech Manager),
 
 
Rob Horn (AGFA Healthcare),
 
 
Tarik Idris (ICW),
 
 
Diana Warner (AHIMA),
 
 
Anna Orlova (AHIMA),
 
 
Harry Rhodes (AHIMA)
 
 
Michelle Williamson
 
 
Tone Southerland (Ready Computing)
 
 
Karen Altell
 
 
Randal Leggett
 
 
Jacklyn Bays
 
 
Christina Lachance (OPA)
 
 
Christina Fowler
 
 
Elliot Sloane (CHIRP)
 
 
=='''Minutes:'''==
 
 
-'''9:30am – 12:45am JOINT MEETING: QRPH – PCC – PHARMACY – ITI'''
 
 
[The minutes of the joint session can be found in the ftp site: ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Technical%20Cmte/Face%20to%20Face%20meetings/February2016/Joint%20meeting%20materials/]
 
 
 
-'''13:30am –APPC Tarik lead this session: goal of today is to review comments on use-cases.'''
 
 
 
All the use-cases drafted are analyzed and approved. An additional use-case, related to Patient management of the patient portal, will be added by Tarik by tomorrow.
 
 
 
Cmte would underline in the doc that mechanism to enforce access control decisions are out of scope. Appendix P is the place where all these topics belong. The Cmte would keep the scope of the profile limited in Consent creation and not address policies enforcement. 
 
 
 
Mauro asks for the creation of a new section in vol.1 that describes at high level all the attrbiutes that can be used in APPC to create structured policies, this request is added as an open issue.  Tarik is asked to add in Security Cons section  how to manage the existence of two Policy Privacy domains.
 
 
 
The goal for the Cmte is to have a stable vol.1 by the end of this week, so that we can cast a semi-formal vote on the profile.
 
 
 
-'''16:15- 17:00 De-id Gila lead the discussion.'''
 
 
A series of bi-weekly tconf is scheduled to proceed on public comment resolution:
 
 
Starting form Wednesday March 9th at 11:30 -13:30 CT.
 
 
The Cmte starts the review of comments received. 
 
 
'''WRAP-UP/HOMEWORK:'''
 
 
By tomorrow, Tarik asks the Cmte to read APPC profile v9 and focus the attention on:  Glossary, Concepts and Security Considerations sections. Those sections will be discussed tomorrow.
 
 
 
 
='''DAY 4: Minutes Feb 18th'''=
 
='''DAY 4: Minutes Feb 18th'''=
  

Latest revision as of 14:38, 23 February 2016

DAY 4: Minutes Feb 18th

Participants:

Elliot Silver (McKesson),

Gila Pike (Cognaissance),

Daniel Berenzeanu (Ready Computing),

John Moherke (GE Healthcare)

Raphael Oliveira (Porto Univeristy),

Nader Cheaib (Asìp Santè),

Sylvie Colas (Asip Santè),

Mauro Zanardini (consorzio Arsenàl.IT),

Jens Kristian Villadsen (Region Midtjylland),

Lynn Felhofer (ITI Tech Manager),

Rob Horn (AGFA Healthcare),

Tarik Idris (ICW),

Elliott Lavy (quadramed)

Diana Warner (AHIMA)

Harry Rhodes (AHIMA)

Bill Majuwrsky (NIST)

Karen Witting (Ready Computing)

Ben Levy (CorePoint Health),

Minutes:

- 9:30-10:00 FHIR DSTU2: discussion on the plan and on timeline for the publication of the new TI version of MHD, PIXm PDQm.

The cmte should take in consideration the following timeline:

  • Ready for ballot = X
  • Go out for ballot = X + 1 week
  • Return ballot =X + 4 weeks
  • Resolve ballot = X + 5 weeks
  • some days to have a cleaned version for publication (…6 weeks total for the entire process of re-publication).


-10:25am - 11:15am PIXm: Daniel leads the presentation.

PIXm is revised by the Cmte. Elliot Silver move the motion to approve PIXm as ready for the ballot, John Moherke seconded it, no abstensions MOTION APPROVED

This version is available in the FTP site:

[ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr14-2016-2017/Technical%20Cmte/Workitems/DSTU2updates/PIXm-working-area/IHE_ITI_Suppl_PIXm_Rev1.1_TI_20160218b_approved.docx ]

-11:15am- 12:30 Dicussion on APPC: Tarik Leads the discussion

Review of the glossary.

Review of the View option defined for the Content Consumer actor.


Concept still need some work but probably vol.3 stuff can affect this section. Suggestion give 45 minutes more to formalize issues and questions related to that section.

13:35 MHD john leads the discussion:

The Cmte reviews the document , some transactional documentation is moved from vol2 to Appendix Z due to their reusability.

-John move to approve MHD PDQm Appendix Z, Rob second it. Approved.

-14:30: Move to APPC to schedule tconf

A bi-weekly call is defined. That serie of calls, starts form 22th February for bi-weekfly call ( APPC 8:00-9:30 CT.)

-15:00 AHIMA report of ongoing activities.

http://wiki.ihe.net/index.php?title=HIT_Standards_for_HIM_Practices-2016#Project_Description

wiki page for ongoing AHIMA work.

-15:10 – APPC read new use-case. Tarik lead. The content of Security Considerations Secction.

-16:15 CP discussion

  • CP-553: Delete Doc from Repository. Bill asks the cmte to have a direction on this: decide to go forward or stop the work on it. The cmte decides to move forward on this topic.
  • CP-799: Bill submits a proposal to address the issue of patientId merge with MU and a new option (so that we are not invalidating “magic” implementations that already do the merge in legacy ways).

The CP is split by the Cmte in two CPs:

    • SubmissionSet clarification and removing the immutability concept --> COMPLETED
    • A second CP that defines the formal approach to manage the merge of Patient Ids using MU will be drafted later.

Both the Cps are in charge to Bill. The Cmte asks Bill to work on CP-799 with higher priority.

-17:30 - 18:00: ITI-41 , ITI-42 Re-documentation

The cmte refines the decision taken about ITI-41 ITI-2 re-documentation:

Vol 1, 2b , 2x, 3 will be published after EU Connect-a-thon. CPs already balloted at the end of the CAT will be not integrated at that time in the spec. Charles/Karen will define a message to sent out when the new version of TF will be published, underlining that technical requirements are unchanged at all.