This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Devices on FHIR (Devices WG) Full list of 2018JAN PoCD Comments"
Jump to navigation
Jump to search
John rhoads (talk | contribs) m (typo fix) |
John rhoads (talk | contribs) m (c) |
||
(6 intermediate revisions by 2 users not shown) | |||
Line 2: | Line 2: | ||
====Terminology==== | ====Terminology==== | ||
− | *[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=15373 15373] <span style="color:#0000ff">Clarify requirement (or not) for MDC code - 2018-Jan PoCD #40 </span> |
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15343 15343] <span style="color:#0000ff">Loosen selected bindings to a value set vs. a Fixed Value - 2018-Jan PoCD #10 </span> | *[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15343 15343] <span style="color:#0000ff">Loosen selected bindings to a value set vs. a Fixed Value - 2018-Jan PoCD #10 </span> | ||
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15344 15344] <span style="color:#0000ff">Add 11073MDC page to the FHIR standard covering the ISO/IEEE 11073 terminology. - 2018-Jan PoCD #11 </span> | *[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15344 15344] <span style="color:#0000ff">Add 11073MDC page to the FHIR standard covering the ISO/IEEE 11073 terminology. - 2018-Jan PoCD #11 </span> | ||
Line 8: | Line 8: | ||
====Resources==== | ====Resources==== | ||
− | *[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15345 15345] Why is udi separate from identifier? - 2018-Jan PoCD #12 | + | *[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15345 15345] <span style="color:#0000ff">Why is udi separate from identifier? - 2018-Jan PoCD #12 </span> |
*[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=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=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=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=15341 15341] <span style="color:#0000ff">Remove DeviceComponent.languageCode in favor of Resource.language - 2018-Jan PoCD #8</span> | *[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15341 15341] <span style="color:#0000ff">Remove DeviceComponent.languageCode in favor of Resource.language - 2018-Jan PoCD #8</span> | ||
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15350 15350] <span style="color:#0000ff">DeviceComponent languageCode field not needed - 2018-Jan PoCD #17 </span> | *[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15350 15350] <span style="color:#0000ff">DeviceComponent languageCode field not needed - 2018-Jan PoCD #17 </span> | ||
− | *[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=15352 15352] <span style="color:#0000ff">Field "identifier" should be conditional or removed - 2018-Jan PoCD #19</span> |
− | *[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=15342 15342] <span style="color:#0000ff">Change DeviceMetric.color & DeviceComponent Channel profile color extension to have a data type of CodeableConcept - 2018-Jan PoCD #9</span> |
*[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=15353 15353] Add dataType field - 2018-Jan PoCD #20 | ||
Line 20: | Line 20: | ||
*[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=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 () | *[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 () | ||
− | *[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=15351 15351] <span style="color:#0000ff">Field "color" should use more appropriate coding scheme - 2018-Jan PoCD #18</span> |
*[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=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=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=15374 15374] Measurement status should be an extension on DeviceMetric - 2018-Jan PoCD #41 () | ||
Line 55: | Line 55: | ||
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15369 15369] <span style="color:#0000ff">Reword Overview text - 2018-Jan PoCD #36 () | *[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15369 15369] <span style="color:#0000ff">Reword Overview text - 2018-Jan PoCD #36 () | ||
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15338 15338] <span style="color:#0000ff">Reword Rosetta Terminology Mapping Management System explanation - 2018-Jan PoCD #5 </span> | *[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15338 15338] <span style="color:#0000ff">Reword Rosetta Terminology Mapping Management System explanation - 2018-Jan PoCD #5 </span> | ||
− | *[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=15339 15339] <span style="color:#0000ff">Typo - 2018-Jan PoCD #6 </span> |
− | *[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=15370 15370] <span style="color:#0000ff">typo - 2018-Jan PoCD #37 </span> |
− | Items | + | Items with resolutions that have been voted on are in <span style="color:#0000ff">blue</span> |
See also [[Devices on FHIR - 2018-JAN - PoCD IG comment list in numerical order]] | See also [[Devices on FHIR - 2018-JAN - PoCD IG comment list in numerical order]] |
Latest revision as of 14:47, 16 April 2018
Contents
Comments
Terminology
- 15373 Clarify requirement (or not) for MDC code - 2018-Jan PoCD #40
- 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
- 15367 Missing ValueSets referenced - 2018-Jan PoCD #34
Resources
- 15345 Why is udi separate from identifier? - 2018-Jan PoCD #12
- 15346 Add to status field values: "paused", "onine", "offline" - 2018-Jan PoCD #13
- 15349 operationalStatus should be modeled as IEEE 11073 concept - 2018-Jan PoCD #16
- 15341 Remove DeviceComponent.languageCode in favor of Resource.language - 2018-Jan PoCD #8
- 15350 DeviceComponent languageCode field not needed - 2018-Jan PoCD #17
- 15352 Field "identifier" should be conditional or removed - 2018-Jan PoCD #19
- 15342 Change DeviceMetric.color & DeviceComponent Channel profile color extension to have a data type of CodeableConcept - 2018-Jan PoCD #9
- 15353 Add dataType field - 2018-Jan PoCD #20
Profiles
- 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 ()
- 15351 Field "color" should use more appropriate coding scheme - 2018-Jan PoCD #18
- 15354 Text fields support should be explained - 2018-Jan PoCD #21 ()
- 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 ()
- 15378 Consider "must support" flag on items such as the identifiers - 2018-Jan PoCD #45 ()
Missing content
- 15372 Explain relationship between this IG and the PHD IG - 2018-Jan PoCD #39
- 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 ()
- 15363 Add diagrams to use cases - 2018-Jan PoCD #30 ()
- 15334 Add use cases showing move from IEEE to FHIR - 2018-Jan PoCD #1 ()
- 15340 Use Cases Should Support Full use of the Profiled Resources - 2018-Jan PoCD #7 ()
- 15355 Additional use cases suggested - 2018-Jan PoCD #22 ()
- 15335 Explain why PoCD uses Device and PHD doesn't - 2018-Jan PoCD #2 ()
- 15366 Datatypes do not belong in terminology - 2018-Jan PoCD #33 ()
- 15365 Add CapabilityStatement - 2018-Jan PoCD #32 ()
Formatting
- 15368 IG format made it difficult to review - 2018-Jan PoCD #35
- 15377 Change stylesheet for IG (created on Forge) to match IG Publisher - 2018-Jan PoCD #44
- 15361 Un-crowd menu bar - 2018-Jan PoCD #28
- 15362 Improve dropdown items and give jumps - 2018-Jan PoCD #29
- 15376 Consolidate introductory sections on Purpose, Devices on FHIR initiative, and Audience - 2018-Jan PoCD #43
- 15360 show differential view - 2018-Jan PoCD #27
- 15364 type slices not rendering correctly in tree view. - 2018-Jan PoCD #31
- 15371 Terminology resources incomplete - 2018-Jan PoCD #38
Wording
- 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
- 15369 Reword Overview text - 2018-Jan PoCD #36 ()
- 15338 Reword Rosetta Terminology Mapping Management System explanation - 2018-Jan PoCD #5
- 15339 Typo - 2018-Jan PoCD #6
- 15370 typo - 2018-Jan PoCD #37
Items with resolutions that have been voted on are in blue
See also Devices on FHIR - 2018-JAN - PoCD IG comment list in numerical order