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

Difference between revisions of "HL7 WGM Jan 2017, San Antonio"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "=='''DRAFT''' 2016 September Working Group Meeting - Baltimore, Maryland - SOA WORKING GROUP== * [http://www.hl7.org/events/wgm092016/ HL7 WGM EVENT Page Link] * [<<add link>...")
 
 
(87 intermediate revisions by the same user not shown)
Line 1: Line 1:
=='''DRAFT''' 2016 September Working Group Meeting - Baltimore, Maryland - SOA WORKING GROUP==
+
=='''DRAFT''' 2017 January Working Group Meeting - San Antonio, TX - SOA WORKING GROUP==
  
* [http://www.hl7.org/events/wgm092016/ HL7 WGM EVENT Page Link]
+
* [http://www.hl7.org/events/wgm012017/ HL7 WGM EVENT Page Link]
* [<<add link>> On-Site Meeting Schedule ]   
+
* [http://www.hl7.org/documentcenter/public_temp_64AB3AC5-1C23-BA17-0CA34A5DC5C46470/calendarofevents/SanAntonio_Onsite_web.pdf On-Site Meeting Schedule ]   
*[http://www.hl7.org/documentcenter/public_temp_2D3C0EED-1C23-BA17-0CA2F4FECDE73282/brochures/wgm/HL7_WGM_20160728.pdf  BROCHURE Link]
+
*[http://www.hl7.org/documentcenter/public_temp_5E287B90-1C23-BA17-0CA69A7139F50595/brochures/wgm/HL7_WGM_20161115.pdf  BROCHURE Link]
  
 
===Service Oriented Architecture (SOA) WORKING GROUP SESSIONS===
 
===Service Oriented Architecture (SOA) WORKING GROUP SESSIONS===
Line 30: Line 30:
 
|-
 
|-
 
|-valign="top" style="background:#f0f0f0;"
 
|-valign="top" style="background:#f0f0f0;"
| SUN||MAY 08||Q1|| 9:00-10:30||No Meeting||.||
+
| SUN||JAN 15||Q1|| 9:00-10:30||No Meeting||.||
 
|-
 
|-
 
|-valign="top" style="background:#f0f0f0;"
 
|-valign="top" style="background:#f0f0f0;"
Line 42: Line 42:
 
|-
 
|-
  
| MON||SEP 19||Q1|| 9:00-10:30||No Meeting ||.||
+
| MON||JAN 16||Q1|| 9:00-10:30||No Meeting ||.||
 
|-
 
|-
 
| ||||Q2||11:00-12:30||No Meeting||.||
 
| ||||Q2||11:00-12:30||No Meeting||.||
Line 50: Line 50:
 
* Provides overview of the workgroup, mission, charter, objectives, current work, etc.  
 
* Provides overview of the workgroup, mission, charter, objectives, current work, etc.  
 
* Intended for all audiences.
 
* Intended for all audiences.
||SOA||Guest Room 317
+
* Review of new HSSP Process Document (if time allows)
 +
||SOA||Regency East #2
 
|-
 
|-
 
|-valign="top"
 
|-valign="top"
Line 69: Line 70:
 
*Scheduling/Resource Management Service
 
*Scheduling/Resource Management Service
  
||SOA||Guest Room 317
+
||SOA||Regency East #2
 
|-
 
|-
 
|-valign="top"
 
|-valign="top"
 
|-valign="top" style="background:#f0f0f0;"
 
|-valign="top" style="background:#f0f0f0;"
|  TUE||SEP 20||Q1|| 9:00-10:30||'''Joint With FHIR Infrastructure''' (confirmed)
+
|  TUE||JAN 17||Q1|| 9:00-10:30||'''Joint With FHIR Infrastructure''' (confirmed)
 
*SOA specification within FHIR
 
*SOA specification within FHIR
  
||SOA||Guest Room 317
+
||SOA||Chula Vista
 
|-
 
|-
 
|-valign="top"
 
|-valign="top"
 
|-valign="top" style="background:#f0f0f0;"
 
|-valign="top" style="background:#f0f0f0;"
| ||||Q2||11:00-12:30|| '''Joint w/ Patient Care''' (Confirmed)
+
| ||||Q2||11:00-12:30|| '''Joint w/ Patient Care and Patient Administration''' (Confirmed)
 
*Care Coordination Discussion
 
*Care Coordination Discussion
 +
*Scheduling Service Discussion
 +
*Other items of interest to SOA, PC, and PA
  
 
||SOA
 
||SOA
||Guest Room 317
+
||Chula Vista
 
|-
 
|-
 
|-valign="top"
 
|-valign="top"
 
|-valign="top" style="background:#f0f0f0;"
 
|-valign="top" style="background:#f0f0f0;"
 
| ||||Q3||1:45-3:00|| '''Patient Administration''' (Confirmed)
 
| ||||Q3||1:45-3:00|| '''Patient Administration''' (Confirmed)
*Scheduling Service Discussion
+
*Scheduling Service Work Session
||SOA||Guest Room 317
+
||SOA||Chula Vista
 
|-
 
|-
 
|-valign="top"
 
|-valign="top"
 
|-valign="top" style="background:#f0f0f0;"
 
|-valign="top" style="background:#f0f0f0;"
| ||||Q4||3:30 - 5:00|| '''Ordering Service and X-Paradigm Interop Discussions'''
+
| ||||Q4||3:30 - 5:00|| '''Ordering Service Work Session'''
*Ordering Service Discussion
+
*Walkthrough of ordering service technical specification work,
**Walkthrough of ordering service technical specification work,
+
*Relationship to FHIR workflow activities,
**relationship to FHIR workflow activities, and
+
*State of OMG submissions,
**state of OMG submissions
+
*Review and contribute to current documents
*X-Paradigm Interoperability Project Discussion
+
 
**TBD
+
||SOA||Chula Vista
||SOA||Guest Room 317
 
 
|-
 
|-
 
|-valign="top"
 
|-valign="top"
 
|-valign="top" style="background:#f0f0f0;"
 
|-valign="top" style="background:#f0f0f0;"
| ||||Q5|| Birds of a Feather ||
+
| ||||Q5|| Open Source Birds of a Feather ||  
*Open Source
+
* Kick off and chartering of the new work group
|| || Baltimore
+
* One of the initial projects will be to realize implementation of HSSP services as part of an HSPC platform implementation project.
 +
 
 +
|| SOA ||Rio Grande Center
 
|-valign="top"
 
|-valign="top"
| WED||SEP 21||Q1|| 9:00-10:30 Split meeting||
+
| WED||JAN 18||Q1|| 9:00-10:30 Split meeting||
  
 
'''1. Joint w/EHR, Security, CBCC, SOA, FHIR'''
 
'''1. Joint w/EHR, Security, CBCC, SOA, FHIR'''
Line 115: Line 119:
 
________________________
 
________________________
  
'''2. Scheduling Service Continuing discussion'''
+
'''2. Scheduling Service Continuing discussion (?)'''
 
*TBD
 
*TBD
  
  
||SOA
 
 
||
 
||
*Constellation C
+
*EHR
*Guest Room 317
+
*SOA
 +
||
 +
*Rio Grande East
 +
*Live Oak
 
|-
 
|-
  
 
|-valign="top"
 
|-valign="top"
| ||||Q2|| 11:00-12:30|| '''Joint w/Security''' (confirmed)
+
| ||||Q2|| 11:00-12:30|| '''Joint w/Security and CBCC''' (confirmed)
 
*Joint SOA/Security Projects and concerns.
 
*Joint SOA/Security Projects and concerns.
**PASS ACS vote to request publication
+
**Projects of joint concern (TBD)
**HL7 Cloud Planning Guide Overview
+
**SLS PSS
**PASS Audit
+
**PASS Audit Ballot Reconciliation
 +
***Provenance and Audit
 +
****Expand scope to include provenance. and/or
 +
****Do a connectathon for audit & provenance leading to an implementation guide?
  
||SOA||Frederick
+
||SOA||Live Oak
 +
|-
 +
|-valign="top"
 +
| ||||Q3||1:45 -3:00|| HSSP Reference Architecture or Cloud Planning Work Session
 +
* TBD
 +
||SOA|| Live Oak
 
|-
 
|-
 
|-valign="top"
 
|-valign="top"
| ||||Q3 / Q4||1:45 -3:00 / 3:30 -5:00|| '''Refresh of Service Functional Model specification process in the world of FHIR.'''
+
| ||||Q4||3:30 -5:00|| Cloud Planning Work Session
* The current Service specification process involves both HL7 and OMG and generally defers technical implementation until further in the process.  Given the energy around FHIR and the potential for lost opportunity to impact FHIR, this discussion will revisit our approach to determine better ways to align with and engage FHIR activities synergistically with SOA efforts.
+
* TBD
 
+
||SOA|| Live Oak
||SOA||
 
* Pisces
 
* Guest Room 317
 
 
 
 
|-
 
|-
 
|-valign="top"
 
|-valign="top"
 
|-valign="top" style="background:#f0f0f0;"
 
|-valign="top" style="background:#f0f0f0;"
|  THU||SEP 22||Q1|| 9:00-10:30|| '''HL7 Cloud Planning Guide Work session'''
+
|  THU||JAN 19||Q1|| 9:00-10:30|| Co-chair meeting?
* Presentation on Amazon Web Services by Zachary Huy.
+
* Administrative issues
* Cloud Planning Guide Survey
+
|| SOA ||Live Oak
* Develop a Cloud blueprint sample
 
* Flesh out draft document
 
|| SOA ||Guest Room 317
 
 
|-
 
|-
 
|-valign="top" style="background:#f0f0f0;"
 
|-valign="top" style="background:#f0f0f0;"
 
|-valign="top" style="background:#f0f0f0;"
 
|-valign="top" style="background:#f0f0f0;"
| ||||Q2||11:00-12:30|| '''Hot Topics'''
+
| ||||Q2||11:00-12:30|| TBD
 
*TBD   
 
*TBD   
||SOA||Guest Room 317
+
||SOA|| Live Oak
 
|-
 
|-
  
Line 167: Line 174:
 
|-
 
|-
  
|  FRI||SEP 23||Q1|| 9:00-10:30||No Meeting||.||
+
|  FRI||JAN 20||Q1|| 9:00-10:30||No Meeting||.||
 
|-
 
|-
  
Line 193: Line 200:
  
 
==MON Q3==
 
==MON Q3==
  - attendees:
+
  - See Attendees Section below
 
#Workgroup Overview / HSSP Intro / New Attendee "Jumpstart"   
 
#Workgroup Overview / HSSP Intro / New Attendee "Jumpstart"   
 
#* Provides overview of the workgroup, mission, charter, objectives, current work, etc.
 
#* Provides overview of the workgroup, mission, charter, objectives, current work, etc.
 
All of the attendees were already familiar and active in SOA so we opened the floor to anyone who wanted to share about what they are involved with.
 
 
Jerry Goodnough:
 
Discussion revolved around changes happening to Pub/sub. As far as Jerry knows, no one on Patient Care who goes to OMG also attends HL7.
 
Ordering Service - October 7 initial submission but likely will end up slipping that entry.
 
Models are on HSBC.
 
 
Diana brought up the question regarding attendance at SOA All hands meetings
 
 
Ken: HSPC has agreed to own the project.
 
 
Vadim, Jerry, and Preston are planning to meet to discuss (what Ken introduced).
 
 
Vadim: Need to identify use cases which would lead to implementation guides.
 
 
 
We have 2 quarters this week looking at the HSSP/OMG process with HL7. Graham will be joining us Q4 Wed.
 
 
Right now it's a bit waterfall. Graham would like to see it more Agile.
 
 
Talking about FHIR-I joint meeting: What do we want that meeting agenda to consist of?
 
  
 
==Mon Q4==
 
==Mon Q4==
  - attendees: 10
+
  - See Attendees Section below
# Welcome and Introductions: Went around and introduced ourselves
+
# Welcome and Introductions:  
# Agenda Review, approval 10 attendees: Passed unanimously
+
# Agenda Review
 +
# Review and approval of previous WGM minutes
 
# Round Robin updates
 
# Round Robin updates
#*New HSSP cover page: Vincent displayed the new cover page on the HSSP.
+
#*PASS Access Control: Publication package complete. Waiting on confirmation from ANSI that spec has been published.
#*PASS Access Control: Diana - Ballot reconciliation package has been uploaded. Will vote on to bring this to publication this week.
+
#*PASS Audit: Ballot complete.  
#*PASS Audit: resurrecting the previous effort. Using all previous work and comments. Will bring this to ballot in January 2017.
+
#*Clinical Decision Support on FHIR:  
#*Clinical Decision Support on FHIR: (Claude not present) Manoj - Connectathon. Leveraged work on Decision Support Model work. CDS Hook is geared toward integration into the EMR. Claude is trying to establish an ongoing CDS FHIR connectathon every two weeks for CDS. Goal is to get the cycles going faster. CDS on FHIR is a methodology and series of resources for pulling information to support a CDS. This supports all CDS use cases.
+
#*Cross-Paradigm Interoperability Project Update: Work is complete. Stefano to follow-up on reconciliation package and publication.
#*Cross-Paradigm Interoperability Project Update: Ken Lord - all the objections in ballot have been addressed and resolved. Ballot reconciliation package has been updated. This was an informative ballot. Australia has been using this as well as folks in the US. Implementation guide is in 2 part, behavioral and informational (MDMI). On the MDMI, did information exchange using open source tools. Have had multiple implementations on the informational (MDMI) side of this guide. Expect to go into some pilots with some HIEs in the short term. Working with FHIM, VPR, DES among others. VA, as part of standards and interop, knowledge-based services (Ken Rubin). Australia has shown interest in MDMI and MDHT. Question: where do we go from here? Maybe provide some information on the HSSP website? This is an OMG standard.  
+
#*Coordination of Care Service - Tech Spec Status: Next submission date is set for mid-February and will be reviewed in March. Looking at late 2017 for the adoption of the technical spec.
#*Coordination of Care Service - Tech Spec Status: Emma - collaboration between patient care and SOA. Been through the STU phases and in the process of getting the FM published. Finishing up the publication request. Will submit the pub request this week. FM is based on the care plan DAM.  
+
#*Ordering Service: Initial submission happened in Dec 2016. Revised submission will happen in Feb 2017.
#*Ordering Service - Jerry - RFP Update: Currently at OMG. Letters of intent period has closed but don't know who has actually submitted a letter of intent. Initial sub is in Nov 7. Final submission date targeted for March but will likely slip to September. HL7 members are entitled to participate in OMG activities. May have some implementation by mid 2017.
+
#*HL7 Cloud Planning Guide Document: Reviewing the PSS and making sure that the scope makes sense for HL7 to publish. Looking at possibly coordinating with HSPC. Will vote on the joint proposal Wed Q3. Will put in an NIB for May 2017.  
#*Event Notification/Escalation Service: EPS and Unified Communication Service? Jerry isn't sure what is meant by this.
+
#*Pub/Sub Service: Still need to review with OMG. Move forward with the STU extension. Action to be taken by Emory.
#*HL7 Cloud Planning Guide Document: Vadim - Market need to identify resources for a Cloud Service. Next step is to break it down and start writing a draft blueprint.
+
#*Unified Communications Service: Write up an RFC (to be decided this quarter). Moving forward with the STU extension. Action to be taken by Emory.
#*Pub/Sub Service: Reference implementation is still at OMG. Published. Good until Feb 2017. At the September 2016 meeting, review DSTU comments and see if ready to proceed to Normative in Jan 2017 or if more time is needed to implement before publishing then request DSTU extension in Jan 2017 meeting.
+
#*FHIR Connect-a-thon: General purpose guidance for Clinical Reasoning Module. Had several participants. Scenario: Apply an order template for a specific patient. FHIR clinical reasoning CDS Service for Zika infection management. Created a clinical reasoning decision artifact. Incorporated in the an end-user experience Epic implementation that can return recommendations. [http://wiki.hl7.org/index.php?title=File:Connectathon_14_-_Clinical_Reasoning_Track_Report.pptx Click here] for full presentation.  
#*Unified Communications Service: Published. Good until Feb 2017. At the September 2016 meeting, review DSTU comments and see if ready to proceed to Normative in Jan 2017 or if more time is needed to implement before publishing then request DSTU extension in Jan 2017 meeting.  
+
#*HSSP Process Guide (SOA on FHIR): Ken wrote up a document, "HSSP Standards Development Process" to outline how to incorporate FHIR into SOA specifications as well as update the overall HSSP process. Detailed discussion will continue Tuesday Q1.
#*FHIR Connect-a-thon: See CDS - FHIR Scheduling resources - need to align with the Scheduling service. Ordering Service have a lot of behavioral components that aren't currently in FHIR. Clause was also integrating the Unified Communications Service with FHIR but not successful yet.
+
#*Scheduling/Resource Management Service:  
#*SOA on FHIR: This is going to be Q3-4 on Wednesday. Have some concrete proposals based on discussions between Graham and Ken.
+
#*All Hands meeting schedule and attendance:
#*Scheduling/Resource Management Service: Have a draft PSS. Will be finalizing this during the WGM.
 
#*All Hands meeting schedule and attendance: General consensus that we move to once a month, status update meeting. Other business to be discussed after the status updates as needed.
 
  
 
==TUE Q1==
 
==TUE Q1==
  - attendees: 12
+
  - See Attendees Section below
 
#Joint With FHIR Infrastructure (confirmed)  
 
#Joint With FHIR Infrastructure (confirmed)  
#*SOA specification within FHIR: Claude: Connectathon brief. Were able to connect the careweb into the HAPI JPA server, EPS, and CDS Manager. Ran into problems with the connection to the UCS. Claude did a short demo as much as he could but one of the servers that he needed wasn't available. Discussion on solutions to problem encountered.
+
#*SOA specification within FHIR:  
The SOA specification pre-dated FHIR. Question is how we bridge that gap?
+
#**Began by re-capping what was done at the last WGM. Went through the [http://wiki.hl7.org/index.php?title=File:SOA-FHIR_Process_v2.pptx SOA-FHIR Process PPT.]
Question are we creating APIs that can interface with FHIR or do we create FHIR APIs.
+
#**CDS is blazing the trail. Looking at Ordering service and Scheduling service to actually test the process as outlined in the document. Targeting FHIR STU 4 for incorporating FHIR into these standards.  
How do we bring the two worlds together?
+
#**Another standard which may be incorporating a FHIR section is PASS SLS.
How do you make the bridge btwn functional and behavioral?
+
#**Ken shared the HSSP process document. Sean - have we reviewed any of the FHIR IGs? Ken - no but it is on our radar. Joshua - Tool is IG publisher, the US Core IG would be the place to start. Joshua likes the requirement for implementation in the OMG process. The IG publisher tool is available on the FHIR webpage.
Vadim: Is there a conflict in the first place? The question is really one of design process? Because of our relationship with OMG, we are in the unusual position of implementation being ahead of development. 2 possible approaches:
 
# Use FHIR only as payload
 
# Use FHIR as the data end
 
  
 +
Joshua - is there a group that we can point to who will be implementing this process.
 +
Ken - in theory, Scheduling will be doing this. They are very open to doing this process.
 +
Joshua - Good. This is the first we've heard of this type of process being implemented.
 +
Don - Are there any other projects that are doing this and are there any projects that FHIR is aware of that would fit this model?
 +
Joshua - The main one that came to my mind was Scheduling so I'm glad to hear that is happening.
 +
Ken - CDS on FHIR is fairly mature already but they may bring some in retroactively.
  
looking at the order service and the order resource in FHIR, what is the relationship. Jerry: simple question without a simple answer.
+
Ken - under this process the SFM doesn't go away. Provides a bridge with what we do today. We want to make sure that as we do new services, they fit well with the existing specs.
Ken: how do we get consistent behavior across different implementations? Vince: FHIR spec of operations should do that.  
 
Discussion on possible solutions led to the conclusion that we may need to create an implementation guide for a specific service, such as scheduling service.
 
Need to figure out how this implementation guide would fit into the OMG process.
 
How do we move from waterfall to more Agile in developing SOA spec. Right now you need to have a completed STU before moving into the OMG process. We want to move to some parallel development of STU, FHIR resources, and OMG project.
 
  
Work these questions in the CDS project.
+
Specific actions: Ken would like a peer review of this process document from a FHIR perspective. Who would be willing to do this?
  
 +
'''Action Item''' Joshua - Lloyd put out an email asking if folks need help. If that doesn't result in a good response, then I am willing to do the review.
 +
Ken - That is good for the process doc review. Another issue is how to do the 6 objectives that would be consistent for all SOA specifications (such as naming conventions, etc...). What would that look like.
 +
 +
'''Action Item''' - Ken to send a note to Joshua(?) or the FHIR Infrastructure for help in creating SOA specific templates.
  
Catalog service: If trying to do CDS that is evidence based, difficult to do this because of different vocabularies in different systems. The catalog service helps to keep all catalogs in sync. This includes vocab and bindings/constraints associated as well as the ability to constrain using context.
+
Timeframe? Joshua - probably after STU 3.  
 
+
Ken - Since Bryn put his hand up, that may be fine.  
We will have a joint meeting between SOA and FHIR-I at the January WGM. Diana will make that invitation.
+
Diana - hopefully we can get some feedback on the process document.
 
 
'''Notes from Vince:'''
 
*FHIR Foundation – Implementation support FHIR.org
 
*CDS on FHIR using OpenCDS – see slides
 
*Using Event Pub/sub called from FHIR which triggers CDS – output via Universal Communication service (UCS)
 
*Mechanism to hook to FHIR – Either a “bespoke” hook imbedded in the server (an interceptor) or add a front end to pub/sub service that implements the FHIR Subscription resource
 
 
 
Proposal:
 
*Use the FHIR Operations concept to define FHIR resources that are Service inputs and outputs and define a set of operations that SOA manages with specified operation names.
 
*A typical Service would require 3 or 4 operations – use CDS as the guinea pig (maybe Human Services directory also – Brian to discuss) where being used for the current catalogue service.
 
  
Note Thursday Q1 O+O, PC, CDS will discuss the catalogue
+
[http://wiki.hl7.org/index.php?title=File:2016_HSSP_Standards_Development_Process_v1.03.docx HSSP Process Document]
  
 
==TUE Q2==
 
==TUE Q2==
  - attendees:
+
  - See Attendees Section below
#Joint w/ Patient Care (Confirmed)
+
#Changed from Joint with Patient Care to Reference Architecture discussion.
#*Scheduling Service: Update - Working on the PSS which will be distributed to Patient Care to be a co-sponsor. This is a PA sponsored project.  
+
Need to flesh out the RA to make it useable.  
#*Care Coordination Service SFM -
 
#*Care Coordination Service Publication - Laura H.: Missed publication date. Working on the publication request. Will send the publication request to Ken and cc Diana in order to finish the request.
 
#*Care Plan - (See notes from Vince below)
 
 
 
Care plan: Emma will send Diana a link to information on this.
 
 
Ken is an OMG Co-chair which makes it difficult for him to be directly involved on any OMG submissions.
 
Ken described the OMG process. The important part is that we come through this process with something that Patient care is willing to accept (ie: any deviation from the STU is understood and accepted).
 
  
Mega-Joint meetings: Early in week having joint meetings with multiple WGs so that only go through the slides once.
+
Can we visualize this starting with the FHIR workflow and then identify the differences when approaching from an SOA point of view.  
  
Next steps:
+
'''Action Item''' - Need to add Orchestration Service and Workflow service to the diagram.
* Continue having a joint meeting (ambassador coming from Patient Care). Make it a three-way joint between Patient Care, SOA, and Patient Administration? Approach Brian (PA co-chair) to see if this consolidation proposal will work.
 
* Patient Care is contemplating having a quarter that is all care plan/care coordination. Targeting Thurs Q1 for this.
 
* Laura has action to send publication request to Ken.
 
* Ken has action item to send PSS for scheduling service to PC.
 
* Ken to get to clarity with Wayne on the HL7 vote to OMG on Care Coordination.
 
* Patient Care has expressed interest in scheduling service as a possible co-sponsor.
 
* If aware of other folks with interest in care plan resources and bring them to OMG's attention.
 
  
12:15 - Adjourned the Patient Care meeting.
+
Did a preliminary sequence diagram for the RA.
  
New discussion - SOA Ontology - what do we do with this? Maybe kill the project in HL7 and find another group who wants to take it on?
+
#Patient Care
Decision: Kill the current project and explore other options if we want to resurrect the project.
+
#* Status - reopened the letter of intent until December but had no takers. It is now closed. Interest from LSU and they are offering one of their hospitals as a possible test bed. Next submission date is for the March OMG meeting.  
  
'''Notes from Vince'''
+
Ken - VA is doing work about workflow and care teams, transitions within and between care teams. Right now what is in FHIR care teams resources is falling short of what VA needs. This is an angle for coordination of care. Need to know the structure and high-level thinking in order to get it into the spec.
''Joint with Patient Care (PC)''
 
  
Status of Coordination of Care Service SFM publication
+
Laura - ONC started calls on care teams on Fridays. PC owns care teams as a steward and are really working through some of the issues. There is an outstanding question regarding if this needs to be pulled into HL7 PC.  
*Was missed in publication cycle.  
 
*Publication request form is being finalised by PC this week – to be reviewed by Ken on behalf of SOA.
 
*Actual document is ready to go.
 
*Coordination of Care OMG submission status
 
**OMG meeting Chicago last week => submission cycle re-opened because only one official submitter (MEDisched with support from Allscripts). Believe that Allscripts will join. State of New York may also be a submitter. Re-opened until Dec 2016.
 
Revised initial submission date March 2017, revised submission date September 2017
 
Technical – now planning to do a FHIR implementation – still working up how to that with current FHIR resources around care plan. Using the clinical Connectathon to test the FHIR resources.
 
*Careplan specification has been implemented as an IHE profile – being trialed at the January 2017 connectathon.
 
**Ken strongly suggested that PC provide a delegate to the submission team to represent HL7 interests.
 
**ONC is trying to coordinate all care planning standards activity – PC will be exploring this to have a multi-committee quarter next WG
 
  
Scheduling Service
+
For Madrid - Set up a joint meeting with PC Tuesday at Q2.
*Has been developed by SOA. PA has agreed to be primary sponsor, FHIR is a co-sponsor.
 
*Ken described scope as per SOA website and relationship to FHIR scheduling resource
 
*Question: are PC interested in being a co-sponsor ?
 
*PSS is being prepared and should be ready by end of week.
 
*Planning DSTU Jan 18 ballot cycle
 
*General feeling PC does want to co-sponsor – will discuss with workgroup and let us know level of support to be noted in the PSS.
 
  
 
==TUE Q3==
 
==TUE Q3==
  - attendees: 7
+
  - See Attendees Section below
 
#Patient Administration (Confirmed)  
 
#Patient Administration (Confirmed)  
#*Scheduling Service Discussion:  
+
#*Scheduling Service Discussion:
*Finished up the PSS for scheduling service.
+
#**gForge items
*Motion by Cooper. Seconded by Diana: SOA WG recommends that PA accept the PSS for Scheduling Service as posted on 9/20/2016. Passed unanimously: 6/0/0
+
#**Structure of slot
*DSTU ballot for SFM Sep 2017. In FHIR Ballot for Jan 2018
+
#**Methodology Status
 +
#***Ken - seems like folks have a handle on the FHIR stuff but the SFM process is a bit opaque. Ken presents the HSSP Process document. Hope is to get 3 or 4 folks (Brian Postlethwaite, Bryn Rhodes, and Dave Carlson) who know both Scheduling and FHIR to work through the process and identify issues with the process and help refine it. Cooper - Trying to understand how this is going to work in the current way of doing things. Brian/Andrew: we may build something faster than this process will allow. Ken - may have to do this iteratively where we start with a "pre-alpha" product. Where we came out of the Baltimore meeting having identified the service specification package which includes 6 elements (listed in the HSSP process document). In the short-term, will work with what we have in STU3 but we don't want to do anything that will interfere with the use of STU4.
 +
#***Andrew: we will start building stuff before STU3 even due to demand. We will be harmonizing with upcoming STU3 and then 4 work.
 +
#**Status of specification
 +
#***Ken - see if I can get more involvement on the VA side. HSPC may have some providers that would be interested in this project. Cooper: we had more folks coming but we haven't done a good job of pulling in all folks who have expressed an interest. Ken: It helps to have something "half-baked" before bringing in the folks on your list.
 +
#***Encounter has been cleaned up. Appointment has similar issues with cardinality. In the process of cleaning up. Need to open up the cardinality to 0..*. The reason for the appointment may not be declared at the time of the scheduling of the appointment. Ken - suggesting that there should be a primary reason and then secondary reasons as this can affect the equipment needed and even the location of the appointment. When at HP, they had some pretty mature scheduling analysis work. If we think that would be useful, I can reach out to HP and see if they are willing to release the information to HL7.  
 +
#**FHIR STU4 Discussion: Goal is to have a substantial scheduling service available for STU4.
 +
#***There is some workflow portability work that is happening elsewhere that could be brought in here. STU4 is a working goal.
  
Cooper was asked about making the joint meeting Tues Q2 to include Patient Care and Patient Administration. Keep Tues Q3 as joint with PA.
+
vote: 14/0/2 to support the 9262 FHIR change request for the Appointment resource.
 +
Recommendation: PA create a split meeting for this quarter where PA can only send the folks who are interested.
  
 
==TUE Q4==
 
==TUE Q4==
  - attendees: 8
+
  - See Attendees Section below
#Ordering Service Discussion
+
#Ordering Service Work Session
 
#*Walkthrough of ordering service technical specification work,
 
#*Walkthrough of ordering service technical specification work,
#*relationship to FHIR workflow activities, and
+
#*relationship to FHIR workflow activities,
 +
#**Catalog resource is being proposed for FHIR. Ordering Service SFM was expanded to incorporate the FHIR Catalog resource. FHIR workflow hasn't really pulled in anything from Ordering Service or FHIR Catalog. The OMG submission consists of the Ordering Service Technical submission which incorporates Order Management and Catalog Management. The FHIR Workflow has 6 architectures but most of what they have currently aren't workflows.
 
#*state of OMG submissions
 
#*state of OMG submissions
 +
#**took to OMG in Dec 2016 and is available for review at https://healthservices.atlassian.net/wiki/display/WGS/HSPC+OMG+Ordering+Service+RFP+WG
 +
#**The OMG prefers the normative version to be the UML model. Claude is working on the ordering front. Hoping the final submission would be in March but finding that to be a bit ambitious.
 +
#**Fleshed out Order Proposal Handling and Order WorkFlow. Updated OrderQuery. Trying to be compliant with SOAP (FHIR) and RestFul implementations (requirement of RFP). OMG requires both PIMs and PSMs. Currently working on the PIM. Ordering as a domain is dynamic. Have is set up using encapsulation to allow for flexibility. The Main Order Entities model is to undergo major revision to reduce confusion due to state changes that were only implicit and terms that are too similar. In OO, they tried to take a diagnostic order and go through the workflow. Need to be able to associate a workflow with an item. What is inside the workflow may change depending on the implementation. Also need an ordering service that may or may not plug into a fulfillment service.
 +
#**Recommended approach: Work the specification and submit. Later, bring in the FHIR implementation and then put out an RFC.
  
Jerry presented the SFM diagram and a draft version of the PIM data Model. Requirement Association, status and requirement will be changing in the PIM.
+
'''Action Item''': Jerry Goodnough to reach out to Jonathan Nebeker about providing resources for this project.
 
 
Will show curated content in the PISM.
 
 
 
Not just an order execution service any more. Allows for advice and changes in the process.
 
 
 
Order catalog management is the other part of the specification. Building and dist of evidence-based catalogs.
 
 
 
Claude has agreed to blaze the trail with FHIR and catalog stuff.
 
 
 
Changed language from "fuzzy" query language to explicit language.
 
 
 
Still looking for a good work-flow model. When we get to PISM will need to determine the FHIR workflow.
 
 
 
This is posted to https://healthservices.atlassian.net/wiki/display/WGS/HSPC+OMG+Ordering+Service+RFP+WG
 
 
 
Now have a reference type which allows us to associate certain information to validate the order.
 
 
 
Would like feedback into the FM.
 
 
 
PIM: you can have semantic profiles. At the PIM level you can get away with less strong typing.
 
 
 
Getting key data elevated in order to be able to do first order processing.
 
 
 
Referrals are in scope.
 
 
 
Timeline: Nov 7 submission. Order catalog is behind by about 6 months.
 
 
 
Suggestion to do a peer review in January.
 
 
 
Action item: Ask for an extension on for Pub/Sub and E&S during the Jan 2017 meeting.
 
 
 
'''Notes from Vince'''
 
 
 
''Order Service''
 
*Current HL7 DSTU
 
*OMG submission underway for 1 year
 
*Two parts – order management and order catalogue. Order management allows order building as well as execution.
 
Catalogue allows building of an appropriate order from an order type specific catalogue to arrive at an appropriate order e.g. no L/S spine Xray order for back pain.
 
*Also includes an interface to a fulfilment service.
 
*See HSPC site for OMG current draft
 
 
 
 
 
#X-Paradigm Interoperability Project Discussion
 
#*Action Item for Ken Lord: Need to make sure that the ballot reconciliation package has been uploaded.
 
  
 
==WED Q1: Split meeting==
 
==WED Q1: Split meeting==
 
#Joint w/EHR, Security, CBCC, SOA, FHIR (See EHR for meeting minutes)
 
#Joint w/EHR, Security, CBCC, SOA, FHIR (See EHR for meeting minutes)
 
  - attendees:
 
  - attendees:
#Scheduling Service Continuing discussion - cancelled
+
#Cancelled
  
 
==WED Q2==
 
==WED Q2==
  - attendees:
+
  - See Attendees Section below
 
+
Project updates:
'''1. PASS ACS vote to request publication.'''
 
 
 
Ballot completed and reconciliation package uploaded. All negative votes have been withdrawn.
 
 
 
Motion – Proposed: Mike Davis
 
Seconded Trish Williams
 
 
 
“SOA approves PASS ACS project go forward to publication as Normative”
 
 
 
Vote 11/1/0
 
Motion passes.
 
 
 
Mike and Kathleen will help Diana with the publication request formalities.
 
 
 
'''2. HL7 Cloud Planning Guide'''
 
 
 
Ken Rubin informed the meeting of current progress with the HL7 Cloud planning Guide
 
document can be found at hssp.wikispaces.com/cloud
 
 
 
Survey on this topic conducted since last WGM  – 3 page questionnaire taking 15 minutes to complete
 
 
 
*50 responses
 
*70% USA, 20% Europe, 10% Asia
 
 
 
70% indicated there were residency policy restrictions for where Health data can be hosted.
 
 
 
Ken went through results which demonstrated wide interest – they will be published on the wiki in the near future.
 
There were two areas where there were Health specific issues one of which was security. However, we could not get security involvement previously.
 
 
 
Now SOA is once again seeking input.
 
 
 
Mike Davis – increased interest due to new solutions from Amazon and Microsoft with security adequate for healthcare data/HIPAA requirements. Renewed interest in software as a service (SAAS).
 
Further work will be undertaken on this Q1 Thursday following a presentation by guest speaker from Amazon web services and plans for Health data in the cloud.
 
 
 
Japan – Amazon in Tokyo is bound by the USA Patriot act under which the FBI can block access to data. Japan thus currently requires separation between private and public cloud.
 
 
 
The intent of the document is (i) make people aware of what the issues are, (ii) where to look for possible information and solutions, (iii) Identify patterns that may be useful
 
 
 
Plan to ballot as informative document for January cycle. TCs bi-weekly. Trish Williams indicated she would like to participate, Mike David will look at document and let us know. Microsoft have indicated they will provide a participant. Kathleen will provide some references.
 
  
Kathleen – after completing this may need to revise privacy and security recommends to take into account specific cloud issues. Trish to look at what work is relevant at ISO TC215 WG 4.
+
#Cloud Planning Guide
 
+
#*Consistent group meeting and advancing the work. May target.
Action items:
+
#*Identifying areas where HL7 standards have particular relevance;  security a key area of interest
*SEC to access the PSS in order for them to consider being added as a co-sponsor.
+
#“SOA on FHIR”
*SOA to send document to security – completed.
+
#*Has been a SOA priority; have a much better perspective on how to do that now
*Times for calls to be changed to allow Australian and European participation ?4pm eastern
+
#*Producing a collective set of FHIR artifacts templated to SOA
 
+
#*Working in collaboration with FHIR Infrastructure Group
'''3. PASS Audit'''
+
#Security Labeling Service PSS
*Documentation on the HL7 wiki
+
#*New project scope statement to build upon existing SLS work
*Previously balloted document has been used as starting point and the previous ballot comments are being reconciled.
+
#*Re-envision to align work to FHIR;  building on SOA on FHIR activities
*Plan to have updated document by end of October for distribution to SOA/SEC
+
#**Some discussion about the role of SLS as applied to FHIR. Not self-evident how they fit together; 
*Plan ballot in January. There are weekly calls Wednesday at 4pm Eastern
+
#**API is content specifying but content agnostic
 
+
#**Discussion and questions about the role of SLS and persistence of Security Labeling in FHIR
'''4. Future plans'''
+
#**Questions about whether a dedicated FHIR section should be added to the document
*Roadplan document that had been produced some time ago was discussed:
+
#**1138 CST:  Mike Davis agreed with John Moehrke on Project scope wording re: FHIR
*Possibilities for future services
+
#**SLS to address how to inspect FHIR objects
 
+
#**Motion to Accept PSS (Kathleen Connor)  Second (Mike Davis). Passed (14-0-4)
(i) Identity resolution and trust
 
 
 
(ii) Consent administration
 
 
 
(iii) Authorization
 
 
 
(iv) Mask
 
 
 
(v) Encrypt/decode
 
 
 
(vi) Anonymization/pseudonymization
 
 
 
(vii) Sign
 
 
 
(viii) Pseudonym service
 
 
 
*NIST has published a SHA-3 standard which VA is recommending
 
 
 
There may be some interest in consent and mechanisms for transmitting consent between organisations.
 
 
 
How to take security SFMs to PSMs?
 
*OMG RFP
 
*Integrate into FHIR as service
 
*Use an alternate SDO to OMG that is specific to security
 
 
 
Alternatives discussed – to be resolved.
 
 
 
Mike Davis to consider VA support for an OMG process for the Security Services.
 
 
 
SOA Joint meeting with Security will take place at January WGM.
 
  
 
==WED Q3/Q4==
 
==WED Q3/Q4==
  - attendees: 13
+
  - See Attendees Section below
#Refresh of Service Functional Model specification process in the world of FHIR.
+
#Reference Architecture: Work on it Thursday, Q2.
#* The current Service specification process involves both HL7 and OMG and generally defers technical implementation until further in the process.  Given the energy around FHIR and the potential for lost opportunity to impact FHIR, this discussion will revisit our approach to determine better ways to align with and engage FHIR activities synergistically with SOA efforts.
+
#Cloud discussion
 
+
#*Vadim presented a proposed simplification of the scope of the document. Proposing that we start with high-level, universal concerns that come up when looking at a cloud implementation.
Created a preliminary SOA process ppt for working with FHIR.
+
#*In answer to the question, why do this, Ken suggested these bullet points:
 
+
#**HL7 does a lot of implementation guides, and did not have presence in the cloud space.
HL7 OMG vote is a lever we can use.
+
#**Many HL7 standards are being implemented using cloud platforms.
 
+
#**In conjunction with HSPC, we are addressing what has been a significant gap in the industry.
Grahame moved. Jerry seconded. Motion to accept the process as discussed and described in the SOA-FHIR Process PPT. Passed 12/0/0
+
#*Proposal - Finish going through Vadim's presentation and then take a first pass at the Phase 2 content and that might be as much as we get through for the May ballot.
*[http://wiki.hl7.org/index.php?title=File:SOA-FHIR_Process.pptx Link to PPT on which SOA and FHIR voted.]
+
#*Who is our audience? One possibility is IT folks talking to Managers and needing a resource regarding which addresses their concerns. For the newbie, it's education and ramp-up, for the expert - it's legitimization or substantiation, for the intermediate - it's validation.  
 
+
#*Motion: Approach HSPC about making this a joint collaborative effort subject to HL7 and HSPC board agreement. Ken made motion, Vadim seconded. 5/0/0
Concurrent development by breaking the development of the STU into different work threads which are developed concurrently in order to speed up development.
+
#*'''Action Item''' - Ken will approach HSPC regarding above motion.
 
+
#SOA Platform - Phase 2
FHIR implementations can start before the STU is balloted.
+
#*Awareness of HL7 portfolio
 
+
#**SOA
Action item: Need to think through how we engage the community, eg. through the FHIR connectathon process.
+
#**FHIR
 
+
#*Reference implementation examples (Reference Architecture diagram if we have a deployment diagram showing how the cloud and HL7 worlds fit using the HSPC platform container model.)
Vic: One possibility is to specify test specs for the developers/implementers.
+
#*Bring in responses to survey to legitimize why these services are valuable.
Ken: There is no shortage of, or consistency of, test specs. I (Ken) don't want to take that on at this point.
 
*[http://wiki.hl7.org/index.php?title=File:SOA-FHIR_Process_v2.pptx Link to updated version of the PPT.]
 
  
Update on OMG:
+
#Reference Architecture discussion
1. Letter of intent: last week the coordination of care submission team voted to open up the LOI through the end of 2016. New initial submission date is March 17, 2017. Slips the final date a little. Want to align with FHIR.
+
#*MDMI isn't a service. There should be a different color for supporting specifications that aren't services.
2. EMR: Create a set of curated workflows that can be ported. Going to have a workshop at the OMG event, 1st week in December in Coronado, CA. Blurb on the OMG site will be up sometime next week.
+
#*Want to extend the current Reference Architecture diagram by diagramming out a use case which accesses multiple services.
 +
#**Possible use case - Payor (insurance), Eligibility, Patient Care Lifecycle (Continuity of care, transfer of care from inpatient to outpatient & long-term care/physical therapy.)
  
 
==Thurs Q1==
 
==Thurs Q1==
  - attendees: 9
+
  - See Attendees Section below
#HL7 Cloud Planning Guide Work session 
+
#Co-chairs met to discuss plans for Madrid.
#* Presentation on Amazon Web Services by Huy H.
+
#Co-chairs agreed to meet on a monthly basis in order to identify direction for future work in SOA.
Introduced himself and did a brief description of cloud.
 
 
 
Healthcare on the cloud: 83% healthcare orgs are on cloud.
 
HIPAA's change to definition of business associate means that the cloud provider is a business associate and therefore you need a business associate agreement with the cloud provider. There is a shared responsibility.
 
Cloud provider is responsible for:
 
*facility operations
 
*physical security
 
*physical infrastructure
 
*network infrastructure
 
*virtualization infrastructure
 
*hardware lifecycle management
 
 
 
HIPAA compliance is up to customer at this point in time.  
 
If AWS can have a list of HIPAA compliant service providers available
 
 
 
Cloud provider responsibilities
 
*Implement appropriate safeguards to prevent unauthorized use of disclosure of PHI
 
*Report incidents that constitute breaches PHI
 
* Make available to HHS its internal practices, books, and records relating to the use and disclosure of PHI
 
*Any subcontractors must agree to the same restrictions and conditions
 
'' '''to which level of access they control''' ''
 
 
 
Does AWS help figure out where the breech happens? yes. Their incident team will help to pinpoint where the breech occurs.
 
 
 
AWS is in the business of data centers
 
 
 
Redundancy for Denial of service or outages? depends on which service you are using. If using software as a service (Like dynamoDB) where there are multiple availability zones. Infrastructure as a service, not necessarily. Platform as a service, you go to the platform vendor.
 
 
 
Hypervisor - multiple virtual machines
 
 
 
Customer Responsibilities
 
*Only process, store, and transmit PHI using HIPAA designated accounts and HIPAA-eligible services
 
*Encrypt PHI in transit and at rest, access control, and network isolation.
 
*Use hardware dedicated virtual compute instances
 
**Dedicated instances are physically isolated at the host hardware level from instances that are not dedicated and from instances that belong to other accounts.
 
*Must record and retain activity related to use of and access to ePHI
 
*Must have contingency plan to protect data in case of emergency. Back ups are the responsibility of whomever controls the database.
 
 
 
HIPAA dictates that there needs to be a dedicated PHYSICAL server for the data. This brings up a question of tenancy. For US health customers, what are the data tenancy requirements? Is there a tenancy requirement that data not leave the state? If that is the case, there are no cloud data center in Utah because they don't have the infrastructure already in place (fiber trunk). Need to investigate if there are data residency requirements at the state level.
 
 
 
AWS HIPAA Program is FedRAMP certified for government use.
 
 
 
AWS HIPAA Eligible Services
 
* Customers may use all services within a HIPAA Account.
 
*Customers may process, store, or transmit ePHO using only Eligible Services.
 
**EC2
 
**EBS
 
**Elastic Load Balancing
 
**S3 - storage service
 
**Amazon Glacier - Archive service
 
**Amazon Redshift - data warehouse built to analyze data fast
 
**Amazon DynamoDB
 
**Amazon RDS for MySQL
 
**Amazon RDS for Oracle
 
**Amazon EMR (elastic map reduce(?))
 
 
 
(Diagram: first red outline - public subnet second is private subnet. All data in transit needs to be over SSL.)
 
There are other architectural services available which don't touch PHI but which can be used to support none PHI data and infrastructure.
 
  
 
==Thurs Q2==
 
==Thurs Q2==
  - attendees: 5
+
  - See Attendees Section below
#Hot Topics
+
#Identified a Care use case scenario and created a sequence diagram showing the SOA services interacting in order to complete the steps of the scenario.
*Round Robin de-brief on week.
+
[http://wiki.hl7.org/index.php?title=File:PCP-Specialist-Care_Team_Scenario.docx Patient Care Referral Scenario]
**Vince: Glad the new services are moving forward. Good representation of services at connectathon and incorporation of services resources in FHIR. Pleasing that SOA and FHIR are moving forward to work together and that we are being pushed to be less waterfall and we've pushed them to be more structured in behavior.
 
**Ken: Each quarter was geared toward moving toward an objective rather than just doing an update. Found the meetings to be very productive.
 
**Joint EHR/Security/CBCC/SOA meeting:
 
***Action item - bring order service and scheduling service for inclusion on the Joint EHR agenda. What other items need to be included on that agenda?
 
***Action item - need to improve communications. Haven't done a webinar in a while. Could put together a webinar on SOA services.
 
***Huy: (Looking at HSSP website diagram) missing monitoring service (devices)in application swim lane and service registry.
 
***AI: Refresh the SOA Practical Guide. Among other things, add the FHIR process.
 
*Kudos to Diana for bringing us into Green.
 
 
 
*Administrivia.
 
**3 year plan?
 
*Repository of service models
 
**do we want one? Definitely desirable.
 
**Possibly use HingeX? Put it on the HSSP website?
 
*Cloud
 
**AI: Trish Williams will follow up on how the Patriot Act affects international customers. (In all likelihood, this is high impact, low probability.) Does the Patriot Act affect a data center that is physically located outside of the US? Depends on how the cloud provider company is structured.
 
 
 
Elasticity is accomplished through provisioning to a different machine.
 
Containerization
 
 
 
Walked through outline of Cloud paper:
 
This is not a paper that folks will be reading cover-to-cover as opposed to cherry-picking the parts of the paper that apply to them.
 
AI: Huy is willing to address section 5. Cloud Maturity Model. Self-survey.
 
 
 
Blueprints are design patterns.
 
*What is the structure that we should follow?  
 
*may be more about business objectives.
 
*multi-cloud design pattern
 
 
 
Brought up the Cloud survey.
 
*Maybe use the "Our principle interests in Cloud are based upon" responses as the categories for the blueprints?
 
*Big data analytics strong driver
 
*don't really have an ROI section in the white paper. Add a section for helping to determine ROI for moving to cloud.
 
  
 
==Attendees==
 
==Attendees==
Line 620: Line 373:
 
|-
 
|-
 
|-
 
|-
! '''SOA Attendee'''||1 MON Q3||2 MON Q4 !! 3 TUES Q1  || 4 TUES Q2 !! 5 TUE Q3 || 6 TUE Q4 || 7 WED Q2 !! 8 WED Q3 || 9 WED Q4 !! 10 THU Q1 || 11 THU Q2 !!
+
! '''SOA Attendee'''||1 MON Q3||2 MON Q4 !! 3 TUES Q1  || 4 TUES Q2 !! 5 TUE Q3 || 6 TUE Q4 || 7 WED Q1 !! 8 WED Q2 || 9 WED Q3 || 10 WED Q4 !! 11 THU Q1 || 12 THU Q2 !!
 +
|-
 +
|-
 +
|| [mailto:ken.rubin@utah.edu Ken Rubin]SOA Co-Chair/VA ||x||x||x||x||x||x||7||x||x||x||x||12||10||.
 +
|-
 +
|| [mailto:diana.proud-madruga@va.gov Diana Proud-Madruga]SOA Co-Chair/VA ||1||x||x||x||x||x||7||x||x||x||x||x||11||.
 +
|-
 +
|| [mailto:Vincent.McCauley@emerging.com.au Vincent McCauley] SOA Co-Chair/Telstra Health
 +
|-
 +
|| [mailto:slotti@invitalia.it Stefano Lotti] SOA Co-Chair ||x||x||x||x||x||x||7||x||x||x||x||x||12||.
 +
|-
 +
|| [mailto:dave.carlson@bookzurman.com Dave Carlson] Book Zurman ||1||2||x||4||5||6||7||8||9||10||11||12||1||.
 +
|-
 +
|| [mailto:lorraine@constable.ca Lorraine Constable] Constable Consulting    ||1||2||x||4||5||x||7||8||9||10||11||12||2||.
 +
|-
 +
|| [mailto:jgoodnough@cogmedsys.com Jerry Goodnough] Cognitive Med. Sys. ||x||x||3||4||x||x||7||8||x||x||11||x||7||.
 +
|-
 +
|| [mailto:mjafari@esc.com Mohammad Jafari] VA
 +
|-
 +
|| [mailto:preston@asu.edu Preston Lee] VA, Arizona State University   
 +
|-
 +
|| [mailto:klordmdmi@gmail.com Ken Lord] VA 
 +
|-
 +
|| [mailto:dan.morford@bookzurman.com Dan Morford] Book Zurman
 +
|-
 +
|| [mailto:sean.muir@va.gov Sean Muir] VA ||x||2||x||4||5||6||7||8||9||10||11||12||2||.
 +
|-
 +
|| [mailto:vpolyakov@inovalon.com Vadim Polyakov] Inovalon ||x||x||x||x||x||x||7||8||x||x||11||12||8||.
 +
|-
 +
|| [mailto:christopher.shawn2@va.gov Chris Shawn] VA ||1||2||3||4||5||6||7||x||9||10||11||12||1||.
 +
|-
 +
|| [mailto:trish.williams@ecu.edu.au Trish Williams] Edith Corvan Univ
 +
|-
 +
|| [mailto:ddecouteau@edmondsci.com Duane DeCouteau] VA ||1||2||3||4||5||6||7||x||9||10||11||12||1||.
 +
|-
 +
|| [mailto:mike.davis@va.gov Mike Davis] VA ||1||2||3||4||5||6||7||x||9||10||11||12||1||.
 +
|-
 +
|| [mailto:jc@securityrs.com Johnathan Coleman] ONC
 +
|-
 +
|| [mailto:miyohara.hideyuki@ap.mitsubishielectric.co.jp Hideyuki Miyohara] HL7 Japan  ||1||2||3||4||5||6||7||x||9||10||11||12||1||.
 +
|-
 +
|| [mailto:joshua.mandel@childrens.harvard.edu Josh Mandel] Children's Harvard  ||1||2||x||4||5||6||7||8||9||10||11||12||1||.
 +
|-
 +
|| [mailto:kshekleton@cerner.com Kevin Shekleton] Cerner   
 +
|-
 +
|| [mailto:laura.heermann@imail.org Laura Heermann] Intermountain Healthcare ||1||2||3||4||x||6||7||8||9||10||11||12||1||.
 
|-
 
|-
 +
|| [mailto:emma.jones@allscripts.com Emma Jones]  Allscripts 
 
|-
 
|-
|| [mailto:ken.rubin@utah.edu Ken Rubin]SOA Co-Chair/VA ||x||||x||x||x||x||x||x||x||x||x||10
+
|| [mailto:cnanjo@cognitivesys.com Claude Nanjo] Cognitive 
 
|-
 
|-
|| [mailto:diana.proud-madruga@va.gov Diana Proud-Madruga]SOA Co-Chair/VA ||x||x||x||x||x||x||x||x||x||x||x||11
+
|| [mailto:juha.mykkanen@thl.fi Juha Mykkanen] HL7 Finland/National Institute for Health and Welfare (THL) Finland 
 
|-
 
|-
|| [mailto:Vincent.McCauley@emerging.com.au Vincent McCauley] SOA Co-Chair/Telstra Health ||x||x||x||x||x||x||x||x||x||x||x||11
+
|| [mailto:brynlewis@intelsoft.com.nu Bryn Lewis] Intelsoft   
 
|-
 
|-
|| [mailto:slotti@invitalia.it Stefano Lotti] SOA Co-Chair
+
|| [mailto:manoj.sharma2@allscripts.com Manoj Sharma] Allscripts   
 
|-
 
|-
|| [mailto:vpolyakov@inovalon.com Vadim Polyakov] Inovalon ||x||x||x||x||x||x||||x||x||||||8
+
|| [mailto:chana.west@esacinc.com Chana West] ESAC Inc.   
 
|-
 
|-
|| [mailto:jgoodnough@cogmedsys.com Jerry Goodnough] Cognitive Med. Sys. ||x||x||x||x||x||x||||x||x||||x||9
+
|| [mailto:kevan.riley@infor.com Kevan Riley] Infor (?) 
 
|-
 
|-
|| [mailto:preston@asu.edu Preston Lee] VA, Arizona State University    ||x||x||||||x||x||||||||||||4
+
|| [mailto:zach.may@esacinc.com Zach May] ESAC Inc.   
 
|-
 
|-
|| [mailto:klordmdmi@gmail.com Ken Lord] VA   ||||x||x||||||||||||x||x||||4
+
|| [mailto:mdrashedul.hasan@fda.hhs.gov Rashedul Hasan] FDA    
 
|-
 
|-
|| [mailto:lorraine@constable.ca Lorraine Constable] Constable Consulting   ||||||||x||||x||||||x||||||3
+
|| [mailto:cooper@epic.com Cooper Thompson] Epic   ||1||2||3||4||x||6||7||8||9||10||11||12||1||.
 
|-
 
|-
|| [mailto:dan.morford@bookzurman.com Dan Morford] Book Zurman ||||||||x|||||||||||||||1
+
|| [mailto:Karl.holzer.cgm.com Karl Holzer] CGM   
 
|-
 
|-
|| [mailto:dave.carlson@bookzurman.com Dave Carlson] Book Zurman ||||||||x||||||||||x||||||2
+
|| [mailto:oliver.krauss@fh-hagenberg.at Oliver Krauss] University of Applied Science Upper Austria 
 
|-
 
|-
|| [mailto:sean.muir@va.gov Sean Muir] VA ||||||||||||||||||x||||||1
+
|| [mailto:alexander.mense@hl7.at Alexander Mense] HL7 Austria    ||1||2||3||4||5||6||7||x||9||10||11||12||1||.
 
|-
 
|-
|| [mailto:trish.williams@ecu.edu.au Trish Williams] Edith Corvan Univ ||||||||||||||x||||||||||1
+
|| [mailto:grahmeg@gmail.com Grahame Grieve]  
 
|-
 
|-
|| [mailto:christopher.shawn2@va.gov Chris Shawn] VA ||||||||||||||x||||||||||1
+
|| [mailto:victor@omg.org Victor Harrison] OMG 
 
|-
 
|-
|| [mailto:mjafari@esc.com Mohammad Jafari] ||||||||||||||x||||||||||1
+
|| [mailto:eafry@cogmedsys.com Emory Fry] Cognitive  ||x||x||3||4||5||x||7||8||9||10||11||12||3||.
 
|-
 
|-
|| [mailto:ddecouteau@edmondsci.com Duane DeCouteau] VA ||||||||||||||x||||||||||1
+
|| [mailto:elizabeth.h.newton@kp.org Elizabeth Newton] KP 
 
|-
 
|-
|| [mailto:mike.davis@va.gov Mike Davis] VA ||||||||||||||x||||||||||1
+
|| [mailto:gora@cal2cal.com Gora Datta] ?   
 
|-
 
|-
|| [mailto:jc@securityrs.com Johnathan Coleman] ONC ||||||||||||||x||||||||||1
+
|| [mailto: Kathleen Connor] VA    ||1||2||3||4||5||6||7||x||9||10||11||12||1||.
 
|-
 
|-
|| [mailto:miyohara.hideyuki@ap.mitsubishielectric.co.jp Hideyuki Miyohara] HL7 Japan  ||||||||||||||x||||||||||1
+
|| [mailto:astatler@cerner.com Andrew Statler] Cerner   
 
|-
 
|-
|| [mailto:joshua.mandel@childrens.harvard.edu Josh Mandel] Children's Harvard  ||||||x||||||||||||||||||1
+
|| [mailto:bpech1@? Brian Pech] ?   
 
|-
 
|-
|| [mailto:kshekleton@cerner.com Kevin Shekleton] Cerner   ||||x||||||||||||||||||||1
+
|| [mailto:mscrimshire@gmail.com Mark Scrimshire] ?    
 
|-
 
|-
|| [mailto:laura.heermann@imail.org Laura Heermann] Intermountain Healthcare ||||||||x||||||||||||||||1
+
|| [mailto:vvasiltsov@cagh.org Vladimir Vasiltsov] CAGH 
 
|-
 
|-
|| [mailto:emma.jones@allscripts.com Emma Jones] Allscripts  ||||x||||x||||||||||||||||2
+
|| [mailto:huynhz@amazon.com Huy Huynh] Amazon   
 
|-
 
|-
|| [mailto:cnanjo@cognitivesys.com Claude Nanjo] Cognitive   ||||||x||||||||||||||||||1
+
|| [mailto:craig.knier@mckesson.com Craig Knier] McKesson   ||x||x||3||4||5||6||7||8||9||10||11||12||2||.
 
|-
 
|-
|| [mailto:juha.mykkanen@thl.fi Juha Mykkanen] HL7 Finland/National Institute for Health and Welfare (THL) Finland  ||||x||||||||||||||||||||1
+
|| [mailto:adamu.haruna@nokia.com Adamu Haruna] Nokia  ||x||2||3||4||5||6||7||8||9||10||11||12||1||.
 
|-
 
|-
|| [mailto:brynlewis@intelsoft.com.nu Bryn Lewis] Intelsoft    ||||x||||x||||x||||||||||||1
+
|| [mailto:chris.grear@analysts.com Chris Grear] Analysts  ||1||x||3||4||5||6||7||8||9||10||11||12||1||.
 
|-
 
|-
|| [mailto:manoj.sharma2@allscripts.com Manoj Sharma] Allscripts    ||||x||||||||||||||||||||1
+
|| [mailto:klemoine@cdc.gov Kent Lemoine] CDC  ||1||2||x||4||5||6||7||8||9||10||11||12||1||.
 
|-
 
|-
|| [mailto:chana.west@esacinc.com Chana West] ESAC Inc.    ||||||x||||||||||||||||||1
+
|| [mailto:rene.kinsey@va.gov Rene Kinsey] VA  ||1||2||x||4||5||6||7||8||9||10||11||12||1||.
 
|-
 
|-
|| [mailto:kevan.riley@infor.com Kevan Riley] Infor (?)   ||||||x||||||||||||||x||||2
+
|| [mailto:smater@epic.com Sam Mater] Epic   ||1||2||3||x||x||6||7||8||9||10||11||12||2||.
 
|-
 
|-
|| [mailto:zach.may@esacinc.com Zach May] ESAC Inc.    ||||||x||||||||||||||||||1
+
|| [mailto:lgu3@cdc.gov Shuai Zheng] CDC  ||1||2||3||x||x||x||7||8||9||10||11||x||4||.
 
|-
 
|-
|| [mailto:mdrashedul.hasan@fda.hhs.gov Rashedul Hasan] FDA  ||||||x||||||||||||||||||1
+
|| [mailto:tracy.angeles@conduent.com Tracy Angeles] Conduent  ||1||2||3||4||x||6||7||8||9||10||11||12||1||.
 
|-
 
|-
|| [mailto:cooper@epic.com Cooper Thompson] Epic   ||||||||||x||||||x||||||||2
+
|| [mailto:alexander.j.deleon@kp.org Alex DeLeon] Kaiser Permanente   ||1||2||3||4||x||6||7||8||9||10||11||12||1||.
 
|-
 
|-
|| [mailto:Karl.holzer.cgm.com Karl Holzer] CGM   ||||||||||||x||||||||||||1
+
|| [mailto:jongeneel@v2v2.nl Irma Jongeneel] HL7 Netherlands   ||1||2||3||4||x||6||7||8||9||10||11||12||1||.
 
|-
 
|-
|| [mailto:oliver.krauss@fh-hagenberg.at Oliver Krauss] University of Applied Science Upper Austria  ||||||||||||x||||||||||||1
+
|| [mailto:wrishel@gmail.com Wes Rishel] Self    ||1||2||3||4||x||6||7||8||9||10||11||12||1||.
 
|-
 
|-
|| [mailto:alexander.mense@hl7.at Alexander Mense] HL7 Austria    ||||||||||||||x||||||||||||1
+
|| [mailto:drew.torres@cerner.com Andrew Torres] Cerner  ||1||2||3||4||x||6||7||8||9||10||11||12||1||.
 
|-
 
|-
|| [mailto:grahmeg@gmail.com Grahame Grieve]    ||||||||||||||||||x||||||1
+
|| [mailto:brian.pos@hotmail.com Brian Postlethwaite] Telestra Health   ||1||2||3||4||x||6||7||8||9||10||11||12||1||.
 
|-
 
|-
|| [mailto:victor@omg.org Victor Harrison] OMG   ||||||||||||||||||x||||||1
+
|| [mailto:sh@getyra.de Simone Hickmann] HL7 Germany   ||1||2||3||4||x||6||7||8||9||10||11||12||1||.
 
|-
 
|-
|| [mailto:eafry@cogmedsys.com Emory Fry] Cognitive   ||||||||||||||||||x||||||1
+
|| [mailto:biru.yang@houstontx.gov Biru Yang] Houston Health Dept   ||1||2||3||4||x||6||7||8||9||10||11||12||1||.
 
|-
 
|-
|| [mailto:elizabeth.h.newton@kp.org Elizabeth Newton] KP   ||||||||||||||||||||x||||1
+
|| [mailto:truc.pham@houstontx.gov Truc Pham] Houston Health Dept   ||1||2||3||4||x||6||7||8||9||10||11||12||1||.
 
|-
 
|-
|| [mailto:gora@cal2cal.com Gora Datta] ?    ||||||||||||||x||||||x||||2
+
|| [mailto:aliraza.momin@houstontx.gov Ali Momin] Houston Health Dept  ||1||2||3||4||x||6||7||8||9||10||11||12||1||.
 
|-
 
|-
|| [mailto: Kathleen Connor] VA   ||||||||||||||x||||||||||1
+
|| [mailto:Suzanne.Gonzales-Webb@va.gov Suzanne Gonzales-Webb] VA ||1||2||3||4||5||6||7||x||9||10||11||12||1||.
 
|-
 
|-
|| [mailto:astatler@cerner.com Andrew Statler] Cerner    ||||||||||||||x||||||||||1
+
|| [mailto:david.pyke@readycomputing.com David Pyke] Ready Computing  ||1||2||3||4||5||6||7||x||9||10||11||12||1||.
 
|-
 
|-
|| [mailto:bpech1@? Brian Pech] ?    ||||||||||||||x||||||||||1
+
|| [mailto:jim.kretz@samhsa.hhs.gov Jim Kretz] SAMHSA ||1||2||3||4||5||6||7||x||9||10||11||12||1||.
 
|-
 
|-
|| [mailto:mscrimshire@gmail.com Mark Scrimshire] ?    ||||||||||||||||||||x||||1
+
|| [mailto:joe.lamy@aegis.net Joe Lamy] Aegis  ||1||2||3||4||5||6||7||x||9||10||11||12||1||.
 
|-
 
|-
|| [mailto:vvasiltsov@cagh.org Vladimir Vasiltsov] CAGH    ||||||||||||||||||||x||||1
+
|| [mailto:JohnMoehrke@gmail.com John Moehrke] VA  ||1||2||3||4||5||6||7||x||9||10||11||12||1||.
 
|-
 
|-
|| [mailto:huynhz@amazon.com Huy Huynh] Amazon    ||||||||||||||||||||x||x||2
+
|| [mailto:mlynda.owens@cognosante.com M'Lynda Owens] Cognosante  ||1||2||3||4||5||6||7||x||9||10||11||12||1||.
 
|-
 
|-
 
|| [mailto:]    ||1||2||3||4||5||6||7||8||9||10||11||12||13||.
 
|| [mailto:]    ||1||2||3||4||5||6||7||8||9||10||11||12||13||.
Line 729: Line 528:
 
|| [mailto:daniel.laupheur@mckesson Daniel Laupheur] McKesson   
 
|| [mailto:daniel.laupheur@mckesson Daniel Laupheur] McKesson   
 
|-
 
|-
|| [mailto:bryn@databaseconsultinggroup.com Bryn Rhodes] ESAC  
+
|| [mailto:bryn@databaseconsultinggroup.com Bryn Rhodes] ESAC   ||1||x||3||4||5||6||7||8||9||10||11||12||1||.
 
|-
 
|-
 
|| [mailto: Martin Rosner]     
 
|| [mailto: Martin Rosner]     
Line 741: Line 540:
 
|| [mailto: Artem Sopin]     
 
|| [mailto: Artem Sopin]     
 
|-
 
|-
|| [mailto:djorgenson@inpriva.com Don Jorgenson] Inpriva   
+
|| [mailto:djorgenson@inpriva.com Don Jorgenson] Inpriva  ||1||2||x||4||5||6||7||8||9||10||11||12||1||.
 
|-
 
|-
 
|| [mailto:andy.bond@nehta.gov.au Andy Bond] NEHTA  
 
|| [mailto:andy.bond@nehta.gov.au Andy Bond] NEHTA  

Latest revision as of 23:09, 26 January 2017

DRAFT 2017 January Working Group Meeting - San Antonio, TX - SOA WORKING GROUP

Service Oriented Architecture (SOA) WORKING GROUP SESSIONS

Back to SOA Wiki: Meetings

Agenda and Meeting Minutes

Day Date Qtr Time AGENDA ITEMS Session Leader Room
SUN JAN 15 Q1 9:00-10:30 No Meeting .
Q2 11:00-12:30 No Meeting .
Q3 1:45 -3:00 No Meeting .
Q4 3:30 -5:00 No Meeting .
MON JAN 16 Q1 9:00-10:30 No Meeting .
Q2 11:00-12:30 No Meeting .
Q3 1:45 -3:00 Workgroup Overview / HSSP Intro / New Attendee "Jumpstart"
  • Provides overview of the workgroup, mission, charter, objectives, current work, etc.
  • Intended for all audiences.
  • Review of new HSSP Process Document (if time allows)
SOA Regency East #2
Q4 3:30-5:00 "Round Robin" Project Updates

Each active project collaborating with SOA will provide a 5-10 minute update on their current status and activities planned for the week. This is the best quarter to attend to receive an overview of all SOA-related work across all projects.

  • New HSSP cover page
  • PASS Access Control
  • PASS Audit
  • Clinical Decision Support on FHIR
  • Cross-Paradigm Interoperability Project Update
  • Coordination of Care Service - Tech Spec Status
  • Ordering Service - RFP Update
  • Event Notification/Escalation Service
  • HL7 Cloud Planning Guide Document
  • Pub/Sub Service
  • FHIR Connect-a-thon
  • SOA on FHIR
  • Scheduling/Resource Management Service
SOA Regency East #2
TUE JAN 17 Q1 9:00-10:30 Joint With FHIR Infrastructure (confirmed)
  • SOA specification within FHIR
SOA Chula Vista
Q2 11:00-12:30 Joint w/ Patient Care and Patient Administration (Confirmed)
  • Care Coordination Discussion
  • Scheduling Service Discussion
  • Other items of interest to SOA, PC, and PA
SOA Chula Vista
Q3 1:45-3:00 Patient Administration (Confirmed)
  • Scheduling Service Work Session
SOA Chula Vista
Q4 3:30 - 5:00 Ordering Service Work Session
  • Walkthrough of ordering service technical specification work,
  • Relationship to FHIR workflow activities,
  • State of OMG submissions,
  • Review and contribute to current documents
SOA Chula Vista
Q5 Open Source Birds of a Feather
  • Kick off and chartering of the new work group
  • One of the initial projects will be to realize implementation of HSSP services as part of an HSPC platform implementation project.
SOA Rio Grande Center
WED JAN 18 Q1 9:00-10:30 Split meeting

1. Joint w/EHR, Security, CBCC, SOA, FHIR

  • See EHR Agenda for topics Electronic Health Records Hosting

________________________

2. Scheduling Service Continuing discussion (?)

  • TBD


  • EHR
  • SOA
  • Rio Grande East
  • Live Oak
Q2 11:00-12:30 Joint w/Security and CBCC (confirmed)
  • Joint SOA/Security Projects and concerns.
    • Projects of joint concern (TBD)
    • SLS PSS
    • PASS Audit Ballot Reconciliation
      • Provenance and Audit
        • Expand scope to include provenance. and/or
        • Do a connectathon for audit & provenance leading to an implementation guide?
SOA Live Oak
Q3 1:45 -3:00 HSSP Reference Architecture or Cloud Planning Work Session
  • TBD
SOA Live Oak
Q4 3:30 -5:00 Cloud Planning Work Session
  • TBD
SOA Live Oak
THU JAN 19 Q1 9:00-10:30 Co-chair meeting?
  • Administrative issues
SOA Live Oak
Q2 11:00-12:30 TBD
  • TBD
SOA Live Oak
Q3 1:45 - 3:00 No Meeting .
Q4 3:30 - 5:00 No Meeting .
FRI JAN 20 Q1 9:00-10:30 No Meeting .
Q2 11:00-12:30 No Meeting .
Q3 1:45 -3:00 No Meeting .
Q4 3:30 -5:00 No Meeting .


Q1=9:00 – 10:30 am; Q2=11:00 – 12:30 pm; Q3=1:45 – 3:00 pm; Q4=3:30 – 5:00 pm

Back to SOA Wiki: Meetings

Business Meeting
Technical Meeting

Meeting Minutes Draft

Back to SOA Wiki: Meetings


MON Q3

- See Attendees Section below
  1. Workgroup Overview / HSSP Intro / New Attendee "Jumpstart"
    • Provides overview of the workgroup, mission, charter, objectives, current work, etc.

Mon Q4

- See Attendees Section below 
  1. Welcome and Introductions:
  2. Agenda Review
  3. Review and approval of previous WGM minutes
  4. Round Robin updates
    • PASS Access Control: Publication package complete. Waiting on confirmation from ANSI that spec has been published.
    • PASS Audit: Ballot complete.
    • Clinical Decision Support on FHIR:
    • Cross-Paradigm Interoperability Project Update: Work is complete. Stefano to follow-up on reconciliation package and publication.
    • Coordination of Care Service - Tech Spec Status: Next submission date is set for mid-February and will be reviewed in March. Looking at late 2017 for the adoption of the technical spec.
    • Ordering Service: Initial submission happened in Dec 2016. Revised submission will happen in Feb 2017.
    • HL7 Cloud Planning Guide Document: Reviewing the PSS and making sure that the scope makes sense for HL7 to publish. Looking at possibly coordinating with HSPC. Will vote on the joint proposal Wed Q3. Will put in an NIB for May 2017.
    • Pub/Sub Service: Still need to review with OMG. Move forward with the STU extension. Action to be taken by Emory.
    • Unified Communications Service: Write up an RFC (to be decided this quarter). Moving forward with the STU extension. Action to be taken by Emory.
    • FHIR Connect-a-thon: General purpose guidance for Clinical Reasoning Module. Had several participants. Scenario: Apply an order template for a specific patient. FHIR clinical reasoning CDS Service for Zika infection management. Created a clinical reasoning decision artifact. Incorporated in the an end-user experience Epic implementation that can return recommendations. Click here for full presentation.
    • HSSP Process Guide (SOA on FHIR): Ken wrote up a document, "HSSP Standards Development Process" to outline how to incorporate FHIR into SOA specifications as well as update the overall HSSP process. Detailed discussion will continue Tuesday Q1.
    • Scheduling/Resource Management Service:
    • All Hands meeting schedule and attendance:

TUE Q1

- See Attendees Section below 
  1. Joint With FHIR Infrastructure (confirmed)
    • SOA specification within FHIR:
      • Began by re-capping what was done at the last WGM. Went through the SOA-FHIR Process PPT.
      • CDS is blazing the trail. Looking at Ordering service and Scheduling service to actually test the process as outlined in the document. Targeting FHIR STU 4 for incorporating FHIR into these standards.
      • Another standard which may be incorporating a FHIR section is PASS SLS.
      • Ken shared the HSSP process document. Sean - have we reviewed any of the FHIR IGs? Ken - no but it is on our radar. Joshua - Tool is IG publisher, the US Core IG would be the place to start. Joshua likes the requirement for implementation in the OMG process. The IG publisher tool is available on the FHIR webpage.

Joshua - is there a group that we can point to who will be implementing this process. Ken - in theory, Scheduling will be doing this. They are very open to doing this process. Joshua - Good. This is the first we've heard of this type of process being implemented. Don - Are there any other projects that are doing this and are there any projects that FHIR is aware of that would fit this model? Joshua - The main one that came to my mind was Scheduling so I'm glad to hear that is happening. Ken - CDS on FHIR is fairly mature already but they may bring some in retroactively.

Ken - under this process the SFM doesn't go away. Provides a bridge with what we do today. We want to make sure that as we do new services, they fit well with the existing specs.

Specific actions: Ken would like a peer review of this process document from a FHIR perspective. Who would be willing to do this?

Action Item Joshua - Lloyd put out an email asking if folks need help. If that doesn't result in a good response, then I am willing to do the review. Ken - That is good for the process doc review. Another issue is how to do the 6 objectives that would be consistent for all SOA specifications (such as naming conventions, etc...). What would that look like.

Action Item - Ken to send a note to Joshua(?) or the FHIR Infrastructure for help in creating SOA specific templates.

Timeframe? Joshua - probably after STU 3. Ken - Since Bryn put his hand up, that may be fine. Diana - hopefully we can get some feedback on the process document.

HSSP Process Document

TUE Q2

- See Attendees Section below 
  1. Changed from Joint with Patient Care to Reference Architecture discussion.

Need to flesh out the RA to make it useable.

Can we visualize this starting with the FHIR workflow and then identify the differences when approaching from an SOA point of view.

Action Item - Need to add Orchestration Service and Workflow service to the diagram.

Did a preliminary sequence diagram for the RA.

  1. Patient Care
    • Status - reopened the letter of intent until December but had no takers. It is now closed. Interest from LSU and they are offering one of their hospitals as a possible test bed. Next submission date is for the March OMG meeting.

Ken - VA is doing work about workflow and care teams, transitions within and between care teams. Right now what is in FHIR care teams resources is falling short of what VA needs. This is an angle for coordination of care. Need to know the structure and high-level thinking in order to get it into the spec.

Laura - ONC started calls on care teams on Fridays. PC owns care teams as a steward and are really working through some of the issues. There is an outstanding question regarding if this needs to be pulled into HL7 PC.

For Madrid - Set up a joint meeting with PC Tuesday at Q2.

TUE Q3

- See Attendees Section below 
  1. Patient Administration (Confirmed)
    • Scheduling Service Discussion:
      • gForge items
      • Structure of slot
      • Methodology Status
        • Ken - seems like folks have a handle on the FHIR stuff but the SFM process is a bit opaque. Ken presents the HSSP Process document. Hope is to get 3 or 4 folks (Brian Postlethwaite, Bryn Rhodes, and Dave Carlson) who know both Scheduling and FHIR to work through the process and identify issues with the process and help refine it. Cooper - Trying to understand how this is going to work in the current way of doing things. Brian/Andrew: we may build something faster than this process will allow. Ken - may have to do this iteratively where we start with a "pre-alpha" product. Where we came out of the Baltimore meeting having identified the service specification package which includes 6 elements (listed in the HSSP process document). In the short-term, will work with what we have in STU3 but we don't want to do anything that will interfere with the use of STU4.
        • Andrew: we will start building stuff before STU3 even due to demand. We will be harmonizing with upcoming STU3 and then 4 work.
      • Status of specification
        • Ken - see if I can get more involvement on the VA side. HSPC may have some providers that would be interested in this project. Cooper: we had more folks coming but we haven't done a good job of pulling in all folks who have expressed an interest. Ken: It helps to have something "half-baked" before bringing in the folks on your list.
        • Encounter has been cleaned up. Appointment has similar issues with cardinality. In the process of cleaning up. Need to open up the cardinality to 0..*. The reason for the appointment may not be declared at the time of the scheduling of the appointment. Ken - suggesting that there should be a primary reason and then secondary reasons as this can affect the equipment needed and even the location of the appointment. When at HP, they had some pretty mature scheduling analysis work. If we think that would be useful, I can reach out to HP and see if they are willing to release the information to HL7.
      • FHIR STU4 Discussion: Goal is to have a substantial scheduling service available for STU4.
        • There is some workflow portability work that is happening elsewhere that could be brought in here. STU4 is a working goal.

vote: 14/0/2 to support the 9262 FHIR change request for the Appointment resource. Recommendation: PA create a split meeting for this quarter where PA can only send the folks who are interested.

TUE Q4

- See Attendees Section below 
  1. Ordering Service Work Session
    • Walkthrough of ordering service technical specification work,
    • relationship to FHIR workflow activities,
      • Catalog resource is being proposed for FHIR. Ordering Service SFM was expanded to incorporate the FHIR Catalog resource. FHIR workflow hasn't really pulled in anything from Ordering Service or FHIR Catalog. The OMG submission consists of the Ordering Service Technical submission which incorporates Order Management and Catalog Management. The FHIR Workflow has 6 architectures but most of what they have currently aren't workflows.
    • state of OMG submissions
      • took to OMG in Dec 2016 and is available for review at https://healthservices.atlassian.net/wiki/display/WGS/HSPC+OMG+Ordering+Service+RFP+WG
      • The OMG prefers the normative version to be the UML model. Claude is working on the ordering front. Hoping the final submission would be in March but finding that to be a bit ambitious.
      • Fleshed out Order Proposal Handling and Order WorkFlow. Updated OrderQuery. Trying to be compliant with SOAP (FHIR) and RestFul implementations (requirement of RFP). OMG requires both PIMs and PSMs. Currently working on the PIM. Ordering as a domain is dynamic. Have is set up using encapsulation to allow for flexibility. The Main Order Entities model is to undergo major revision to reduce confusion due to state changes that were only implicit and terms that are too similar. In OO, they tried to take a diagnostic order and go through the workflow. Need to be able to associate a workflow with an item. What is inside the workflow may change depending on the implementation. Also need an ordering service that may or may not plug into a fulfillment service.
      • Recommended approach: Work the specification and submit. Later, bring in the FHIR implementation and then put out an RFC.

Action Item: Jerry Goodnough to reach out to Jonathan Nebeker about providing resources for this project.

WED Q1: Split meeting

  1. Joint w/EHR, Security, CBCC, SOA, FHIR (See EHR for meeting minutes)
- attendees:
  1. Cancelled

WED Q2

- See Attendees Section below

Project updates:

  1. Cloud Planning Guide
    • Consistent group meeting and advancing the work. May target.
    • Identifying areas where HL7 standards have particular relevance; security a key area of interest
  2. “SOA on FHIR”
    • Has been a SOA priority; have a much better perspective on how to do that now
    • Producing a collective set of FHIR artifacts templated to SOA
    • Working in collaboration with FHIR Infrastructure Group
  3. Security Labeling Service PSS
    • New project scope statement to build upon existing SLS work
    • Re-envision to align work to FHIR; building on SOA on FHIR activities
      • Some discussion about the role of SLS as applied to FHIR. Not self-evident how they fit together;
      • API is content specifying but content agnostic
      • Discussion and questions about the role of SLS and persistence of Security Labeling in FHIR
      • Questions about whether a dedicated FHIR section should be added to the document
      • 1138 CST: Mike Davis agreed with John Moehrke on Project scope wording re: FHIR
      • SLS to address how to inspect FHIR objects
      • Motion to Accept PSS (Kathleen Connor) Second (Mike Davis). Passed (14-0-4)

WED Q3/Q4

- See Attendees Section below
  1. Reference Architecture: Work on it Thursday, Q2.
  2. Cloud discussion
    • Vadim presented a proposed simplification of the scope of the document. Proposing that we start with high-level, universal concerns that come up when looking at a cloud implementation.
    • In answer to the question, why do this, Ken suggested these bullet points:
      • HL7 does a lot of implementation guides, and did not have presence in the cloud space.
      • Many HL7 standards are being implemented using cloud platforms.
      • In conjunction with HSPC, we are addressing what has been a significant gap in the industry.
    • Proposal - Finish going through Vadim's presentation and then take a first pass at the Phase 2 content and that might be as much as we get through for the May ballot.
    • Who is our audience? One possibility is IT folks talking to Managers and needing a resource regarding which addresses their concerns. For the newbie, it's education and ramp-up, for the expert - it's legitimization or substantiation, for the intermediate - it's validation.
    • Motion: Approach HSPC about making this a joint collaborative effort subject to HL7 and HSPC board agreement. Ken made motion, Vadim seconded. 5/0/0
    • Action Item - Ken will approach HSPC regarding above motion.
  3. SOA Platform - Phase 2
    • Awareness of HL7 portfolio
      • SOA
      • FHIR
    • Reference implementation examples (Reference Architecture diagram if we have a deployment diagram showing how the cloud and HL7 worlds fit using the HSPC platform container model.)
    • Bring in responses to survey to legitimize why these services are valuable.
  1. Reference Architecture discussion
    • MDMI isn't a service. There should be a different color for supporting specifications that aren't services.
    • Want to extend the current Reference Architecture diagram by diagramming out a use case which accesses multiple services.
      • Possible use case - Payor (insurance), Eligibility, Patient Care Lifecycle (Continuity of care, transfer of care from inpatient to outpatient & long-term care/physical therapy.)

Thurs Q1

- See Attendees Section below 
  1. Co-chairs met to discuss plans for Madrid.
  2. Co-chairs agreed to meet on a monthly basis in order to identify direction for future work in SOA.

Thurs Q2

- See Attendees Section below
  1. Identified a Care use case scenario and created a sequence diagram showing the SOA services interacting in order to complete the steps of the scenario.

Patient Care Referral Scenario

Attendees

SOA Attendee 1 MON Q3 2 MON Q4 3 TUES Q1 4 TUES Q2 5 TUE Q3 6 TUE Q4 7 WED Q1 8 WED Q2 9 WED Q3 10 WED Q4 11 THU Q1 12 THU Q2
Ken RubinSOA Co-Chair/VA x x x x x x 7 x x x x 12 10 .
Diana Proud-MadrugaSOA Co-Chair/VA 1 x x x x x 7 x x x x x 11 .
Vincent McCauley SOA Co-Chair/Telstra Health
Stefano Lotti SOA Co-Chair x x x x x x 7 x x x x x 12 .
Dave Carlson Book Zurman 1 2 x 4 5 6 7 8 9 10 11 12 1 .
Lorraine Constable Constable Consulting 1 2 x 4 5 x 7 8 9 10 11 12 2 .
Jerry Goodnough Cognitive Med. Sys. x x 3 4 x x 7 8 x x 11 x 7 .
Mohammad Jafari VA
Preston Lee VA, Arizona State University
Ken Lord VA
Dan Morford Book Zurman
Sean Muir VA x 2 x 4 5 6 7 8 9 10 11 12 2 .
Vadim Polyakov Inovalon x x x x x x 7 8 x x 11 12 8 .
Chris Shawn VA 1 2 3 4 5 6 7 x 9 10 11 12 1 .
Trish Williams Edith Corvan Univ
Duane DeCouteau VA 1 2 3 4 5 6 7 x 9 10 11 12 1 .
Mike Davis VA 1 2 3 4 5 6 7 x 9 10 11 12 1 .
Johnathan Coleman ONC
Hideyuki Miyohara HL7 Japan 1 2 3 4 5 6 7 x 9 10 11 12 1 .
Josh Mandel Children's Harvard 1 2 x 4 5 6 7 8 9 10 11 12 1 .
Kevin Shekleton Cerner
Laura Heermann Intermountain Healthcare 1 2 3 4 x 6 7 8 9 10 11 12 1 .
Emma Jones Allscripts
Claude Nanjo Cognitive
Juha Mykkanen HL7 Finland/National Institute for Health and Welfare (THL) Finland
Bryn Lewis Intelsoft
Manoj Sharma Allscripts
Chana West ESAC Inc.
Kevan Riley Infor (?)
Zach May ESAC Inc.
Rashedul Hasan FDA
Cooper Thompson Epic 1 2 3 4 x 6 7 8 9 10 11 12 1 .
Karl Holzer CGM
Oliver Krauss University of Applied Science Upper Austria
Alexander Mense HL7 Austria 1 2 3 4 5 6 7 x 9 10 11 12 1 .
Grahame Grieve
Victor Harrison OMG
Emory Fry Cognitive x x 3 4 5 x 7 8 9 10 11 12 3 .
Elizabeth Newton KP
Gora Datta ?
[mailto: Kathleen Connor] VA 1 2 3 4 5 6 7 x 9 10 11 12 1 .
Andrew Statler Cerner
Brian Pech ?
Mark Scrimshire ?
Vladimir Vasiltsov CAGH
Huy Huynh Amazon
Craig Knier McKesson x x 3 4 5 6 7 8 9 10 11 12 2 .
Adamu Haruna Nokia x 2 3 4 5 6 7 8 9 10 11 12 1 .
Chris Grear Analysts 1 x 3 4 5 6 7 8 9 10 11 12 1 .
Kent Lemoine CDC 1 2 x 4 5 6 7 8 9 10 11 12 1 .
Rene Kinsey VA 1 2 x 4 5 6 7 8 9 10 11 12 1 .
Sam Mater Epic 1 2 3 x x 6 7 8 9 10 11 12 2 .
Shuai Zheng CDC 1 2 3 x x x 7 8 9 10 11 x 4 .
Tracy Angeles Conduent 1 2 3 4 x 6 7 8 9 10 11 12 1 .
Alex DeLeon Kaiser Permanente 1 2 3 4 x 6 7 8 9 10 11 12 1 .
Irma Jongeneel HL7 Netherlands 1 2 3 4 x 6 7 8 9 10 11 12 1 .
Wes Rishel Self 1 2 3 4 x 6 7 8 9 10 11 12 1 .
Andrew Torres Cerner 1 2 3 4 x 6 7 8 9 10 11 12 1 .
Brian Postlethwaite Telestra Health 1 2 3 4 x 6 7 8 9 10 11 12 1 .
Simone Hickmann HL7 Germany 1 2 3 4 x 6 7 8 9 10 11 12 1 .
Biru Yang Houston Health Dept 1 2 3 4 x 6 7 8 9 10 11 12 1 .
Truc Pham Houston Health Dept 1 2 3 4 x 6 7 8 9 10 11 12 1 .
Ali Momin Houston Health Dept 1 2 3 4 x 6 7 8 9 10 11 12 1 .
Suzanne Gonzales-Webb VA 1 2 3 4 5 6 7 x 9 10 11 12 1 .
David Pyke Ready Computing 1 2 3 4 5 6 7 x 9 10 11 12 1 .
Jim Kretz SAMHSA 1 2 3 4 5 6 7 x 9 10 11 12 1 .
Joe Lamy Aegis 1 2 3 4 5 6 7 x 9 10 11 12 1 .
John Moehrke VA 1 2 3 4 5 6 7 x 9 10 11 12 1 .
M'Lynda Owens Cognosante 1 2 3 4 5 6 7 x 9 10 11 12 1 .
[mailto:] 1 2 3 4 5 6 7 8 9 10 11 12 13 .
[mailto:] 1 2 3 4 5 6 7 8 9 10 11 12 13 .
[mailto: Steve Hufnagel]
[mailto: Raheem Daya] McKesson
[mailto: Shane Loney] McKesson
Greg Gustafson Penrad
Daniel Laupheur McKesson
Bryn Rhodes ESAC 1 x 3 4 5 6 7 8 9 10 11 12 1 .
[mailto: Martin Rosner]
[mailto: Yunwei Wang]
[mailto: Maxim Abramsky]
[mailto: Raphael Majeed]
[mailto: Artem Sopin]
Don Jorgenson Inpriva 1 2 x 4 5 6 7 8 9 10 11 12 1 .
Andy Bond NEHTA
Robert Bishop VA
Nancy Orvis DoD
Russell Ott Deloitte