• Created by Unknown User (nikolas.reineke), last modified on Sep 29, 2016

The Direct Transport SWG meetings are cancelled until further FHIR profile development work is completed.

Scope

A community-led sub-workgroup that will work to explore Direct as a candidate standard for transporting queries for the Data Access Framework (DAF)


Meeting Details

N//A


Materials

1) Data Access Framework Homepage
2) Launch Presentation from Monday, May 5, 2014
3) DAF/Direct Design Prototype Submitted by Joel Ryba
4) DAF Targeted Use Case
5) Statement of Principles Document for MU2 Transitions of Care
6) DAF DIRECT Components Updated 5/20/14
7) Example of a Simple Schema and Instance for a DAF request using XML
8) DAF over Direct Query Flow 1.4 (update loaded 6/24/14)
9) DAF Request in SOAP wrapped IHE Style XML for transport over Direct
10) DAF over Direct Voting Issues for consideration, updated 6/30/14
11) Example of Data Element Query Parameters submitted 7/7/14
Discussion during the 7/7/14 meeting by Dr. Steve Beller: I presented the Example of Data Element Query Parameters spreadsheet during the today's meeting as an example of one possible way to deliver data element queries via Direct. It's purpose is to address our simplest use case, i.e. human readable parameters for manual query without use of web services. The example is based on a QueryHealth prototype he developed a couple of years ago for the complex NQF 0059 quality metric query. It includes the query parameters and related value sets. The feedback was mixed; some liked it, but others expressed concern that it is so different than what the DAF Data Elements WG is doing as to require a new standard. I will attend the next Data Elements WG and see if & how we can adopt the approach they are working on.
- Update on 7/11/14: Having attended the 7/9 DAF Data Elements WG and listened to the 7/2 meeting, I have some insights and ideas regarding an approach to delivering query parameters for the Basic use case, i.e., Simple SMTP DIRECT for manual queries without XDM. I uploaded a proposal in a Word file at this link. I'll be back in two weeks to discuss, but welcome and comments in the mean time. - Steve
12) Vimeo recording of the July 7, 2014 meeting - Examined the proposed query parameters structure for the "Complex" use case for document based queries.
13) Vimeo recording of the July 28, 2014 meeting - Examined the proposed query parameters structure for the "Basic" use case for data element based queries.
- Follow-up to the 7/28 meeting: Dr. Beller updated the proposal to include issues discussed during the meeting and to provide an concrete example of the proposed Basic query parameters structure. The updated proposal is at this link - DAF over DIRECT Basic Use Case proposal 20140731.docx
14) Vimeo recording of the Aug 4, 2014 meeting - Examined a concrete example of the proposed Query Parameters Definition Grid for the data element query Basic use case and discussed related issues
- Follow-up to the 8/4 meeting: Dr. Beller updated his proposal document to include issues discussed during the meeting, including refining the definition of the Basic data element use case, as well as discussing the DAF charter scope and suitability of FHIR for that use case. The updated proposal is at this link - DAF over DIRECT Basic Use Case proposal 20140805.docx
- Follow-up to the 8/7 Main DAF meeting: After presenting the Basic use case to the Main WG, the community generally agreed that the Basic use case in a "worthy" whose need ought to be addressed. Dr. Beller explained that the reason it is not currently addressed by DAF charter is because the initial focus of DAF was on using web services for automated queries (the "Complex" use case) and thus the Basic use case was not even a consideration. Once the DAF over Direct SWG began, however, we were able to examine Direct's unique capabilities and found that it could address the Basic use case (as well as the Complex one). Since time ran out before we could come to a decision about expanding the scope to include both use cases, the discussion will continue next week.
15) During the 8/13/2014 Main DAF meeting, Dr. Beller's Basic use case data element proposal was determined to be out of scope, while Joel Ryba's Document level proposal was determined to be in-scope. The day following the meeting, a new e-mail thread further clarified what made the Basic proposal out of scope and opened up discussion a discussion of the importance of having transparency in the DAF process so that responders would know what will be queried. During the email discussion, Dr. Beller presented a new proposal for the Direct data element query based on a transparent process and there was general agreement that it would be in scope. He offered to present additional details in a DAF over Direct meeting in mid-Sept. Also discussed was whether the SWG should over then next few weeks while work is done offline by the Main WG on the DAF FHIR profile.
16) On the 9/15/14 meeting, it was agreed that the DAF FHIR profile being developed by the main DAF WG will be used by the SWG as well. After next week's meeting, the SWG will go on hiatus until the main WG completes the FHIR profile.
  • No labels