90160908 OO FHIR conCall
HL7 OO on FHIR (for Orders and Observations) Call in details: |
Date: 2016/09/08 2015 - 02:00 PM (Eastern Time, GMT -04 DST) | |
Quorum = chair + 4 yes |
Co chairs | Chair | Notetaker | |
---|---|---|---|
Riki Merrick | X | ||
Rob Hausam | |||
Lorraine Constable | |||
Patrick Lloyd | |||
Ken McKaslin | |||
Hans Buitendijk |
Attendees | |
---|---|
X | Eric Haas |
X | Riki M |
Hans Buitendijk | |
X | Jose Costa-Teixicara |
Dan Rusk | |
X | Jonathan Harber |
David Burgess | |
Lloyd McKenzie | |
X | Rob Hausam |
Andrea Pitkus | |
x | Francois Marcary |
x | BobYencha |
x | Kathy Walsh |
- Roll Call
- Agenda Check
- Minutes from
- Agenda
- Culture and Susceptibility Reporting in FHIR
- See Github Wiki
- Test Catalog review
Lab Test Catalog
Logical Model based on eDOS guide and LCSD IHE profile and in future that will eventually map over to FHIR artifacts.
Discussed to identify the things that are:
- the catalog meta data
- catalog entry (Catalog -> entry -> refer to the actual item that is used)
- "control" metadata
- item metadata
Model should include all the attributes for any kind that could be in the catalog ( But FHIR adheres to the 80% rule)
FHIR allows you to search on all the elements in the catalog using REST APIs, including search criteria with metadata on the items (for example expiration dates on pricing etc)
Careful mixing information labels vs how to use information – when you model, model that the information is, but not the look and feel (example subheader – is a relationship between two parts of the report instead of calling it subheader – seem to be missing some definitions and may need to rename elements)
Other catalog models discussed:
- GS1 (has been in use for a long time in manufacturing – is the superset of all the attributes needed) and medication catalogs is what FDA is working on
- Bob Yencha to see if he can share some others from supply chain industry
Jose’s presentation of Hospital Device Workflow (Media:Catalogs_inventory_and_clinical.pptx)
Shows the workflow of using the devices in a hospital setting – manufacturer sends to GUUID as well as the hospital (GUUID does not cover all information that users may need to know)
Our modelshould focus on from manufacturer to other organizations, not how folks are setting this up inside their organization
Have clear separate between item information and the control meta data – so may be the control meta data applies also inside the organization.
eDOS is specialized for Lab tests – also eDOS supports customizations of the catalog per customer. The larger piece is the Catalog general model which is the focus of Jose's PSS
FHIR allow to send the entire catalog r as well as searching adn retrieval of the a subsection or individual items
Next steps:
- finish to add datatypes, etc to Logical model
- map to FHIR resources and create resource proposal
- Jose to produce list of the catalog control metadata elements – overview diagram
- coordinate with Lab Services WG
Micro/Susceptability report:
Looking at micro model for grouping of observations:
Micro report:
Gram stain / other observation of the sample / culture – with sub observations of identification count, susceptibility elements etc
Next steps:
- Create the profiles and review them
- Bindings
- Mappings to LRI
- Eric working on structure map tooling to map to the specific profiles that are referenced in the micro – include value set binding etc
- Map Examples
- Create the V2 transforms
- Transform the examples
Other Agenda items not covered:
- Review of DAF-Core for lab results, smoking and vitals.
- Tracker Items time permitting.
Back to OO_on_FHIR