Add support for risk conditions and other patient specific attributes

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Considered for Future Use
    • Priority: Medium
    • Immunization Forecast CDS (FHIR)
    • STU3
    • Public Health
    • (profiles)
    • Hide

      There was already a vote to defer this, but it wasn't transitioned.

      Show
      There was already a vote to defer this, but it wasn't transitioned.
    • Craig Newman/Danny Wise: 20-0-0

      From Kevin Snow at Envision:

      We need to develop a strategy for calling different versions of API version (different FHIR version, contraindication type resources are added in the future) if this happened would we want to create a new FHIR operation name or simply an updated version. If it's an updated version should be have the ability to call by version number and what we do to ensure we maintain backwards compatibility if we move forwards with adding something like risks i.e. - how do we ensure no breaking changes.

            Assignee:
            Unassigned
            Reporter:
            Craig Newman
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: