How to handle bad input data. - ImmDS #8

XMLWordPrintableJSON

    • Type: Question
    • Resolution: Considered - Question answered
    • Priority: Medium
    • Immunization Forecast CDS (FHIR)
    • STU3
    • Public Health
    • (NA)
    • Use Cases
    • Hide

      We can add a section that explains how to use OperationOutcome (and other base resources) to express the error conditions

      Show
      We can add a section that explains how to use OperationOutcome (and other base resources) to express the error conditions
    • Craig Newman/Danny Wise: 20-0-0

      Comment:

      How should an immunization CDS engine respond if the patient or immunization information had logic errors that prevented calculating a proper response? For example if the administration date for the immunization was before the birth of the patient or the vaccination code was not recognized by the receiving system? In these cases it might not be possible to produce a sensible result or the result may be missing critical information. How does the server signal properly to the requestor that it was unable to respond and the reason why? Suggested by Brian Lee at STC.

      Summary:

      How to handle bad input data.

            Assignee:
            Unassigned
            Reporter:
            Nathan Bunker
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: