Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for CQL manipulating BackboneElement types #1253

Open
JPercival opened this issue Oct 18, 2023 · 1 comment
Open

Support for CQL manipulating BackboneElement types #1253

JPercival opened this issue Oct 18, 2023 · 1 comment
Assignees

Comments

@JPercival
Copy link
Contributor

Not sure if this is still an issue. Please just close if the issue is resolved/fixed...

In CQL, we want to be able to return BackboneElement and child element types from (at least) functions. For example:

define function "MedicationRequestResource"(medicationRequest MedicationRequest, profileURLs List<FHIR.canonical>):
  medicationRequest m
  return MedicationRequest{
    id: FHIR.id {value: 'LCR-' + m.id},
    meta: MetaElement(medicationRequest, profileURLs),
    dosageInstruction: DosageInstructionElement(m.dosageInstruction),
    dispenseRequest: DispenseRequestElement(m.dispenseRequest)
  }

define function "DosageInstructionElement"(dosageInstruction Dosage):
  return Dosage {
    ...
  }

define function "DispenseRequestElement"(dispenseRequest BackboneElement):
  return BackboneElement {
    dispenseInterval: ...
    validityPeriod: ...
  }

Last I heard, there were issues dealing with these types of child elements and backbone elements.

@JPercival JPercival self-assigned this Oct 18, 2023
@JPercival
Copy link
Contributor Author

BackboneElements are generally abstract types in the FHIR spec, and are declared implicitly as part of an overall Resource definition. IOW, it's probably not valid to work with BackboneElement directly. I'll do a bit more research on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant