HL7 WMG and Plenary, Sept 2016, Baltimore
- 1 DRAFT 2016 September Working Group Meeting - Baltimore, Maryland - SOA WORKING GROUP
- 2 Agenda and Meeting Minutes
- 3 Meeting Minutes Draft
DRAFT 2016 September Working Group Meeting - Baltimore, Maryland - SOA WORKING GROUP
Service Oriented Architecture (SOA) WORKING GROUP SESSIONS
Agenda and Meeting Minutes
|Day||Date||Qtr||Time||AGENDA ITEMS||Session Leader||Room|
|SUN||MAY 08||Q1||9:00-10:30||No Meeting||.|
|Q3||1:45 -3:00||No Meeting||.|
|Q4||3:30 -5:00||No Meeting||.|
|MON||SEP 19||Q1||9:00-10:30||No Meeting||.|
|Q3||1:45 -3:00|| Workgroup Overview / HSSP Intro / New Attendee "Jumpstart"
||SOA||Guest Room 317|
|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.
|SOA||Guest Room 317|
|TUE||SEP 20||Q1||9:00-10:30||Joint With FHIR Infrastructure (confirmed)
||SOA||Guest Room 317|
|Q2||11:00-12:30||Joint w/ Patient Care (Confirmed)
||SOA||Guest Room 317|
|Q3||1:45-3:00||Patient Administration (Confirmed)
||SOA||Guest Room 317|
|Q4||3:30 - 5:00||Ordering Service and X-Paradigm Interop Discussions
||SOA||Guest Room 317|
|Q5||Birds of a Feather||
|WED||SEP 21||Q1||9:00-10:30 Split meeting||
1. Joint w/EHR, Security, CBCC, SOA, FHIR
2. Scheduling Service Continuing discussion
|Q2||11:00-12:30||Joint w/Security (confirmed)
|Q3 / Q4||1:45 -3:00 / 3:30 -5:00||Refresh of Service Functional Model specification process in the world of FHIR.
|THU||SEP 22||Q1||9:00-10:30||HL7 Cloud Planning Guide Work session
||SOA||Guest Room 317|
||SOA||Guest Room 317|
|Q3||1:45 - 3:00||No Meeting||.|
|Q4||3:30 - 5:00||No Meeting||.|
|FRI||SEP 23||Q1||9:00-10: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
Meeting Minutes Draft
- Workgroup Overview / HSSP Intro / New Attendee "Jumpstart"
- 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.
Ken: The containerization and
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?
- attendees: 10
- Welcome and Introductions: Went around and introduced ourselves
- Agenda Review, approval 10 attendees: Passed unanimously
- Round Robin updates
- New HSSP cover page: Vincent displayed the new cover page on the HSSP.
- PASS Access Control: Diana - Ballot reconciliation package has been uploaded. Will vote on to bring this to publication this week.
- 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: (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: 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: 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 - 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.
- Event Notification/Escalation Service: EPS and Unified Communication Service? Jerry isn't sure what is meant by this.
- 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.
- 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.
- 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.
- 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.
- SOA on FHIR: This is going to be Q3-4 on Wednesday. Have some concrete proposals based on discussions between Graham and Ken.
- 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.
- attendees: 12
- 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.
The SOA specification pre-dated FHIR. Question is how we bridge that gap? Question are we creating APIs that can interface with FHIR or do we create FHIR APIs. How do we bring the two worlds together? How do you make the bridge btwn functional and behavioral? 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
What's available in FHIR (three pillars): PUB/SUB Operations
looking at the order service and the order resource in FHIR, what is the relationship. Jerry: simple question without a simple answer. 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.
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.
We will have a joint meeting between SOA and FHIR-I at the January WGM. Diana will make that invitation.
- Joint w/ Patient Care (Confirmed)
- 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.
- 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 - Ken updated Patient Care on where this project is with OMG.
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.
- 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.
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? Decision: Kill the current project and explore other options if we want to resurrect the project.
- attendees: 7
- Patient Administration (Confirmed)
- Scheduling Service Discussion: Finished up the PSS for scheduling service.
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
Cooper was asked about making the joint meeting Tues Q2 to include Patient Care and Patient Administration. Keep Tues Q3 as joint with PA.
- attendees: 8
- Ordering Service Discussion
- Walkthrough of ordering service technical specification work,
- relationship to FHIR workflow activities, and
- state of OMG submissions
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.
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.
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.
- 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
- Joint w/EHR, Security, CBCC, SOA, FHIR (See EHR for meeting minutes)
- Scheduling Service Continuing discussion
- Joint SOA/Security Projects and concerns.
- PASS ACS vote to request publication
- HL7 Cloud Planning Guide Overview
- PASS Audit
- attendees: 13
- Refresh of Service Functional Model specification process in the world of FHIR.
- 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.
Created a preliminary SOA process ppt for working with FHIR.
HL7 OMG vote is a lever we can use.
Grahame moved. Jerry seconded. Motion to accept the process as discussed and described in the SOA-FHIR Process PPT. Passed 12/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.
FHIR implementations can start before the STU is balloted.
Action item: Need to think through how we engage the community, eg. through the FHIR connectathon process.
Vic: One possibility is to specify test specs for the developers/implementers. Ken: There is no shortage of, or consistency of, test specs. I (Ken) don't want to take that on at this point.
Update on OMG: 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. 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.
- attendees: 9
- HL7 Cloud Planning Guide Work session
- Presentation on Amazon Web Services by Huy H.
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
- 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.
- 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.
- Cloud Planning Guide Survey
- Develop a Cloud blueprint sample
- Flesh out draft document
- Hot Topics
|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||12||13|
|Ken RubinSOA Co-Chair/VA||x||x||x||x||x||x||x||x||x||11||12||13||.|
|Diana Proud-MadrugaSOA Co-Chair/VA||x||x||x||x||x||x||x||x||x||x||11||12||13||.|
|Vincent McCauley SOA Co-Chair/Telstra Health||x||x||x||x||x||x||x||x||x||x||11||12||13||.|
|Stefano Lotti SOA Co-Chair|
|Vadim Polyankov Inovalon||x||x||x||x||x||x||7||x||x||10||11||12||13||.|
|Dan Morford Book Zurman||x||7||8||9||10||11||12||13||.|
|Dave Carlson Book Zurman||x||7||8||x||10||11||12||13||.|
|Sean Muir VA||7||8||x||10||11||12||13||.|
|Andy Bond NEHTA||7||8||9||10||11||12||13||.|
|Robert Bishop VA||7||8||9||10||11||12||13||.|
|Nancy Orvis DoD||7||8||9||10||11||12||13||.|
|Russell Ott Deloitte||7||8||9||10||11||12||13||.|
|Trish Williams Edith Corvan Univ||x||8||9||10||11||12||13||.|
|Jerry Goodnough Cognitive Med. Sys.||x||x||x||x||x||x||7||x||x||10||11||12||13||.|
|Chris Shawn VA||x||8||9||10||11||12||13||.|
|Duane DeCouteau VA||x||8||9||10||11||12||13||.|
|Mike Davis VA||x||8||9||10||11||12||13||.|
|Johnathan Coleman ONC||7||8||9||10||11||12||13||.|
|Don Jorgenson Inpriva||7||8||9||10||11||12||13||.|
|Hideyuki Miyohara HL7 Japan||x||8||9||10||11||12||13||.|
|Josh Mandel Children's Harvard||x||7||8||9||10||11||12||13||.|
|Kevin Shekleton Cerner||x||7||8||9||10||11||12||13||.|
|[mailto: Yunwei Wang]||7||8||9||10||11||12||13||.|
|[mailto: Maxim Abramsky]||7||8||9||10||11||12||13||.|
|[mailto: Raphael Majeed]||7||8||9||10||11||12||13||.|
|[mailto: Artem Sopin]||7||8||9||10||11||12||13||.|
|Laura Heermann Intermountain Healthcare||x||7||8||9||10||11||12||13||.|
|[mailto: Martin Rosner]||7||8||9||10||11||12||13||.|
|Emma Jones Allscripts||x||x||7||8||9||10||11||12||13||.|
|[mailto: Steve Hufnagel]||6||7||8||9||10||11||12||13||.|
|[mailto: Raheem Daya] McKesson||6||7||8||9||10||11||12||13||.|
|[mailto: Shane Loney] McKesson||6||7||8||9||10||11||12||13||.|
|Claude Nanjo Cognitive||x||6||7||8||9||10||11||12||13||.|
|Lorraine Constable Constable Consulting||x||x||7||8||x||10||11||12||13||.|
|Greg Gustafson Penrad||6||7||8||9||10||11||12||13||.|
|Daniel Laupheur McKesson||6||7||8||9||10||11||12||13||.|
|Bryn Rhodes ESAC||7||8||9||10||11||12||13||.|
|Preston Lee VA, Arizona State University||x||x||x||x||7||8||9||10||11||12||13||.|
|Ken Lord VA||x||x||5||6||7||8||x||x||11||12||13||.|
|Juha Mykkanen HL7 Finland/National Institute for Health and Welfare (THL) Finland||x||6||7||8||9||10||11||12||13||.|
|Bryn Lewis Intelsoft||x||x||x||7||8||9||10||11||12||13||.|
|Manoj Sharma Allscripts||x||6||7||8||9||10||11||12||13||.|
|Chana West ESAC Inc.||x||6||7||8||9||10||11||12||13||.|
|Kevan Riley Infor (?)||x||6||7||8||9||x||11||12||13||.|
|Zach May ESAC Inc.||x||6||7||8||9||10||11||12||13||.|
|Rashedul Hasan FDA||x||6||7||8||9||10||11||12||13||.|
|Cooper Thompson Epic||x||x||9||10||11||12||13||.|
|Karl Holzer CGM||x||7||8||9||10||11||12||13||.|
|Oliver Krauss University of Applied Science Upper Austria||x||7||8||9||10||11||12||13||.|
|Alexander Mense HL7 Austria||1||2||3||4||5||6||x||8||9||10||11||12||13||.|
|Victor Harrison OMG||1||2||3||4||5||6||7||8||x||10||11||12||13||.|
|Emory Fry Cognitive||1||2||3||4||5||6||7||8||9||10||11||12||13||.|
|Elizabeth Newton KP||1||2||3||4||5||6||7||8||9||10||11||12||13||.|