Submitting WG/Project/Implementer Group
Orders & Observations WG
Justification and Objectives
This will be the first opportunity to test the new order-catalog FHIR IG.
The objective is to test the "laboratory service catalog" of this IG, before it goes to ballot in August.
This track will use R4 version of FHIR.
Stream dedicated to this track on chat.fhir.org
Clinical input requested (if any)
None
Related tracks
None
Track Lead
François Macary, francois.macary@phast.fr
Rob Hausam, rob@hausamconsulting.com
Expected participants
PHAST : FHIR catalog server available at: https://jade.phast.fr/resources-server/api/FHIR/ (role: Catalog cutodian)
Uses http basic authentication with username = Connectathon and password = Connectathon_052020
Quest Diagnostics : client implementing the two roles "Catalog consumer" and "Catalog owner"
...
Track Orientation
Order Catalog track orientation webinar held on April 23, 11am EST.
Get the recording, password is 8u*k%1AU
Slide-deck below:
System Roles
- Catalog custodian: a laboratory service catalog FHIR Server. The system shall have at least one catalog of laboratory services, loaded. It should be at least ready to support read and search.
- Catalog consumer: a catalog FHIR client. The system shall be capable of browsing the lab catalog content, and to retrieve the definitions of laboratory services from it.
- Catalog owner: a system owning the content of the catalog, and delegating its FHIR publication to a Catalog custodian.
Scenarios
Scenario 1: Browse catalog content
System roles: Catalog consumer > Catalog custodian
Action: Search for laboratory services in the catalog, using the search criteria specified in the order-catalog FHIR IG.
Scenario 2: Retrieve the full details of a laboratory service definition
System roles: Catalog consumer > Catalog custodian
Action: apply step 2 as specified here in the order-catalog FHIR IG.
Scenario 3: Import a subset of a catalog
System roles: Catalog consumer > Catalog custodian
Action: Import interaction described in this section of the guide
Scenario 4: Transaction create or update in a catalog
System roles: Catalog owner > Catalog custodian
Action: using a transaction Bundle, create/update the graph of resources representing the full description of a laboratory service in the catalog
Scenario 5: Atomic create, update, delete in a catalog
System roles: Catalog owner > Catalog custodian
Action: Atomic interactions (create, update, patch, delete) on resources of a catalog, with integrity control maintained by the custodian.
Security and Privacy Considerations
No personal data is involved on this track.
The base level of security proposed is: http basic authentication + TLS 1.0