Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Submitting WG/Project/Implementer Group

  • Orders & Observations

Justification and ObjectivesWhat’s

the purpose of hosting this connectathon track? What do you hope to achieve?Validate the representation for non-quantitative IVD tests' result values mappings to LOINC and/or SNOMED in the LIVD Implementation Guide version 2 draft.  

This track will use what version of FHIR.

  • FHIR R4

Clinical input requested (if any)

Does your track have a need for input from the clinical community? If so, what are the needs?

Related tracks


  • Input from Lab Device Manufacturers, Laboratory IT and those performing the IVD Test Code to LOINC mapping are essential.

Related tracks

  • Order Catalog Track
  • Terminology Services

Proposed Track Lead

Name, email. Track leads must be registered users on

Expected participants

Who do you expect to be present? How many do you expect to attend?

Track Orientation

A webinar will be hosted on date at time to share further participation information about this track.

System Roles

Describe each type of system that could participate in the track

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

Role 1 Name


Describe the different scenarios participating systems can engage in during the conenctathon. Each scenario should provide sufficient description that participants can appropriately construct their software in advance to prepare to interoperate during the connectathon.

Scenario Step 1 Name



Success Criteria:

Bonus point:


Indicate any test scripts that will be used to help verify system behavior

Security and Privacy Considerations


Expected participants

  • 3-4 starting Saturday PM through Sunday.  Need to confirm whether we can start earlier or not.

Track Orientation

  • Friday, August 30, 1-2pm ET
  • Friday, September 6, 1-2pm ET

Online Meeting Link:
Online Meeting ID: ord

If not on FCC (e.g., in a car) or not wanting to use VOIP, use the following dial-in:

Dial-in Number (United States): (515) 739-1430 Access Code: 294586

International Dial-in Numbers:

FAQ’s, tips and other helpful information regarding is available at > Resources > Tools and Resources  > Tip Sheet.

System Roles

  • Device Manufacturer
    • The Device Manufacturer creates a Bundle for their LIVD Publication and make that available at least as a file (e-mail, Direct, CD, website link) or FHIR server (although latter is not expected to be interacted with in the current state).
  • Laboratory
    • The Laboratory, LIS or separate system, will receive the LIVD Bundle and present the content in a readable form, which may be a spreadsheet, online view, or otherwise.
  • Middleware/Device Connectivity
    • A middleware solution may be used to configure the test analyte mappings on behalf of an LIS as results flow from device to LIS. This role is therefore expected to be very similar, if not that same as that of a Lab/LIS, but separated for now to validate whether that is correct.
  • Intermediary Third Party Library
    • A third party collecting all manufacturer's data and making it available through a FHIR server for others to access. This could be completely independent (e.g., a standards organization or terminology library), as part of an LIS or Middleware/Device Connectivity.


  • Scenario 1 - The manufacturer creates a LIVD Publication Bundle and makes it electronically available to a receiver. The receiver uses the LIVD Publication Bundle to render the content in their preferred format (e.g., spreadsheet, in-line with configurator, UI display).
  • Scenario 2 - Multiple manufacturers create a LIVD Publication Bundle and make it electronically available to a receiver. The receiver populates a FHIR server and makes APIs available to access these across manufacturers. Another party uses an App to obtain the data from that intermediary.
  • Scenario 3 - Multiple manufacturers create a LIVD Publication Bundle (including manufacturer codes for observations, a LOINC code system fragment and one or more ConceptMap resources).  This content will be loaded (via a FHIR REST endpoint or otherwise) to a server with terminology service capabilities, which will make the content available to a receiver via FHIR terminology service operation endpoints. The receiver (client) will use the FHIR terminology service API to access the data in the context of specific identified client needs.


  • While we have test data, there is not a test script at this point, particularly as we are not communicating directly between a client and a server.
  • Focus is on qualitative test examples to ensure they are properly represented in the FHIR profiles.

Security and Privacy Considerations

  • None