eHealth Infrastructure



<OperationDefinition xmlns="http://hl7.org/fhir">
  <id value="-s-get-patient-procedures"/>
  <text>
    <status value="extensions"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><h2>get-patient-procedures</h2><p>OPERATION: get-patient-procedures</p><p>The official URL for this operation definition is: </p><pre>http://ehealth.sundhed.dk/fhir/OperationDefinition/-s-get-patient-procedures</pre><div><p>This operation returns an overview of patient procedures within a time period and filtered by either EpisodeOfCare or Condition code(s). On success, the returned Bundle contains a Parameters structure detailing the count of measurements received and expected. This is done per ProcedureRequest with status active for those that are related to EpisodeOfCare either given as input or pertaining to one of the Condition codes. The measurement regime expressed in ProcedureRequest.occurrence[x] is, when possible, resolved to time slot(s) corresponding to datetime/period where an action is supposed to take place, typically performed by the Patient. When the occurrenceTiming variant is used, resolved time slots overlapping with the input time periode are considered. For occurrenceTiming expression which are either adhoc or unresolved, the effective datetime/period of a measurement is considered when checked for overlap with input time period.</p>
<h2>Input</h2>
<p>The operation has three mandatory inputs, a Patient reference, a start date and an end date. Additionally the operation has two optional inputs: a list of reference(s) to EpisodeOfCare and a list of Codings for Condition.</p>
<h3>Patient reference</h3>
<p>Mandatory reference for the Patient which the procedure overview is computed for.</p>
<h3>Start and end datetimes</h3>
<p>Start and end datetime are both mandatory, and together specify the period of interest in the patient procedure overview. As stated above, for resolvable past and future time slots as well as adhoc and unresolved timings there must overlap with this period.</p>
<h3>EpisodeOfCare list</h3>
<p>The EpisodeOfCare list is optional, but either of EpisodeOfCare or Condition codes must be provided. If EpisodeOfCare are provided, these will be used to further filter which active CarePlan and ProcedureRequest are considered for the patient procedure overview.</p>
<h3>Condition Coding list</h3>
<p>The list of Coding for Condition is optional, but either of EpisodeOfCare or Condition codes must be provided. If Condition Coding are provided, the EpisodeOfCare considered are those referring to a Condition matching at least one of the codes in the list. As above, the EpisodeOfCare (one or more) considered further determines which active CarePlan and ProcedureRequest are considered.</p>
<h2>Output</h2>
<p>For valid inputs, the server will compute and return a Bundle. The Bundle contains a Parameters resource with resolved measurement regimes and associated counts of measurement submitted and counts expected. Such counts are also included in the Parameters structure when the measurement regime is either adhoc or unresolved. In addition, the Bundle contains CarePlan and ProcedureRequest referenced in the Parameters. The Bundle can contain an OperationOutcome describing any encountered warnings.</p>
</div><p>URL: [base]/$get-patient-procedures</p><p>Parameters</p><table class="grid"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>patient</td><td>1..1</td><td><a href="http://hl7.org/fhir/STU3/references.html#Reference">Reference</a></td><td/><td/></tr><tr><td>IN</td><td>episodeOfCare</td><td>0..*</td><td><a href="http://hl7.org/fhir/STU3/references.html#Reference">Reference</a></td><td/><td/></tr><tr><td>IN</td><td>conditionCodings</td><td>0..*</td><td><a href="http://hl7.org/fhir/STU3/datatypes.html#Coding">Coding</a></td><td/><td/></tr><tr><td>IN</td><td>start</td><td>1..1</td><td><a href="http://hl7.org/fhir/STU3/datatypes.html#dateTime">dateTime</a></td><td/><td/></tr><tr><td>IN</td><td>end</td><td>1..1</td><td><a href="http://hl7.org/fhir/STU3/datatypes.html#dateTime">dateTime</a></td><td/><td/></tr><tr><td>OUT</td><td>return</td><td>0..1</td><td><a href="http://hl7.org/fhir/STU3/bundle.html">Bundle</a></td><td/><td/></tr></table></div>
  </text>
  <url
       value="http://ehealth.sundhed.dk/fhir/OperationDefinition/-s-get-patient-procedures"/>
  <name value="get-patient-procedures"/>
  <status value="active"/>
  <kind value="operation"/>
  <date value="2021-05-06T07:41:40+00:00"/>
  <description
               value="This operation returns an overview of patient procedures within a time period and filtered by either EpisodeOfCare or Condition code(s). On success, the returned Bundle contains a Parameters structure detailing the count of measurements received and expected. This is done per ProcedureRequest with status active for those that are related to EpisodeOfCare either given as input or pertaining to one of the Condition codes. The measurement regime expressed in ProcedureRequest.occurrence[x] is, when possible, resolved to time slot(s) corresponding to datetime/period where an action is supposed to take place, typically performed by the Patient. When the occurrenceTiming variant is used, resolved time slots overlapping with the input time periode are considered. For occurrenceTiming expression which are either adhoc or unresolved, the effective datetime/period of a measurement is considered when checked for overlap with input time period.
## Input
The operation has three mandatory inputs, a Patient reference, a start date and an end date. Additionally the operation has two optional inputs: a list of reference(s) to EpisodeOfCare and a list of Codings for Condition.
### Patient reference
Mandatory reference for the Patient which the procedure overview is computed for.
### Start and end datetimes
Start and end datetime are both mandatory, and together specify the period of interest in the patient procedure overview. As stated above, for resolvable past and future time slots as well as adhoc and unresolved timings there must overlap with this period.
### EpisodeOfCare list
The EpisodeOfCare list is optional, but either of EpisodeOfCare or Condition codes must be provided. If EpisodeOfCare are provided, these will be used to further filter which active CarePlan and ProcedureRequest are considered for the patient procedure overview.
### Condition Coding list
The list of Coding for Condition is optional, but either of EpisodeOfCare or Condition codes must be provided. If Condition Coding are provided, the EpisodeOfCare considered are those referring to a Condition matching at least one of the codes in the list. As above, the EpisodeOfCare (one or more) considered further determines which active CarePlan and ProcedureRequest are considered.
## Output
For valid inputs, the server will compute and return a Bundle. The Bundle contains a Parameters resource with resolved measurement regimes and associated counts of measurement submitted and counts expected. Such counts are also included in the Parameters structure when the measurement regime is either adhoc or unresolved. In addition, the Bundle contains CarePlan and ProcedureRequest referenced in the Parameters. The Bundle can contain an OperationOutcome describing any encountered warnings."/>
  <idempotent value="false"/>
  <code value="get-patient-procedures"/>
  <system value="true"/>
  <type value="false"/>
  <instance value="false"/>
  <parameter>
    <name value="patient"/>
    <use value="in"/>
    <min value="1"/>
    <max value="1"/>
    <type value="Reference"/>
  </parameter>
  <parameter>
    <name value="episodeOfCare"/>
    <use value="in"/>
    <min value="0"/>
    <max value="*"/>
    <type value="Reference"/>
  </parameter>
  <parameter>
    <name value="conditionCodings"/>
    <use value="in"/>
    <min value="0"/>
    <max value="*"/>
    <type value="Coding"/>
  </parameter>
  <parameter>
    <name value="start"/>
    <use value="in"/>
    <min value="1"/>
    <max value="1"/>
    <type value="dateTime"/>
  </parameter>
  <parameter>
    <name value="end"/>
    <use value="in"/>
    <min value="1"/>
    <max value="1"/>
    <type value="dateTime"/>
  </parameter>
  <parameter>
    <name value="return"/>
    <use value="out"/>
    <min value="0"/>
    <max value="1"/>
    <type value="Bundle"/>
  </parameter>
</OperationDefinition>