Difference between revisions of "LIVD FHIR IG Proposal"
Hbuitendijk (talk | contribs) |
|||
| (13 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | <div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | ||
<div style="background:#F0F0F0"> | <div style="background:#F0F0F0"> | ||
| − | This page documents a [[:category: | + | This page documents a [[:category:Approved FHIR IG Proposal|Approved]] [[:category:FHIR IG Proposal|FHIR IG Proposal]] |
</div> | </div> | ||
</div> | </div> | ||
[[Category:FHIR IG Proposal]] | [[Category:FHIR IG Proposal]] | ||
| − | [[Category: | + | [[Category:Approved FHIR IG Proposal]] |
| − | |||
| + | Approved 2018-08-08 | ||
<!-- For additional guidance on considerations for resource creation, refer to [[FHIR IG Considerations]] --> | <!-- For additional guidance on considerations for resource creation, refer to [[FHIR IG Considerations]] --> | ||
| Line 28: | Line 28: | ||
==Owning work group name== | ==Owning work group name== | ||
Orders & Observations | Orders & Observations | ||
| − | <!-- The name of the committee that is proposed to have responsibility for developing and maintaining the IG. | + | <!-- The name of the committee that is proposed to have responsibility for developing and maintaining the IG. |
[[YourWorkGroupName]] | [[YourWorkGroupName]] | ||
| + | --> | ||
==Committee Approval Date:== | ==Committee Approval Date:== | ||
August 3, 2018 | August 3, 2018 | ||
| − | + | <!-- | |
<i>Please enter the date that the committee approved this IGproposal</i> | <i>Please enter the date that the committee approved this IGproposal</i> | ||
| + | --> | ||
==Contributing or Reviewing Work Groups== | ==Contributing or Reviewing Work Groups== | ||
None. | None. | ||
| − | <!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the IG (optional) | + | <!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the IG (optional) |
* Work Group Name | * Work Group Name | ||
* or link | * or link | ||
* or "None" | * or "None" | ||
| + | --> | ||
==FHIR Development Project Insight ID== | ==FHIR Development Project Insight ID== | ||
| − | 1335 | + | [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=1335 1335] |
<!-- Please specify the id of your work group’s PSS for doing FHIR work that covers the development and maintenance of this IG. (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc --> | <!-- Please specify the id of your work group’s PSS for doing FHIR work that covers the development and maintenance of this IG. (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc --> | ||
| Line 69: | Line 72: | ||
==Content location== | ==Content location== | ||
| − | + | https://github.com/HL7/livd | |
<!-- What is the path within the HL7 github repository (i.e. https://github.com/HL7/xxx) or what is the Simplifier project name? --> | <!-- What is the path within the HL7 github repository (i.e. https://github.com/HL7/xxx) or what is the Simplifier project name? --> | ||
| − | |||
==Proposed IG realm and code== | ==Proposed IG realm and code== | ||
| Line 99: | Line 101: | ||
==Involved parties== | ==Involved parties== | ||
The LIVD Implementation Guide is the result of a collaboration between representatives from the: | The LIVD Implementation Guide is the result of a collaboration between representatives from the: | ||
| − | * IICC | + | * IVD Industry Connectivity Consortium (IICC) |
* FDA | * FDA | ||
* CDC | * CDC | ||
| Line 105: | Line 107: | ||
* CMS | * CMS | ||
* ONC | * ONC | ||
| + | * IHE Pathology and Laboratory Medicine (PaLM) Technical Committee | ||
| + | * Phast | ||
* LIS vendors | * LIS vendors | ||
| + | ** Orchard Software | ||
| + | ** Epic | ||
| + | ** Cerner Corporation | ||
* IVD instrument manufacturers | * IVD instrument manufacturers | ||
| + | ** Abbott Laboratories | ||
| + | ** Roche Diagnostics International, Ltd | ||
| + | ** bioMerieux | ||
| + | * Swiss Laboratory Interoperability Interest Group (Joint Venture of FAMH.ch, IHE-Suisse.ch, HL7.ch, SULM.ch) | ||
* and other interested parties | * and other interested parties | ||
| Line 124: | Line 135: | ||
==Example Scenarios== | ==Example Scenarios== | ||
| − | The primary scenario is for a manufacturer to post the | + | The primary scenario is for a manufacturer to post the LIVD catalog (FHIR Bundle) on a website and/or distribute it as part of their device documentation, upon which a consuming app will ingest the LIVD catalog and present it as they best see fit. |
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this IG. They should demonstrate the full scope of the IG and allow exercising of the IG's capabilities (all profiles, different types of applications, etc.) --> | <!-- Provide a listing of the types of scenarios to be represented in the examples produced for this IG. They should demonstrate the full scope of the IG and allow exercising of the IG's capabilities (all profiles, different types of applications, etc.) --> | ||
| Line 134: | Line 145: | ||
==Timelines== | ==Timelines== | ||
| − | The target is to | + | The target is to perform Connectathons through early 2019 and then have the first STU ballot in September 2019, and based on feedback and connectathon experience have a second ballot in January 2020 to solidify content and enable maturation and refinement per FMM stages. |
<!-- Indicate the target date for having the IGcomplete from a committee perspective and ready for vetting and voting --> | <!-- Indicate the target date for having the IGcomplete from a committee perspective and ready for vetting and voting --> | ||
| Line 142: | Line 153: | ||
==FMG Notes== | ==FMG Notes== | ||
| + | Would like to see greater evidence of non-US participation for a UV-scoped guide | ||
| + | |||
| + | 2019-06-21 Updated by the LIVD project team. See the additional participants listed above. | ||
Latest revision as of 17:08, 21 June 2019
This page documents a Approved FHIR IG Proposal
Approved 2018-08-08
Contents
- 1 LIVD Implementation Guide
- 1.1 Owning work group name
- 1.2 Committee Approval Date:
- 1.3 Contributing or Reviewing Work Groups
- 1.4 FHIR Development Project Insight ID
- 1.5 Scope of coverage
- 1.6 IG Purpose
- 1.7 Content location
- 1.8 Proposed IG realm and code
- 1.9 Maintenance Plan
- 1.10 Short Description
- 1.11 Long Description
- 1.12 Involved parties
- 1.13 Expected implementations
- 1.14 Content sources
- 1.15 Example Scenarios
- 1.16 IG Relationships
- 1.17 Timelines
- 1.18 When IG Proposal Is Complete
- 1.19 FMG Notes
LIVD Implementation Guide
Owning work group name
Orders & Observations
Committee Approval Date:
August 3, 2018
Contributing or Reviewing Work Groups
None.
FHIR Development Project Insight ID
Scope of coverage
The LIVD Implementation Guide addresses the ability for IVD device manufacturers to communicate for each of their devices the suggested mapping of the IVD (InVitro Diagnostic) Test Codes to one or more LOINC codes.
As the initial scope does not include for manufacturers to provide FHIR based service APIs, rather providing the relevant resources in a Bundle using some form of download/file transfer, the various operations otherwise necessary are not included. Future versions will address that scope.
The consuming application will present the data in a format and context suitable to those who configure devices to interact with a Laboratory Information System (LIS) to ensure the appropriate LOINC code is used when a result is communicated from the device to the LIS>
IG Purpose
The IG enables consistent expression of the suggested mappings using an industry standard that enables consistency across manufacturers, as well as enabling a path to service based APIs to provide access to these mappings.
Content location
Proposed IG realm and code
uv/livd
Maintenance Plan
The community (manufacturers, FDA, CDC, LIS vendors, and others) is already progressing scope to address suggested mapping of non-quantitative results for the device. As these and other capabilities are being addressed and service based APIs are being implemented, subsequent versions of the guide will be developed to address these requirements.
Short Description
The LIVD Implementation Guide provides a industry standard expression for an IVD device manufacturer's suggestions for a specific device's mapping from the internal, proprietary IVD test codes to suggested LOINC codes when a LIS manager is connecting and configuring a device to the LIS.
Long Description
The LIVD Implementation Guide provides a industry standard expression for an IVD device manufacturer's suggestions for a specific device's mapping from the internal, proprietary IVD test codes to suggested LOINC codes when a LIS manager/analyst is connecting and configuring a device to the LIS.
As an LIS manager/analyst is configuring a device to be connected to the LIS, the suggested mappings can focus the manager/analyst on the most likely LOINC codes to consider, thus enabling a choice relevant to the specific context of the device's use and purpose within the Laboratory that is more consistent across the industry.
Involved parties
The LIVD Implementation Guide is the result of a collaboration between representatives from the:
- IVD Industry Connectivity Consortium (IICC)
- FDA
- CDC
- NLM
- CMS
- ONC
- IHE Pathology and Laboratory Medicine (PaLM) Technical Committee
- Phast
- LIS vendors
- Orchard Software
- Epic
- Cerner Corporation
- IVD instrument manufacturers
- Abbott Laboratories
- Roche Diagnostics International, Ltd
- bioMerieux
- Swiss Laboratory Interoperability Interest Group (Joint Venture of FAMH.ch, IHE-Suisse.ch, HL7.ch, SULM.ch)
- and other interested parties
Expected implementations
Device manufacturers and LIS vendors are interested and expected to implement the initial version to publish LIVD mappings (manufacturers) and present the mappings in context of the LIS configuration process (LIS vendors). The initial version of the IG resulting from the For Comment ballot and connectathon will further inform the initial take-on by these parties.
Content sources
The LIVD Implementation Guide is based on the IICC whitepaper that describes an agreed to data set and format using JSON (not based on FHIR resource specifications) that is currently being published by various manufacturers.
Example Scenarios
The primary scenario is for a manufacturer to post the LIVD catalog (FHIR Bundle) on a website and/or distribute it as part of their device documentation, upon which a consuming app will ingest the LIVD catalog and present it as they best see fit.
IG Relationships
None.
Timelines
The target is to perform Connectathons through early 2019 and then have the first STU ballot in September 2019, and based on feedback and connectathon experience have a second ballot in January 2020 to solidify content and enable maturation and refinement per FMM stages.
When IG Proposal Is Complete
When you have completed your proposal, please send an email to FMGcontact@HL7.org
FMG Notes
Would like to see greater evidence of non-US participation for a UV-scoped guide
2019-06-21 Updated by the LIVD project team. See the additional participants listed above.
