Linked Care 2024

Acknowledgement

The given structure of this track is mainly based on HL7 International's Connectathon Patient Track definition.


Short Description

This track provides participants with a comprehensive introduction to the Linked Care Implementation Guide, using the real-world use case of an interdisciplinary medication ordering workflow. We will focus on three actors with three user stories each a well-defined scenario using a small number of different resources that can easily be met by those who have not had a lot of exposure to FHIR.

Long Description

With the Linked Care IG ballot on the finish line, this is an opportunity to see a brand new profile come to life as a standard-for-trial-use (STU). There will be a live demonstration using model clients for all three actors, against the public development and quality clusters of the actual Linked Care infrastructure. Participants are invited (and guided) to use the open source SDK to impersonate any of the test actors using a set of pseudo certificates with the full set of security and authentication mechanisms in place, and exercise the different resource operations from the console or from the debugger to get an impression of how client and server interact to process medication orders, prescriptions and dispenses.

This tracks is suitable for participants who are interested in the standardization process, best practices and first-hand experiences with an implementation following such standardization, and is also aimed at software developers intending to add FHIR client capabilities to their products with the aim to implement a solution according to some IG in general.

Type

Educate on the standardization and application of FHIR technology in Austria, disseminate practical results from the research part of the Linked Care project

Submitting Work Group/
Project/
Accelerator/
Affiliate/
Implementer Group  

HL7 Austria / TC FHIR / AG Pflege

The Linked Care Consortium

LOIDL Consulting & IT Services GmbH

Track Lead(s)
Track Lead Email(s)

latikaynen@loidl-consulting.at

Related Tracks
None
FHIR Version

Linked Care IG:

  • FHIR R5
Specification(s) this track uses

https://fhir.hl7.at/r5-LinkedCare-main (Linked Care IG R5)

Artifacts of focus

LINCARequestOrchestration

https://fhir.hl7.at/r5-LinkedCare-main/StructureDefinition-linca-full-proposal-list.html

LINCAProposalMedicationRequest

https://fhir.hl7.at/r5-LinkedCare-main/StructureDefinition-linca-proposal-medication-request.html

LINCAPrescriptionMedicationRequest

https://fhir.hl7.at/r5-LinkedCare-main/StructureDefinition-linca-prescription-medication-request.html

LINCAMedicationDispense

https://fhir.hl7.at/r5-LinkedCare-main/StructureDefinition-linca-dipsense-documentation.html

Date / Time
Monday March 11, 09:00am-15:30pm CET
Test Servers
See Test Servers
Expected participants

Level 1:

  • Any participants looking for a hands-on experience of how a multi-actor, intersectional healthcare workflow can work.
  • FHIR server interaction via a precompiled version of the SDK test client, which can be operated from any Windows or Linux terminal.
  • Publicly available, but fully security-enabled FHIR instances are used.

Level 2:

  • More experienced attendees interested in working with an application-specific FHIR profile from a client implementer's perspective: how to connect, authenticate, work with the RESTful FHIR API, invoke operations, evaluate operation outcomes
  • Developers who are interested in stepping through an end-to-end testing, behavior-driven sample implementation and learn how a self-certifying client can be built to prove that it complies with a FHIR IG specification
  • Developers with basic .NET Core Debugging skills in any suitable IDE, and a basic knowledge of the C# programming language
Track Details

System Roles

FHIR Client

FHIR Server

Pre-Requisites

Here are some links to assist implementers:

Security and Privacy considerations

Do not submit personal data (in particular, social insurance numbers and the like). Development and Test clusters require authentication, but are not encrypted and hardened like a production instance would be - use only the provided pseudo certificates.

TestScript(s)

The test scripts are part of the public test project sources, which are in turn part of the open source SDK.