Enumerate required search paramters rather than specific combinations of search parameters - USCore #143

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • US Core (FHIR)
    • STU3
    • Structured Documents
    • Profiles and Extensions
    • Hide

      Make it clear in the profiles the searches enumeraated are the base expectations on what a FHIR server supports.

      Add new search parameters page that servers WILL support additional query combinations and that implementers should submit combination proposals for consideration in future updates.

      Show
      Make it clear in the profiles the searches enumeraated are the base expectations on what a FHIR server supports. Add new search parameters page that servers WILL support additional query combinations and that implementers should submit combination proposals for consideration in future updates.
    • Brett Marquard/Claude Nanjo: 24-0-0
    • Enhancement
    • Non-substantive

      Comment:

      Instead of enumerating the specific combinations of query parmaters that are required, identify the individual query paramters that must be supported. E.g., instead of saying – DiagnosticReport must support search by "patient + category", "patient + code", and "patient + category + date", require that searches must support searches by patient, category, code, and date. Without this, for example, it is implied that an EHR does not need to support "patient + code + date" as a search pattern, even though what an EHR must implement to support the enumerated combinations would imply that there should be little additional effort to support that specific combination. Further restrictions could still be added – such as that "patient" must always be in the query. Comments applies to all US Core FHIR profiles.

      Summary:

      Enumerate required search paramters rather than specific combinations of search parameters

            Assignee:
            Unassigned
            Reporter:
            Kensaku Kawamoto
            Kensaku Kawamoto
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: