Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated links from gForge to JIRA

...

AreaIssuesDescriptionProposed Disposition
CDS Hooks

14944 14943 14935 14932

Use CDS HooksAlready decided
14933Don't create a new domain-specific resource to define CDS recommendations for specific domains.Defer this to the CDS workgroup for future consideration. Clinical Practice Guidelines on FHIR project, could potentially have impact on this. Take what they developed and see if the immunization work case could fit into that. This only for Immunization space, not applicable beyond. Future consideration. 
Public Health issue, not directly related to this Implementation guide14939Should include notGivenReasonPH took care of this
14905Should support for Immunization.vaccinationProtocol be changed?PH resolved this

Terminology

We will use US-Core and/or QI-Core

  • Where we need values we will build out the value sets
  • Where we don't we will leave them as is
14940Terminology binding includes 4 data elements, are these supposed to be included in this profile?Persuasive with mod. Plan to go through and include value sets as much as possible. 
14923The route codes need to be less ambiguous Persuasive with mod. Will refer to an existing profile that better defines this. e.g. US-Core / QI-Core
14922The value set should be increased, patient objection and product out of stock are useful, immunity should be better supported, medical precautions should also have more granularity Persuasive with mod. Will refer to an existing profile that better defines this. e.g. US-Core / QI-Core
14920More extensive set of values would be much more usefulPersuasive
14909Change how vocabulary is boundPersuasive with mod. Will refer to an existing profile that better defines this. e.g. US-Core / QI-Core
14901Should support NDC, not just CVX Persuasive with mod. Will refer to an existing profile that better defines this. e.g. US-Core / QI-Core
14921Value set should include more possibilities and should differentiate the different types of sources Not persuasive
Structure use of resources and profiles of resources14942Link to payer/insurerNot persuasive
14941Should reference Condition resourceFuture consideration: current-out-of-scope for the PSS

14938 14937

Suggest coordinating this profile with QI corePersuasive with mod: We are considering this along with US-Core
14936Why was the US Core profile not used?Persuasive with mod: We are considering this along with QI-Core
14934Suggest coordinating with others to apply notion of restricted patient profile more broadlyPersuasive with mod: We are looking at adopting US-Core and/or QI-Core and not restricting the patient object. Will allow restriction of patient information using data absent reason. 
14931Recommend removing profile and referencing general resourceConsidering
14930Guide is not clear that recommendations are not patient specificNot persuasive: The guide is patient specific, although the identify of the patient is not needed to make recommendation, will update language to make this clear
14929Don't limit the Patient resourcePersuasive with mod: We are looking at adopting US-Core and/or QI-Core and not restricting the patient object. Will allow restriction of patient information using data absent reason. 
14924Consider ODHFuture consideration: Currently out-of-scope for PSS, but useful for future work. 
Technical fixes to the implementation guide presentation/format, additional examples, etc.

14928 14913 14912

Need examples.Persuasive

14927 14926Broken linkPersuasive

14919No context or guidance to instruct the reader how to use the artifacts describedPersuasive

14918Provide a Capability StatementPersuasive

14917 14916Need to link profile to the operationPersuasive

14915IG is underspecified and incompletePersuasive

14914List inputs explicitly Persuasive with mod: We are going to not constrain the patient resource, but instead pass through a standard US-Core and/or QI-Core. 

14911Differential is not being renderedPersuasive

14908Remove XML template and JSON template tabsPersuasive

14907Format content should link to definitions in nav-tab Persuasive

14906Remove nav-tabs for mappingsPersuasive

14904Link to ImmunizationRecommendation.template-forecastStatusReason does not workPersuasive

14903Link to ImmunizationRecommendation. Recommendation. dateCriterion.code value set does not workPersuasive

14902Link to ImmunizationRecommendation. Recommendation.forecastStatus value set does not workPersuasive

...