Atlanta wgm meeting Minutes Service-oriented Architecture Workgroup

Service-oriented Architecture Workgroup

Monday, October 05, 2015

12:33 PM
Note: This session is dedicated to receiving status updates from each of the sub-projects affiliated with SOA, both to inform the broader community as to current activities, as well as to indicate when and which topics are to be addressed later within the week.
1. Balloted Unified communication service

3 DSTUs with OMG

EPS (look up)

Contracted with VA

• 
  Ordering Service
  

SOA/CDS/OO

Normally process in HSSP starts with a service functional model then go to OMG which creates a complete SOA technical spec (DSTU)

Since VA has funded this for another year, the spec will have a limited update while working out the kinks in the DSTUs.

2. PASS ACS

6 votes short of passing

Question: what is the relationship between PASS ACS and IHE ATNA Audit provisions.

Not really any convergence between ACS and ATNA but this could come into PASS Audit.

 

Cross-Paradigm Implementation Project

Map the different standards at the semantic and behavioral levels.

Semantic mapping is more advanced

DMI possible to create references that contain

Completed ballot reconciliation and are looking to complete the behavioral part of the standard.

Started as a specific implementation guide with immunization being the use case for the implementation.

Have 2 informative ballots. Thinking that the next ballot will be DSTU.

 

Cloud Blueprint

Looking to complete the PSS.

Composed FHIR Services

Has there been a presentation showing an SOA approach using FHIR?

Questions

We can use Rest as a particular kind of service.

SOA discloses business functionality. SOA is concerned with business meaningful functions. SOA has a lot of data related functions so whether it's SOA or not. It can be a little subjective.

Smart is evolving into FHIR. Allows for the development of FHIR applications on the fly.

Don: I would like to see a tool that makes sure that services using FHIR resources have what they need. So much of healthcare could be done at a system analyst level.

Business process management tool that can pull all the FHIR resources needed when defining a service.

SAHMSA's consent to share service is one possible example. (currently using CCDA 1.1 not FHIR)

One of the things that may be useful is to create an implementation guide similar to X paradigm and in working on this project we may discover a tool(s).

(need summary)

Quarter focused on two principal elements. The SOA workgroup had taken action dating back to the first FHIR DSTU ballot to harmonize what at that time were two disparate sections, one focused on “services” and the other on “service-oriented architecture” that were part of the document. Since the Paris WGM, these sections were fully integrated with that content contributed to the current DSTU publication. A review was conducted of the approach and new content, with discussion to rationalize how and why the remediation undertaken was done. The issues to resolve:

• 
  Based upon ballot comment, the prior section was too “tutorial-like” and less prescriptive
  
• 
  A lot of existing content was either rationalizing or defensive in posture
  
• 
  The prior services content was at varying levels of granularity
  
• 
  Two sections needed to be harmonized into one
  

Actions taken:

• 
  Revision of the section was done with the intention of being largely “content neutral”. While existing verbiage was edited and moved, little new original text was added, and removal of content was primarily to eliminate redundancies
  
• 
  In the prior version, three “approach styles” of bringing together of SOA and FHIR were contrasted, with each being studied independently while considering 8-10 factors. This was redone, focusing the section on the “factors” and then calling-out differences among them when there were variations among the approach styles. This resulted in a cleaner section with less redundant material
  
• 
  Tutorial and rationalization text was moved to the end of the section, instead focusing on how to bring together FHIR with SOA, and the dimensions of the problem space that SOA is able to help address. Tutorial information was substantially trimmed.
  

• 
  Specific examples of use of SOA techniques applied to FHIR (code examples) were not included in this revision, though that was an aspirational goal. Hope is to identify candidates and include example as illustrative to complement existing content for DSTU 2.1
  

Other Items:

• 
  The FHIR WG was informed about the Cloud Blueprint project (emerging). A review of the draft project scope statement was conducted, and FHIR invited to participate as a co-sponsor of the project. In brief, the Cloud Blueprint project will create an informative document to help HL7 consumer make informed decisions about how and where HL7 standards fit into a cloud implementation/migration. The emphasis will be on the intersection with existing HL7 portfolio. The effort will NOT re-create existing generic cloud implementation (e.g. virtualization, platform-as-a-service, etc.) guidance, rather referring to high-quality sources that are available.
  

Note: Ken apologized that the revised documentation did not receive customary advanced notice and review, in part from his time constraints and in part due to a problem with the HL7 listserv.

Tues Q3 SOA

Don J. Officially resigned. Diana P-M has expressed an interest in stepping in as interim co-chair.

Cloud blueprint

Use case driven

Meat of the document would be a design pattern (section 3)

Even if what we are doing isn't new and unique, this can be used as a jumping off point for healthcare organization who wants to implement a cloud solution.

Viewpoint: how does the healthcare organization need to organize

Recommend reading "Design Patterns: Elements of Reusable Object Oriented Software."

This book is a compilation of design patterns that they did write. We are looking to do something similar for cloud, compiling cloud design patterns and healthcare best practices around a healthcare cloud implementation.

Suggestion that we reach out to the mobile health WG as another possible co-Sponsor.

Looking at having this as a signed PSS within a month.

Next steps (assuming approval) (this list is on a document on the HSSP wiki) Survey HL7 members Develop the Maturity Model Collect info for primer Elaborate the target audience roles Identify short-list of blueprint contexts

use case development

Define substructure for each blueprint

Consider design patterns pattern

Bottom-up view of HL7 Standards as applied to each of the above patterns.

Look at reference Cloud architecture

Diana and Ken to work on the justification section.

Dimitrio would like a rethinking of the call times to allow for greater European participation. (Doodle poll)

Tuesday, October 06, 2015

12:32 PM

Object Management Group (OMG) RFP

• 
  Introductions
  
• 
  SOA Specifications are done in 2 parts
  
  • 
    HL7
    
  • 
    OMG (www.omg.org)
    
    • 
      OMG gets standards through the RFP process.
      
    • 
      We will be seeing two RFPs
      
    • 
      OMG meets 4x/year