Difference between revisions of "DoF PoCD 2018-02-19"

From HL7Wiki
Jump to navigation Jump to search
(start meeting page)
 
(refactor)
Line 1: Line 1:
 
==Devices on FHIR Point-of-Care Tech Call - Ballot Resolution 2018-02-09==
 
==Devices on FHIR Point-of-Care Tech Call - Ballot Resolution 2018-02-09==
  
Attendance:
+
Attendance: Stefan Karl, Michael Faughn, Ken Fuchs, John Rhoads (notes)
  
===Comments===
+
Agenda: discuss suggested resolutions for ballot comments related to Point-of-Care Device Implementation Guide on 2018 JAN ballot. See tracker items for followup text with the suggestions.
 +
 
 +
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15373 15373] Clarify requirement (or not) for MDC code - 2018-Jan PoCD #40 ()
 +
 
 +
Since this Implementation Guide is built on the use of DeviceComponent and DeviceMetric resources to represent functional components using the concepts of the IEEE 11073 model applied to a point-of-care device, it is logical to use the associated nomenclature. In Observation, this context is not necessarily used, but it is reasonable for this Implementation Guide to require that a consistent nomenclature be used, which does not preclude the use of additional codes such as LOINC or SNOMED.
  
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15334 15334] Add use cases showing move from IEEE to FHIR - 2018-Jan PoCD #1 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15335 15335] Explain why PoCD uses Device and PHD doesn't - 2018-Jan PoCD #2 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15336 15336] Why does PoCD use Sample Array while PHD uses Real-Time Sample Array - 2018-Jan PoCD #3 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15337 15337] Why does PoCD use Sample Array while PHD uses Real-Time Sample Array - 2018-Jan PoCD #4 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15338 15338] Reword Rosetta Terminology Mapping Management System explanation - 2018-Jan PoCD #5 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15339 15339] Typo - 2018-Jan PoCD #6 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15340 15340] Use Cases Should Support Full use of the Profiled Resources - 2018-Jan PoCD #7 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15341 15341] Remove DeviceComponent.languageCode in favor of Resource.language - 2018-Jan PoCD #8 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15342 15342] Change DeviceMetric.color & DeviceComponent Channel profile color extension to have a data type of CodeableConcept - 2018-Jan PoCD #9 ()
 
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15343 15343] Loosen selected bindings to a value set vs. a Fixed Value - 2018-Jan PoCD #10 ()  
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15343 15343] Loosen selected bindings to a value set vs. a Fixed Value - 2018-Jan PoCD #10 ()  
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15344 15344] Add 11073MDC page to the FHIR standard covering the ISO/IEEE 11073 terminology. - 2018-Jan PoCD #11 ()
+
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15345 15345] Why does PoCD use Sample Array while PHD uses Real-Time Sample Array - 2018-Jan PoCD #12 ()
+
Consensus was that this comment is persuasive, with the advantage that concepts not currently in standards codes, such as for new proprietary observations, can be used.
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15346 15346] Add to status field values: "paused", "onine", "offline" - 2018-Jan PoCD #13 ()
+
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15347 15347] How is a "gateway" identified - 2018-Jan PoCD #14 ()
+
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15348 15348] If system both storing and exposing Device data, should there be another "Source"? - 2018-Jan PoCD #15 ()
+
See also [[Devices on FHIR (Devices WG) Full list of 2018JAN PoCD Comments]]
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15349 15349] operationalStatus should be modeled as IEEE 11073 concept - 2018-Jan PoCD #16 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15350 15350] DeviceComponent languageCode field not needed - 2018-Jan PoCD #17 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15351 15351] Field "color" should use more appropriate coding scheme - 2018-Jan PoCD #18 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15352 15352] Field "identifier" should be conditional or removed - 2018-Jan PoCD #19 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15353 15353] Add dataType field - 2018-Jan PoCD #20 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15354 15354] Text fields support should be explained - 2018-Jan PoCD #21 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15355 15355] Additional use cases suggested - 2018-Jan PoCD #22 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15356 15356] Short background to DoF project needed - 2018-Jan PoCD #23 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15357 15357] Add Scope description - 2018-Jan PoCD #24 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15358 15358] Reference UDI DAM and UDI Pattern ID - 2018-Jan PoCD #25 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15359 15359] Reference UDI DAM and UDI Pattern ID in future documents - 2018-Jan PoCD #26 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15360 15360] show differential view - 2018-Jan PoCD #27 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15361 15361] Un-crowd menu bar - 2018-Jan PoCD #28 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15362 15362] Improve dropdown items and give jumps - 2018-Jan PoCD #29 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15363 15363] Add diagrams to use cases - 2018-Jan PoCD #30 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15364 15364] type slices not rendering correctly in tree view. - 2018-Jan PoCD #31 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15365 15365] Add CapabilityStatement - 2018-Jan PoCD #32 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15366 15366] 33 Datatypes do not belong in terminology - 2018-Jan PoCD #33 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15367 15367] Missing ValueSets referenced - 2018-Jan PoCD #34 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15368 15368] IG format made it difficult to review - 2018-Jan PoCD #35 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15369 15369] Reword Overview text - 2018-Jan PoCD #36 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15370 15370] typo - 2018-Jan PoCD #37 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15371 15371] Terminology resources incomplete - 2018-Jan PoCD #38 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15372 15372] Explain relationship between this IG and the PHD IG - 2018-Jan PoCD #39 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15373 15373] Clarify requirement (or not) for MDC code - 2018-Jan PoCD #40 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15374 15374] Measurement status should be an extension on DeviceMetric - 2018-Jan PoCD #41 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15375 15375] Measurement status should be modifier extension in DeviceMetric - 2018-Jan PoCD #42 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15376 15376] Consolidate introductory sections on Purpose, Devices on FHIR initiative, and Audience - 2018-Jan PoCD #43 ()  
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15377 15377] Change stylesheet for IG (created on Forge) to match IG Publisher - 2018-Jan PoCD #44 ()
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15378 15378] Consider "must support" flag on items such as the identifiers - 2018-Jan PoCD #45 ()
 

Revision as of 17:46, 19 February 2018

Devices on FHIR Point-of-Care Tech Call - Ballot Resolution 2018-02-09

Attendance: Stefan Karl, Michael Faughn, Ken Fuchs, John Rhoads (notes)

Agenda: discuss suggested resolutions for ballot comments related to Point-of-Care Device Implementation Guide on 2018 JAN ballot. See tracker items for followup text with the suggestions.

  • 15373 Clarify requirement (or not) for MDC code - 2018-Jan PoCD #40 ()

Since this Implementation Guide is built on the use of DeviceComponent and DeviceMetric resources to represent functional components using the concepts of the IEEE 11073 model applied to a point-of-care device, it is logical to use the associated nomenclature. In Observation, this context is not necessarily used, but it is reasonable for this Implementation Guide to require that a consistent nomenclature be used, which does not preclude the use of additional codes such as LOINC or SNOMED.

  • 15343 Loosen selected bindings to a value set vs. a Fixed Value - 2018-Jan PoCD #10 ()

Consensus was that this comment is persuasive, with the advantage that concepts not currently in standards codes, such as for new proprietary observations, can be used.


See also Devices on FHIR (Devices WG) Full list of 2018JAN PoCD Comments