DoF PoCD 2018-02-19

From HL7Wiki
Revision as of 15:56, 19 February 2018 by John rhoads (talk | contribs) (start meeting page)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

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

Attendance:

Comments

  • 15334 Add use cases showing move from IEEE to FHIR - 2018-Jan PoCD #1 ()
  • 15335 Explain why PoCD uses Device and PHD doesn't - 2018-Jan PoCD #2 ()
  • 15336 Why does PoCD use Sample Array while PHD uses Real-Time Sample Array - 2018-Jan PoCD #3 ()
  • 15337 Why does PoCD use Sample Array while PHD uses Real-Time Sample Array - 2018-Jan PoCD #4 ()
  • 15338 Reword Rosetta Terminology Mapping Management System explanation - 2018-Jan PoCD #5 ()
  • 15339 Typo - 2018-Jan PoCD #6 ()
  • 15340 Use Cases Should Support Full use of the Profiled Resources - 2018-Jan PoCD #7 ()
  • 15341 Remove DeviceComponent.languageCode in favor of Resource.language - 2018-Jan PoCD #8 ()
  • 15342 Change DeviceMetric.color & DeviceComponent Channel profile color extension to have a data type of CodeableConcept - 2018-Jan PoCD #9 ()
  • 15343 Loosen selected bindings to a value set vs. a Fixed Value - 2018-Jan PoCD #10 ()
  • 15344 Add 11073MDC page to the FHIR standard covering the ISO/IEEE 11073 terminology. - 2018-Jan PoCD #11 ()
  • 15345 Why does PoCD use Sample Array while PHD uses Real-Time Sample Array - 2018-Jan PoCD #12 ()
  • 15346 Add to status field values: "paused", "onine", "offline" - 2018-Jan PoCD #13 ()
  • 15347 How is a "gateway" identified - 2018-Jan PoCD #14 ()
  • 15348 If system both storing and exposing Device data, should there be another "Source"? - 2018-Jan PoCD #15 ()
  • 15349 operationalStatus should be modeled as IEEE 11073 concept - 2018-Jan PoCD #16 ()
  • 15350 DeviceComponent languageCode field not needed - 2018-Jan PoCD #17 ()
  • 15351 Field "color" should use more appropriate coding scheme - 2018-Jan PoCD #18 ()
  • 15352 Field "identifier" should be conditional or removed - 2018-Jan PoCD #19 ()
  • 15353 Add dataType field - 2018-Jan PoCD #20 ()
  • 15354 Text fields support should be explained - 2018-Jan PoCD #21 ()
  • 15355 Additional use cases suggested - 2018-Jan PoCD #22 ()
  • 15356 Short background to DoF project needed - 2018-Jan PoCD #23 ()
  • 15357 Add Scope description - 2018-Jan PoCD #24 ()
  • 15358 Reference UDI DAM and UDI Pattern ID - 2018-Jan PoCD #25 ()
  • 15359 Reference UDI DAM and UDI Pattern ID in future documents - 2018-Jan PoCD #26 ()
  • 15360 show differential view - 2018-Jan PoCD #27 ()
  • 15361 Un-crowd menu bar - 2018-Jan PoCD #28 ()
  • 15362 Improve dropdown items and give jumps - 2018-Jan PoCD #29 ()
  • 15363 Add diagrams to use cases - 2018-Jan PoCD #30 ()
  • 15364 type slices not rendering correctly in tree view. - 2018-Jan PoCD #31 ()
  • 15365 Add CapabilityStatement - 2018-Jan PoCD #32 ()
  • 15366 33 Datatypes do not belong in terminology - 2018-Jan PoCD #33 ()
  • 15367 Missing ValueSets referenced - 2018-Jan PoCD #34 ()
  • 15368 IG format made it difficult to review - 2018-Jan PoCD #35 ()
  • 15369 Reword Overview text - 2018-Jan PoCD #36 ()
  • 15370 typo - 2018-Jan PoCD #37 ()
  • 15371 Terminology resources incomplete - 2018-Jan PoCD #38 ()
  • 15372 Explain relationship between this IG and the PHD IG - 2018-Jan PoCD #39 ()
  • 15373 Clarify requirement (or not) for MDC code - 2018-Jan PoCD #40 ()
  • 15374 Measurement status should be an extension on DeviceMetric - 2018-Jan PoCD #41 ()
  • 15375 Measurement status should be modifier extension in DeviceMetric - 2018-Jan PoCD #42 ()
  • 15376 Consolidate introductory sections on Purpose, Devices on FHIR initiative, and Audience - 2018-Jan PoCD #43 ()
  • 15377 Change stylesheet for IG (created on Forge) to match IG Publisher - 2018-Jan PoCD #44 ()
  • 15378 Consider "must support" flag on items such as the identifiers - 2018-Jan PoCD #45 ()