<p>2017122_HL7LIVD_Notes</p><p>Attendees: Andrea, Hans, Mike, Rob, JD, Riki, Dan</p><p>Riki joins 8 min late – </p><p>How to handle including a code in the publication that will be effective in the future?</p><p>Not needed for this at the moment – note as parking lot item to potentially add an effective later</p><p>In LOINC there was discussion about that for specific codes – let’s wait for someone to bring that up at a later time</p><p>Add LIVD in definition</p><p>Composition.author – 1..1 – add LIVD to the definition</p><p>Do we need to restrict allowable types to organization? Yes</p><p>Additional attributes only need the display part = string for organization name</p><p>Can a test be linked to a patient? Not in this particular setting, but once the analyzer uses a test on a sample do we need to link back to here? No it was not intended to be traced to this publication.</p><p>Different project different scope – where you have to look back only, not linking forward, so not here – and save that for separate analysis, not part in individual transactions every time</p><p>Composition.title 1.1 String, definition ok</p><p>Leave the other Composition attributes as 0..0 up to section – Yes</p><p>Composition.section 1..* - we want to group by type described – like component, profiles, specimen information, but we do not want to be too prescriptive – more as example – definition should be the root for this section? Is it a root? Is it a category or header?</p><p>The group or set of resource instances of the same type grouped together – for example LOINC, devices as examples</p><p>Composition.section.title = 1..1, string, Label for this section, e.g. devices, LOINC, concept maps etc. catalogEntry = entry livd-section-type = required binding, not extensible: devices, conceptmap, loinc-codes, ivd-test-codes, entry-definition – we will add observationdefinition and labdeviceprofile at a later time need to set binding - LIVDSectionType Compare the section types to the headers in the white paper – making sure we don’t miss any groups – also the names do not match what is in the paper – don’t need to, since this is FHIR resource names and organization?</p><p>Green items ae all represented in columns in sectiontype code system? – catalog profile is NOT in there, as it is the overarching publication</p><p>All headers in the table from the LIVD is represented in the FHIR slide</p><p>In bindings tab add LIVDSectionType as name</p><p>As reference use #livd-section-type – code list - required (means you cannot add codes) and definition – list of types used in LIVD</p><p>Compostion.section.code change CodeableConcept to coding – no restrict to coding as first element of the CodeableConcept datatype? No actually it is should be a code, so can delete all the elements of CodeableConcept</p><p>Shortname must become the concatenation of the codes we have on the list, separated by “|”</p><p>Updated spreadsheet is here: TBD</p><p>Updated slides are here: http://wiki.hl7.org/index.php?title=File:LIVD_FHIR_Mapping.pptx </p>