2018JAN PHD Implementation Guide - Directory of Tracker Item Links

Directory of Links to All Tracker Items for 2018JAN Ballot for Personal Health Device Implementation Guide

• 15379 **website comment** - 2018-Jan PHD #1
  
• 15380 The approach for handling multiple specializations and the use of a ChildDeviceComponent does not work in the PHD infrastructure. In order for the uploader to perform this task, the PHD would need to provide a handle to the VMD so the uploader would know
  
• 15381 Associated with the statement above, the ChildDeviceComponent is not needed. It is currently not done in this IG. - 2018-Jan PHD #3
  
• 15382 As stated in the IG itself the version of FHIR used by the IG is not compatible with the version of the tool used to create this IG. This descrepancy will need to be fixed when the tool supports R4. This issue applies to the Structure definitions and the
  
• 15383 Pointing to the PHG in the Observation resource instead of the DeviceComponent will allow the presence of a single DeviceComponent to represent the PHD regardless of the uploading application as it will contain information ONLY about the PHD. As it is now
  
• 15384 The ASN.1 code system has no definitions. The section describes how to create the code from the PHD but this information is of no value to the consumer. The consumer needs to know where these codes are defined. There are a limited set which are defined in
  
• 15386 Typo - 2018-Jan PHD #7
  
• 15387 PHDs such as glucometers also provide remote monitoring of measurements not included in the "vital signs panel" definition given by LOINC 85353-1 used elsewhere, and directly contradicts other FHIR useage. Should remove "vital signs" reference as confusin
  
• 15388 Typo - 2018-Jan PHD #9
  
• 15389 Question about Metric object. - 2018-Jan PHD #10
  
• 15390 Mder Measurement Status as used in the 11073 stds represents a blending of concepts - as mapped, some that can be mapped to DataAbsentReason, Status, as well as some that are relagated to a MeasurementStatus extension on Observation. Thosee shown as a "co
  
• 15391 The mapping of MDER bits to component.code and .valueCodeableConcept is overly complex, and violates core terminology representation best practicves /principles. The pattern suggested is essentially a Yes /No question ask and answer. Examples show .code="se
  
• 15392 Phd Parent DeviceComponent profile is described as a profile that *has* a parent DeviceComponent (the PHG). This is confusing. This profile should be the "PHD DeviceComponent profile", and the PHG profile should be called "PHG Parent DeviceComponent profi
  
• 15393 All observation and other profiles show the 110073 MDC code ordered to be the first coding in Observation.coding, This sets an bad precedent on future implementatins that are similar to, but not 11073 or Continua based, for positional dependencies. Modern
  
• 15394 Typo - 2018-Jan PHD #15
  
• 15395 Typo - 2018-Jan PHD #16
  
• 15396 suggested clarification - 2018-Jan PHD #17
  
• 15397 Reference needed - 2018-Jan PHD #18
  
• 15398 Bad link - 2018-Jan PHD #19
  
• 15399 Bad link - 2018-Jan PHD #20
  
• 15400 Bad link - 2018-Jan PHD #21
  
• 15401 Reference needed - 2018-Jan PHD #22
  
• 15402 clarify language - 2018-Jan PHD #23
  
• 15403 Question. - 2018-Jan PHD #24
  
• 15404 improper nesting - 2018-Jan PHD #25
  
• 15405 no content - 2018-Jan PHD #26
  
• 15406 IG lacks references to the technical artifacts, i.e. StructureDefinitions - 2018-Jan PHD #27
  
• 15407 IG lacks example instances - 2018-Jan PHD #28
  
• 15408 IG lacks CapabilityStatements - 2018-Jan PHD #29
  
• 15409 I could not find any justification for oredering the slices. Relax this constraint here and on other elements where there is ordered slicing such as here http: / /hl7.org /fhir /uv /phd /2018Jan /PhdRtsaObservationProfile.html for identifiers) to put less of a
  
• 15410 it is not obvious to reader that these elements are extensions. Call them out as such and provide the supporting structureDefinition links. - 2018-Jan PHD #31
  
• 15411 UCUM is preferred in FHIR and I recommend using itof MDC instead. At least provide a conceptMap from MDC to UCUM. - 2018-Jan PHD #32
  
• 15412 "home" entry should be capitalized to be consistent with the other items. - 2018-Jan PHD #33
  
• 15413 Consider rewording for clarity - 2018-Jan PHD #34
  
• 15414 "capabilitties" should be "capabilities" - 2018-Jan PHD #35
  
• 15415 "chronically-ill" should be "chronically ill" - 2018-Jan PHD #36
  
• 15416 Suggest displaying the differences between 3.0.1 and 3.2.0 in a table, instead of a set of bullets - 2018-Jan PHD #37
  
• 15417 The structure definition (table) of elemnts for each profile should always show the description of the elements. Using mouse-hover to show the description of the elements /attributes is not ideal, and does not display when printing. I also suggest automati
  
• 15418 Most instances of Quantity use .unit. In this case, you use .code. If possible, suggest populating .unit in addition to .code so that it can be interpreted by implementers more easily. This may require a mapping between commonly used units (perhaps from U
  
• 15419 Version History case correction for "Implementation Guide" - 2018-Jan PHD #40
  
• 15420 Version History correction for device "thermometer" - 2018-Jan PHD #41
  
• 15421 Version History correction to change to "HL7 Health Care Devices (HCD) Work Group" - 2018-Jan PHD #42
  
• 15422 Version History correction to make column headers align with column data for "Date, Version, Description and Current Versions" columns. - 2018-Jan PHD #43
  
• 15423 "Purpose" page correction to camel case for consistency - 2018-Jan PHD #44
  
• 15424 "Purpose" page spelling and grammer corrections - 2018-Jan PHD #45
  
• 15425 "Audience" page spelling and grammer corrections - 2018-Jan PHD #46
  
• 15426 "Scope" page spelling and grammer corrections - 2018-Jan PHD #47
  
• 15427 "Use Cases" page wording corrections - 2018-Jan PHD #48
  
• 15428 "Use Cases" page request on more details for Example 3 - Medical Research - 2018-Jan PHD #49
  
• 15429 "Technical Implementation Guidance" page consistency in specifying the standard before the version. - 2018-Jan PHD #50
  
• 15430 "Technical Implementation Guidance-Generic and Extensible Model" page spelling and grammar corrections - 2018-Jan PHD #51
  
• 15431 "Technical Implementation Guidance -DIM to FHIR Mapping: Basic" spelling and grammar corrections - 2018-Jan PHD #52
  
• 15432 "Technical Implementation Guidance -DIM to FHIR Mapping: Basic" paragraphing correction. - 2018-Jan PHD #53
  
• 15433 "Technical Implementation Guidance General Note to Consumers" wording correction. - 2018-Jan PHD #54
  
• 15434 "Technical Implementation Guidance -DIM to FHIR Mapping: Details" spelling corrections. - 2018-Jan PHD #55
  
• 15435 "Technical Implementation Guidance -Coincident Time Stamp" spelling corrections. - 2018-Jan PHD #56
  
• 15436 "Technical Implementation Guidance -Non 11073 20601 Devices" spelling corrections - 2018-Jan PHD #57
  
• 15437 "Value Sets" page links not working - 2018-Jan PHD #58
  
• 15438 Correct spelling errors on main Profile page - 2018-Jan PHD #59
  
• 15439 Remove strike-through text in DeviceComponent Profiles and Rationalle for Child DeviceComponent areas of the Profiles main page. - 2018-Jan PHD #60
  
• 15440 Correct spelling errors on PhdBaseObservationProfile page - 2018-Jan PHD #61
  
• 15441 Correct the link to http: / /hl7.org /fhir /IEEE.ASN1 on PhdBaseObservationProfile page - 2018-Jan PHD #62
  
• 15442 Hover-over tool tip does not appear for some of the elements in the structure definition e.g. Patient -%3E reference on PhdBaseObservationProfile page - 2018-Jan PHD #63
  
• 15443 Correct spelling errors on PhdNumericObservationProfile page - 2018-Jan PHD #64
  
• 15444 A hover-over tool tip does not appear for some of the elements in the structure definition e.g. Data Absent Reason -%3E coding-%3ESystem-%3Ecode. on PhdCompoundNumericProfile page - 2018-Jan PHD #65
  
• 15445 Correct the title on the PhdCompound NumericObservationProfile page - 2018-Jan PHD #66
  
• 15446 Correct spelling errors on PhdCompoundNumericObservationProfile page - 2018-Jan PHD #67
  
• 15447 Correct spelling error on Phd Coded Enumeration Observation Profile page - 2018-Jan PHD #68
  
• 15448 Correct the link to "Generating the PHD Reported Time Stamp" on the Phd Coded Enumeration Observation Profile page - 2018-Jan PHD #69
  
• 15449 urn:iso:std:iso:11073:10101 should have a URL, or at least update the descriptive text to indicate "URN" instead of "URL". - 2018-Jan PHD #70
  
• 15450 Some of the URLs for the value sets don't work. The URLs should work, or the links should be removed and a description should be provided for how to access the contents of the value sets. - 2018-Jan PHD #71
  
• 15451 the mapping is from PHD to FHIR not the other way around - 2018-Jan PHD #72
  
• 15452 word change - 2018-Jan PHD #73
  
• 15453 Typo - 2018-Jan PHD #74
  
• 15454 Reference needed - 2018-Jan PHD #75
  
• 15455 Request for clarifying text. - 2018-Jan PHD #76
  
• 15456 Suggested word change. - 2018-Jan PHD #77
  
• 15457 Typo - 2018-Jan PHD #78
  
• 15458 link needed - 2018-Jan PHD #79
  
• 15459 the table with the measurement profiles should include the base measurement profile and the name of the FHIR profiles and maybe even the IEEE class name - 2018-Jan PHD #80
  
• 15460 Question about structural changes in FHIR versions. - 2018-Jan PHD #81
  
• 15461 word change - 2018-Jan PHD #82
  
• 15462 word change - 2018-Jan PHD #83
  
• 15463 can the leading "." for all FHIR attributes in the tables be deleted%3F - 2018-Jan PHD #84
  
• 15464 structure suggestion - 2018-Jan PHD #85
  
• 15465 creating DeviceMetric resources could be of interest as well - see email discussion - 2018-Jan PHD #86
  
• 15466 BLE GATT protocols are extensible, just not in a generic way. Please rephrase. - 2018-Jan PHD #87
  
• 15467 The profile hierarchy it is not visible in Forge when opening the xml structure definition files or in Simplifier.net. Can this be shown in a UML class diagram / picture, with e.g. PHD Numeric being subclassed from PHD Base profile being subclassed from F
  
• 15468 Cardinality change suggestion - 2018-Jan PHD #89
  
• 15469 Clarifying suggestion - 2018-Jan PHD #90
  
• 15470 structure suggestion - 2018-Jan PHD #91
  
• 15471 structure suggestion / question - 2018-Jan PHD #92
  
• 15472 correct BTLE acronym - 2018-Jan PHD #93
  
• 15473 structure definition missing - 2018-Jan PHD #94
  
• 15474 editorial / language improvement - 2018-Jan PHD #95
  
• 15475 This empty profile and the strike-through text in the profile page and superfluous table should be removed. - 2018-Jan PHD #96
  
• 15476 Typo - 2018-Jan PHD #97
  
• 15477 Question - 2018-Jan PHD #98
  
• 15478 Seeking clarification. - 2018-Jan PHD #99
  
• 15479 There should be an attribute in DeviceComponent and /or Device that can carry multiple device types. E.g. DeviceComponent.type with 1..* multiplicity - 2018-Jan PHD #100
  
• 15480 Clarification suggestion / question - 2018-Jan PHD #101
  
• 15481 PHD an PHG commonality question - 2018-Jan PHD #102
  
• 15482 Confusing text - 2018-Jan PHD #103
  
• 15483 Structure FHIR question. - 2018-Jan PHD #104
  
• 15484 Typo - 2018-Jan PHD #105
  
• 15485 Structure question - 2018-Jan PHD #106
  
• 15486 Structure question - 2018-Jan PHD #107
  
• 15487 Clarifying text - 2018-Jan PHD #108
  
• 15488 Structure question - 2018-Jan PHD #109
  
• 15489 Mapping the device information into deviceComponent resource is mentioned, but no exmaple is given - 2018-Jan PHD #110
  
• 15490 Confusing text - 2018-Jan PHD #111
  
• 15491 Consumer of FHIR resources, Consumer of PHD data, PHD decoder and creator of the FHIR resources are mentioned several times in the IG but no explanation is provided. So, I suggest short explanation /dictionary to avoid confusion when using the therms - 201
  
• 15492 Question - 2018-Jan PHD #113
  
• 15493 Observation.related will be replaces with Observation.derivedFormat and Observation.hasMember (as it is announed on build.fhir.org). Should this be mentioned here as well%3F - 2018-Jan PHD #114
  
• 15494 The hierarchy of the profiles is missing. It is not mentioned that the defined Observation profiles are subclassed from the PHD Base Profile - 2018-Jan PHD #115
  
• 15495 In the structure definition, shouldn't the effectivePeriod be under effective%5Bx%5D%3F - 2018-Jan PHD #116
  
• 15496 Cardinality change suggestion - 2018-Jan PHD #117
  
• 15497 Structure definition is missing - 2018-Jan PHD #118
  
• 15498 Empty profile. If the profile is removed, is there a replacement defined (as extension, or deviceComponent.type 0..*)%3F - 2018-Jan PHD #119
  
• 15499 If no Child DeviceComponent Profile exists, do we still need Phd Parent DevviceComponent Profile. Can it be called only Phd DeviceComponent Profile%3F - 2018-Jan PHD #120
  
• 15500 You should not take Device completely out of the workflow. We should not condemn potential consumers to mulitple query iterations to get at the same observation (one looking at Device and one at Device Component) to save bandwitdh for the reporter on some
  
• 15501 You should not take Device completely out of the workflow. We should not condemn potential consumers to mulitple query iterations to get at the same observation (one looking at Device and one at Device Component) to save bandwitdh for the reporter on some
  
• 15502 You should not take Device completely out of the workflow. We should not condemn potential consumers to mulitple query iterations to get at the same observation (one looking at Device and one at Device Component) to save bandwitdh for the reporter on some
  
• 15503 You should not take Device completely out of the workflow. We should not condemn potential consumers to mulitple query iterations to get at the same observation (one looking at Device and one at Device Component) to save bandwitdh for the reporter on some
  
• 15504 no content - 2018-Jan PHD #125
  
• 15505 Harmonization of PHD FHIR Resource Usage to the PoCD Resource model. - 2018-Jan PHD #126
  
• 15506 PHD IG Should Fully Integrate UCUM - 2018-Jan PHD #127