FHIR Chat · Dose-dense AC example · chemotherapy IG

Stream: chemotherapy IG

Topic: Dose-dense AC example

Lee Surprenant (Apr 11 2017 at 15:17):

here was my attempt for the MedicationRequests for dose-dense AC (but just the regimen itself)

Lee Surprenant (Apr 11 2017 at 15:17):

MedicationRequest-DOXOrubicin.xml MedicationRequest-Cyclophosphamide.xml

Lee Surprenant (Apr 11 2017 at 15:35):

height.xml
weight.xml

Lee Surprenant (Apr 11 2017 at 15:35):

note from sadiq: this should use the vital signs profiles

Sadiq Saleh (Apr 11 2017 at 15:36):

http://build.fhir.org/observation-vitalsigns.html

Lee Surprenant (Apr 11 2017 at 16:03):

regarding the daysOfCycle extension, here is what we are doing now:

<timing>
      <extension url="http://nccn.org/fhir/daysOfCycle">
        <extension url="day">
          <valueInteger value="1" />
        </extension>
      </extension>

this is what we used to do in the past:

<extension url="http://nccn.org/fhir/relativeTime">
  <extension url="base">
    <valueCode value="cycleStart" />
  </extension>
  <extension url="offset">
    <valueQuantity>
      <value value="0" />
      <unit value="d" />
    </valueQuantity>
  </extension>
</extension>

Lee Surprenant (Apr 11 2017 at 16:15):

@Daniel Lanphear I think a part of the reason we switched was something I overheard while talking with @Andrew Ross about how this is structured in iKnowMed. Does it sound familiar? Would love to take a poll or something to see how most systems represent this.

Marten Smits (Apr 11 2017 at 16:15):

 <extension url="http://nccn.org/fhir/daysOfCycle">
        <extension url="day">
          <valueInteger value="1" />
        </extension>
 </extension>

I see you use a complex extension, are there other elements that "day" optional in this extension?

Marten Smits (Apr 11 2017 at 16:16):

Why not use? :

 <extension url="http://nccn.org/fhir/daysOfCycle">       
         <valueInteger value="1" />       
 </extension>

Lee Surprenant (Apr 11 2017 at 16:16):

can valueInteger repeat?

Lee Surprenant (Apr 11 2017 at 16:17):

i think not and so we wanted each day separate inside a single extension

Marten Smits (Apr 11 2017 at 16:17):

No, but the extension can

Lee Surprenant (Apr 11 2017 at 16:18):

i'm not sure we should design around it, but we have examples similar to "on day 1, 2, and 3 OR on days 2, 3, and 4"

Lee Surprenant (Apr 11 2017 at 16:19):

possibly those could be split into two different MedicationRequest options (ActivityDefinition in our case)

Lee Surprenant (Apr 11 2017 at 16:19):

but keeping the list of days self-contained in single extension allows us to put them both on single ActivityDefinition (again, not sure if that is good reason or not)

Marten Smits (Apr 11 2017 at 16:22):

I get that, but I don't know if it's common practice in FHIR to solve that like this. Let me find out

Marten Smits (Apr 11 2017 at 16:25):

http://hl7.org/fhir/extensibility.html :
" Extensions can also contain extensions, either because the extension definition itself defines complex content - that is, a nested tree of values in the extension - or because the extension is extended with an additional extension defined separately. "

Marten Smits (Apr 11 2017 at 16:25):

Doesn't say anything about using it to make elements repeat

Last updated: Apr 12 2022 at 19:14 UTC