Presentation is loading. Please wait.

Presentation is loading. Please wait.

LIVD on FHIR Draft Discussion.

Published byLiana Wibowo Modified over 5 years ago

Similar presentations

Presentation on theme: "LIVD on FHIR Draft Discussion."— Presentation transcript:

1 LIVD on FHIR Draft Discussion

2 Concept Mapping Publication LIVDCatalogProfile (Composition) LIVD
FHIR Resources Publication -- Equipment IVD Test Result Code LOINC Code LIVDCatalogProfile (Composition) LIVDCatalogEntryProfile (CatalogEntry - R4) DeviceDefinitionProfile (Device) Choices: “ActivityDefinition” codeable concept (one entry with multiple codes) “ActivityDefinition” multiple instances and mapped Catalog Entry mapping ConceptMap

3 FHIR Resources Only test device that it is performed on
Does not take into account reagent – future scope perhaps IVD Test Code may not have a LOINC code (yet) Need to support nullflavor of “unknown” Need to support that an IVD Test Code can be represented by multiple LOINC codes. Where there are multiple LOINCs for one IVD Test Code, individual guidance etc. LIVDCatalogProfile Publication LIVDCatalog EntryProfile DeviceDefinitionProfile Equipment 1:* 1:1 IVD Test Code IVD Test Result LOINC Code 0:* Analyte Mapping 1:* 0:*

4 Publication: Catalog Publication LIVD FHIR Profile on Composition --
Publisher Publication Version ID LOINC Version ID LOINC Copyright Localization Region LIVDCatalogProfile Catalog.identifier (1..1) Catalog.name (0..1) Catalog.publisher (1..1) Catalog.version (1..1) format to be defined by publisher. Ask for Composition.version Catalog.LOINCVersionIdentifier (1..1) Consider ConceptMap Would yield a change in Catalog.identifier Catalog.LOINCCopyright (1..1) Text + URL to terms of use Catalog.language (1..1) RFC 5646 (doublecheck) Extension. Ask for one on Catalog Catalog.region (0..1) Ask for Composition.context

5 “Package” Composition
Composition.status Composition.type - Could request a LOINC for LIVD Catalog, although we can make up our own. Composition.subject = LIVDCatalogProfile Composition.date Composition.author – Requires Organization to be an allowable reference. Composition.title – Name of the file? Composition.section.title = Perhaps: CatalogEntry, Device, ConceptMap, CodingSystem - We can have nested sections, so have some choices. Composition.section.entry = CatalogEntry instances, Device instances, ConceptMap instances, CodingSystem instances

6 Publication Line Item: Catalog Entry
LIVD FHIR Resource – Proposal Pending -- CatalogEntry CatalogEntry.identifier Need to find out how far we can go with balloting without this being in R4. Is presence in a build o.k. for a Comment ballot? Need to manually create this one since FORGE is on R3 only.

7 Equipment: Device Equipment DeviceDefinitionProfile LIVD FHIR Resource
Manufacturer Model UID (device identifier component) UID Type DeviceDefinitionProfile Device.manufacturer (1..1) Device.model (1..1) Device.udi.deviceIdentifier (0..1) Device.udi.issuer (0..1) Condition: if Device.udi.deviceIdentifier is present. While it looks like it is o.k. to have just one device identifier for a publication For other use cases it may be necessary to have multiple UDIs for one Device. To be Considered separately. Not in our scope for now.

8 What concept for mapping?
ObservationDefinition Sounds reasonable, but need to be strictly definition of course How do you related observation A with observation B? Component construct? Concern that LOINC pre-coordinates various resources it is not great to use of those to represent this. ActivityDefinition To some this sounds more like process steps rather than core tests. For others it could cover tests as well. Still a problem how to map. Missing data for IVD Test codes and LOINC codes. ProcedureDefinition Could work, but similar challenges as Observation. Term is not used within Lab settings, so does not sound right. Perhaps on the order side. DataElement => StructureDefinition ConceptMap Neutral and has mapping. Does not appear to have everything need. Need to understand where what goes.

9 FHIR Resources LIVDBundleProfile LABObservationDefinition
LABDeviceProfile LIVDCatalogProfile Bundle or Composition or both? Publication 1:* LIVDDeviceMetricProfile LIVDDeviceObservationDefinition.performer/source/originator/generator (Ref: Device, etc.) 1..1 = Abbott 1200 1:* 1:1 LIVDEntryDefinitionProfile LIVDDeviceDefinitionProfile LIVDDeviceObservationDefinition ObservationDefinition = IVD Test Code Equipment 1:* 1:1 Device.model=Abbott 1200 1:1 IVD Test Code LIVDIVDTestCodeSystemProfile informs CodeSystem.nnn=Abbott 1200 LIVDConceptMapProfile Analyte Mapping LIVDEntryDefinitionProfile Source: IVD Test Code Target: LOINC Code 1:* LIVDLOINCCodeSystemProfile LOINC Code CodeSystem.nnn=LOINC IVD Test Code ConceptMap.source=Abbott 1200 ConceptMap.group.element.code=ObservationDefinition.code

10 LIVDDeviceDefinitionProfile 1..*
LIVDBundleProfile LIVDCatalogProfile LIVDDeviceDefinitionProfile 1..* Device.model=Acme 1200 1..* 1..* LIVDLOINCCodeSystemProfile LIVDConceptMapProfile 1..1 LIVDDeviceObservationDefinition Source: IVD Test Code Target: LOINC Code LIVDLOINCValueSetProfile 1..1 1..1 0..* ObservationDefinition.code = IVD Test Code ObservationDefinition.performer = Acme 1200 1..* ValueSet.code = LOINC Code ConceptMap.source = Acme 1200 ConceptMap.group.element.code = ObservationDefinition.code (IVD Test Code) ConceptMap.group.element.target.code = CodeSystem.concept.code (LOINC Code)

11 X LIVDBundleProfile LIVDCatalogProfile LIVDDeviceDefinitionProfile
1..* 1..* LIVDLOINCCodeSystemProfile …. Device.model=Acme 1200 1..* LIVDConceptMapProfile 1..1 LIVDDeviceObservationDefinition Source: IVD Test Code Target: LOINC Code LIVDLOINCValueSetProfile …. 1..1 1..1 0..* 1..* X LIVDLOINCAnswerCodeSystemProfile LIVDSNOMEDCodeSystemProfile …. N..1 LIVDValueSetProfile Source: IVD Test Result Values Target: SNOMED/LOINC Answer Value 1..1 1..1 Obs – OpioidTest ResVal – positive:positive ResVal – negative:negative ResVal – clear, cloudy, etc. ResVal – reactive, non-reactive, grey 0..* LIVDLOINCAnswerValueSetProfile LIVDSNOMEDValueSetProfile …. 1..1 1..* No dependency

12 Mapping Options – Device - ConceptMap
An IVD Test Code can be unique just within a Device or across Devices. Up to manufacturer. The level of granularity of a Device is up to the manufacturer However we map Device to ConceptMap, needs to support that and not make it more difficult.

13 Mapping Options – Device - ConceptMap
Device link to ConceptMap ConceptMap to Device Include extension in Device to link to ConceptMap Include Device identifier in ConceptMap using an extension 1..1 1..*

14 Mapping Options – Device - ConceptMap
Using Code System link Using ObservationDefinition Link Device = Abbott Architect I200 Code System = XYZ Device = Abbott Architect 1200 ConceptMap Group.source=XYZ IVD Test A : LOINC 1, or 2, or 3 IVD Test B : LOINC 4, 5, 6 IVD Test C Ask Dan

15 Mapping Options – Device - ConceptMap
EntryDefinition Concatenated Device Code Create an Entry for DeviceDefinition Create an Entry for ConceptMap Link Entry to Entry “IVD Test Code” = Device + IVD Test Code

16 Observation Definitions
Identifier Code (codesystem) Who/what can perform this (Ref: Device, Practitioner, Organization) Device What can it perform (Ref:ObservationDefinition,Proce dureDefinition)

17 LOINC Attributes may help with that as well.
Map Data Model IVD Test Code LOINC 0:N Vendor Specimen Description Vendor Result Description Vendor Comment LOINC Code – VS/CS LOINC Long Name – VS and/or CS Component - CS Property - CS Time - CS System - CS Scale - CS Method - CS Vendor Analyte Code Vendor Analyte Name Vendor Reference ID Consider using either ObservationDefinition like attributes to put into ConceptMap OR perhaps be able to link a “full” ObservationDefinition resource into the ConceptMap to further aid automating the definition of ObservationDefinitions. LOINC Attributes may help with that as well. FUTURE SCOPE

18 ConceptMap - LIVD ConceptMap.identifier ConceptMap.status
ConceptMap.source ConceptMap.target ConceptMap.group.source ConceptMap.group.sourceVersion ConceptMap.group.target ConceptMap.group.targetVersion ConceptMap.group.element.code ConceptMap.group.element.target.code EXT:ConceptMap.group.element.target.dependsOn.criterionT ype EXT:ConceptMap.group.element.target.dependsOn.criterion Not necessary at the moment, maybe future. Set to active. Not necessary at the moment since it is contained for the foreseeable future. Maybe in the future. URI to the code system that contains the vendor’s IVD Test Codes Version of the vendor’s code system URI to the LOINC code system Version of LOINC Vendor Analyte Code LOINC Code Values: Vendor Specimen Description, Vendor Result Description, Vendor Comment The actual value Related to Device

19 ConceptMap…dependsOn.code/value
t&tracker_item_id=15604&start=0 submitted. Ideally before getting it before final May deadline.

20 Code System IVD Analyte CodeSystem.uri CodeSystem.version
CodeSystem….Various others perhaps CodeSystem.concept.code = Vendor Analyte Code CodeSystem.concept.display = Vendor Analyte Name CodeSystem.concept.designation.use = “Vendor Reference ID” CodeSystem.concept.designation.valu e = the value of the vendor reference ID LOINC (Get this from elsewhere as probably already done – just need to profile if down further) CodeSystem.uri CodeSystem.version CodeSystem…Various others perhaps CodeSystem.concept.code = LOINC Code CodeSystem.concept.display = LOINC Long Name CodeSystem.concept.property (this likely already is profiled for LOINC) Component Property Time System Scale Method

21 Profile Considerations
Apply constraints from whitepaper where 0..1 or 0..* become “RE”. Bind ActivityDefinition.mappingReference (ActivityDefinition.identifier) to LOINC Do we need a bundle/composition/something to tie the entire “catalog” together?

22 Implementation Guide Considerations

23 Other Slides not used for now

24 IVD Test Result IVD Test Result ActivityDefinition LIVD FHIR Resource
Vendor Analyte Code Vendor Analyte Name Vendor Specimen Description Vendor Result Description Vendor Reference ID Vendor Comment ActivityDefinition ActivityDefinition.identifier ActivityDefinition.name ActivityDefinition.specimenDefiniti onReference(SpecimenDefinition. description) ActivityDefinition.description ActivityDefinition.relatedArtifact ActivityDefinition.mappingReferen ce(ActivityDefinition)

25 LOINC Codes LOINC ActivityDefinition LIVD FHIR Resource - Proposed
LOINC Long Name Component Property Time System Scale Method ActivityDefinition ActivityDefinition.identifier ActivityDefinition.LOINC.longName ActivityDefinition.LOINC.component ActivityDefinition.LOINC.Property ActivityDefinition.LOINC.Time ActivityDefinition.LOINC.System ActivityDefinition.LOINC.Scale ActivityDefinition.LOINC.Method ActivityDefinition.mappingReference( ActivityDefinition)

26 IVD Test Result IVD Test Result ConceptMap LIVD FHIR Resource
Vendor Analyte Code Vendor Analyte Name Vendor Specimen Description Vendor Result Description Vendor Reference ID Vendor Comment ConceptMap

27 LOINC Codes ConceptMap LOINC LIVD FHIR Resource - Proposed LOINC Code
LOINC Long Name Component Property Time System Scale Method ConceptMap

28 Bundle Bundle.type = document
Bundle.entry.resource – The resource instances Seems to terse and no opportunity to organize the instances into section, nor give the overall package a title. Check with Rick Geimer what is the minimum used when including Composition.

29 Vendor Analyte Code 0..* 0..* LIVD LOINC Local LOINC Maps
(RELMA, Web) Local LOINC Maps Informs Human Mapper creates LOINC Code LIS Test Result Code 0..1

Download ppt "LIVD on FHIR Draft Discussion."

Similar presentations

EHR-S Reconciliation Worksheet Instructions. The spreadsheet is an extract from the EHR-S Database. Each column is Filterable by click- ing on the header.

EHR-S Reconciliation Worksheet Instructions. The spreadsheet is an extract from the EHR-S Database. Each column is Filterable by click- ing on the header.
Configuration management

Configuration management
Configuration management

Configuration management
XHTML Week Two Web Design. 2 What is XHTML? XHTML is the current standard for HTML Newest generation of HTML (post-HTML 4) but has many new features which.

XHTML Week Two Web Design. 2 What is XHTML? XHTML is the current standard for HTML Newest generation of HTML (post-HTML 4) but has many new features which.
A complete citation, notecard, and outlining tool

A complete citation, notecard, and outlining tool
Embrace the Elephant A few provocative questions….

Embrace the Elephant A few provocative questions….
HData History 1 2009: Work on hData begins Mid-2011: ONC NwHIN team looks at hData and REST 2010: hData receives MIP funding.

HData History : Work on hData begins Mid-2011: ONC NwHIN team looks at hData and REST 2010: hData receives MIP funding.
C-CDA Constraints FACA - Strategy Discussion June 23, 2014 Mark Roche, MD.

C-CDA Constraints FACA - Strategy Discussion June 23, 2014 Mark Roche, MD.
Doc.: 15-10-0175-00-004g Draft ETSI ERM TG28 Liaison response on EN 300 220 March 2010 Larry Taylor, DTCSlide 1 Project: IEEE P802.15 Working Group for.

Doc.: g Draft ETSI ERM TG28 Liaison response on EN March 2010 Larry Taylor, DTCSlide 1 Project: IEEE P Working Group for.
1 Sources:  SusanTurner - Napier University  C. Robson, Real World Research, Blackwell, 1993  Steve Collesano: Director, Corporate Research and Development.

1 Sources:  SusanTurner - Napier University  C. Robson, Real World Research, Blackwell, 1993  Steve Collesano: Director, Corporate Research and Development.
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.

Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
LRI Validation Suite Meeting November 1st, 2011. Agenda Review of LIS Test Plan Template CLIA Testing EHR testing (Juror Document)—Inspection Testing.

LRI Validation Suite Meeting November 1st, Agenda Review of LIS Test Plan Template CLIA Testing EHR testing (Juror Document)—Inspection Testing.
Training course on biodiversity data publishing and fitness-for-use in the GBIF Network, 2011 edition How Darwin Core Archives have changed the landscape.

Training course on biodiversity data publishing and fitness-for-use in the GBIF Network, 2011 edition How Darwin Core Archives have changed the landscape.
Standards Analysis Summary vMR – Pros Designed for computability Compact Wire Format Aligned with HeD Efforts – Cons Limited Vendor Adoption thus far Represents.

Standards Analysis Summary vMR – Pros Designed for computability Compact Wire Format Aligned with HeD Efforts – Cons Limited Vendor Adoption thus far Represents.
CountryData Technologies for Data Exchange SDMX Information Model: An Introduction.

CountryData Technologies for Data Exchange SDMX Information Model: An Introduction.
© 2012 The MITRE Corporation. All rights reserved. For internal MITRE use 13 June 2013 Meeting #3 hData Record Format Taskforce 1 © 2012 The MITRE Corporation.

© 2012 The MITRE Corporation. All rights reserved. For internal MITRE use 13 June 2013 Meeting #3 hData Record Format Taskforce 1 © 2012 The MITRE Corporation.
Forms and Server Side Includes. What are Forms? Forms are used to get user input We’ve all used them before. For example, ever had to sign up for courses.

Forms and Server Side Includes. What are Forms? Forms are used to get user input We’ve all used them before. For example, ever had to sign up for courses.
History Day Interpretive Web Site Category 2011. Notes on Web Site Category  Fourth year as a full NHD category.  Individual and Group entries are now.

History Day Interpretive Web Site Category Notes on Web Site Category  Fourth year as a full NHD category.  Individual and Group entries are now.
Submitting Course Outlines for C-ID Designation Training for Articulation Officers Summer 2012.

Submitting Course Outlines for C-ID Designation Training for Articulation Officers Summer 2012.
Standards Analysis Summary vMR –Pros Designed for computability Compact Wire Format Aligned with HeD Efforts –Cons Limited Vendor Adoption thus far Represents.

Standards Analysis Summary vMR –Pros Designed for computability Compact Wire Format Aligned with HeD Efforts –Cons Limited Vendor Adoption thus far Represents.

Similar presentations

Ads by Google