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

Difference between revisions of "201809 Catalog Track"

From HL7Wiki
Jump to navigation Jump to search
Line 32: Line 32:
 
<!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track -->
 
<!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track -->
 
The following organizations have indicated an interest in participating in this track:
 
The following organizations have indicated an interest in participating in this track:
*Phast - Phast will participate with a FHIR server supporting a clinical lab compendium.
+
*Phast (France) - a FHIR server supporting a clinical lab compendium.
 
*University of Utah will participate with a FHIR client able to query a lab compendium.
 
*University of Utah will participate with a FHIR client able to query a lab compendium.
*Quest Diagnostics (to be confirmed) - Quest intends to bring a client for testing the administration of a lab compendium.
+
*Quest Diagnostics (US laboratory) acting as a client administrating a lab compendium
 +
* (Russian laboratory) acting as a client administrating and querying a lab compendium
 
* ''Your organization here!''
 
* ''Your organization here!''
  

Revision as of 22:03, 29 September 2018

Return to Connectathon 19 page

Return to Sep 2018 Proposals

Order Catalog

Submitting WG/Project/Implementer Group

  • Orders and Observations

Justification

Resources and Resource profiles needed to support catalogs of various types (lab compendia, medication formularies, healthcare service directories, etc) are in an early draft stage. These include a Catalog profile on Composition, a CatalogEntry resource, an ObservationDefinition resource, a SpecimenDefinition resource, and potentially a profile on ActivityDefinition. This connectathon track is intended to test the design approach and confirm the resource set meets the needs of the use case. The track is based on the September R4 ballot

This will inform the development of the catalog resources, with a goal of reaching FMM 1 for FHIR Release.

FHIR version used

For this connectathon the catalog track will be based on the current build of FHIR. The reason for that is that a number of resources used by Catalogs (CatalogEntry, ObservationDefinition, SpecimenDefinition) have evolved after the publication of the September ballot. And these late evolutions are needed for this testing session.

Proposed Track Lead

See Connectathon_Track_Lead_Responsibilities

François Macary
Email: francois.macary@phast.fr
Zulip: François Macary

Expected participants

The following organizations have indicated an interest in participating in this track:

  • Phast (France) - a FHIR server supporting a clinical lab compendium.
  • University of Utah will participate with a FHIR client able to query a lab compendium.
  • Quest Diagnostics (US laboratory) acting as a client administrating a lab compendium
  • (Russian laboratory) acting as a client administrating and querying a lab compendium
  • Your organization here!

Roles

Please include information here regarding how much advance preparation will be required if creating a client and/or server.

Catalog Server

A FHIR Server should support the following resources for this track:

  • Catalog Profile of Composition
  • CatalogEntry
  • Content resources appropriate to the type of catalog. For Lab:
    • ActivityDefinition
    • SpecimenDefinition
    • ObservationDefinition

A FHIR server is available for testing with sample data

http://jade.phast.fr/Baltimore-Catalog/api/FHIR/

Catalog Consumer

  • University of Utah: Client browsing the content of a clinical laboratory compendium
  • Quest Diagnostics: Client administrating a clinical laboratory compendium

Scenarios

This connectathon track will test the following interactions based on a clinical laboratory compendium:

Administration of the catalog by a clinical laboratory

  • Creation of new catalog entries
  • Update of catalog entries
  • Retirement of a catalog entry and replacement by another one

All these interactions use Bundle of type "transaction" and "transaction-response"

Query and retrieval of catalog entries by a CPOE system

Search Catalog by title

GET [base]/composition?title=[Catalog.title]

Example: http://jade.phast.fr/catalogs/api/fhir/composition?title=CIOlab

Check Catalog by id

GET [base]/composition/[catalogId]

Example: http://jade.phast.fr/catalogs/api/fhir/composition/2

Search catalog entry by name of specialty

Example: search for virology orderable tests and panels

Search catalog entry by name of orderable service

Example: search all entries corresponding to orderable tests or panels containing the word "sodium"

Retrieve details for an orderable diagnostic service

GET [base]/CatalogEntry?_has:Composition:_id=2&_id=[CatalogEntry id]

TestScript(s)

None.

Security and Privacy Considerations