Simplify CDA identifier searching - 2018-May Core Norm Infrastructure #42

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive with Modification
    • Priority: High
    • FHIR Core (FHIR)
    • STU3
    • Modeling & Methodology
    • Datatypes
    • 2.23.0.11
    • Hide

      No need for a change to rule. To handle this CDA use-case, you can do a single search using this syntax:

      identitier=|[root],[root]

      That will find cases where the specified OID is either the value or the system.

      Will add this into the specification in the search spec and in the mapping to II.

      Show
      No need for a change to rule. To handle this CDA use-case, you can do a single search using this syntax: identitier=| [root] , [root] That will find cases where the specified OID is either the value or the system. Will add this into the specification in the search spec and in the mapping to II.
    • Ron Shapiro/Grahame Grieve: 2-0-0
    • Non-substantive
    • STU3

      Existing Wording: If the identifier value itself is naturally a globally unique URI (e.g. an OID, a UUID, or a URI with no trailing local part), then the?system?SHALL be "urn:ietf:rfc:3986", and the URI is in the?value?(OIDs and UUIDs using urn:oid: and urn:uuid: - see?note on the V3 mapping?and the?examples).

      Comment:

      Because of this clause, search on a CDA identifier is difficult, ,as you need to look for the document id in both the value and system depending on whether an extension is used.

      We need a better solution for searching CDA document ids

      Summary:

      Simplify CDA identifier searching

            Assignee:
            Unassigned
            Reporter:
            Elliot Silver
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: