Explain FHIRPath libraries better - SDC #13

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • Structured Data Capture (SDC) (FHIR)
    • STU3
    • FHIR Infrastructure
    • (profiles) [deprecated]
    • 5.1 Use of the Expre
    • Hide

      In SDC, we will extend the existing CQL library to add slices that support FHIRPath (0..) and FHIRQuery (0..) in addition to the existing 0..1 and 0..1 for raw and compiled CQL. Will then submit a change request proposing that the current CQL Library profile be revised to an Expression profile that adopts our additions.

      Show
      In SDC, we will extend the existing CQL library to add slices that support FHIRPath (0.. ) and FHIRQuery (0.. ) in addition to the existing 0..1 and 0..1 for raw and compiled CQL. Will then submit a change request proposing that the current CQL Library profile be revised to an Expression profile that adopts our additions.
    • Bryn Rhodes/Nagesh Bashyam: 6-0-0
    • Correction
    • Compatible, substantive

      Existing Wording: ...If the expression is blank for CQL or if conveying FHIRPath or a query, the specific reference URL must look like this:

      [canonical URL of library]#[id element of the 'content' repetition whose Attachment.data holds the expression] E.g. http://somewhere.org/fhir/Library/12345#a2

      Comment:

      If I read this correctly, SDC specifies that Library resources can have a library of FHIRPath expressions, each expression in a separate Attachement.

      This an intesting case but does require more description, including a profile of its own to indicate the library is structured as described.

      Summary:

      Explain FHIRPath libraries better

            Assignee:
            Unassigned
            Reporter:
            Bas van den Heuvel
            Bas van den Heuvel
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: