EHMI Addressing Service (EAS)
0.8.1 - ci-build Denmark flag

EHMI Addressing Service (EAS), published by MedCom. This guide is not an authorized publication; it is the continuous build for version 0.8.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/medcomdk/dk-ehmi-eas/ and changes regularly. See the Directory of published versions

: EAS SikrGrp1 getReceivingOrganizationByPatientId - error1c - XML Representation

Draft as of 2024-06-01

Raw xml | Download



<OperationDefinition xmlns="http://hl7.org/fhir">
  <id value="eas.SikrGrp1-getReceivingOrganizationByPatientId-error1c"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: OperationDefinition eas.SikrGrp1-getReceivingOrganizationByPatientId-error1c</b></p><a name="eas.SikrGrp1-getReceivingOrganizationByPatientId-error1c"> </a><a name="hceas.SikrGrp1-getReceivingOrganizationByPatientId-error1c"> </a><a name="eas.SikrGrp1-getReceivingOrganizationByPatientId-error1c-da-DK"> </a><p>URL: [base]/$getSikrGrp1_getReceivingOrganizationByPatientId</p><p>URL: [base]/CapabilityStatement/[id]/$getSikrGrp1_getReceivingOrganizationByPatientId</p><p>Input parameters Profile:<a href="StructureDefinition-EasCorePatient.html">EasCorePatient</a></p><p>Output parameters Profile:<a href="StructureDefinition-EasOperationOutcome.html">EasOperationOutcome</a></p><h3>Parameters</h3><table class="grid"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Scope</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>target</td><td/><td>1..1</td><td><a href="http://hl7.org/fhir/R4/patient.html">Patient</a></td><td/><td><div><p>submitting the Patients Id would evoke this search operation</p>
</div></td></tr><tr><td>OUT</td><td>return</td><td/><td>0..1</td><td><a href="http://hl7.org/fhir/R4/operationoutcome.html">OperationOutcome</a></td><td/><td><div><p>The response is an OperationOutcome due to non-existing EER-data</p>
</div></td></tr></table><div><p>eas_SikrGrp1_getReceivingOrganizationByPatientId return MedComMessagingOrganization</p>
</div></div>
  </text>
  <url
       value="http://easbase.eas.dk/OperationDefinition/eas_SikrGrp1_getReceivingOrganizationByPatientId"/>
  <version value="0.8.1"/>
  <name value="EAS SikrGrp1 getReceivingOrganizationByPatientId - error1c"/>
  <title value="EAS SikrGrp1 getReceivingOrganizationByPatientId - error1c"/>
  <status value="draft"/>
  <kind value="query"/>
  <date value="2024-06-01T00:00:00+01:00"/>
  <publisher value="MedCom"/>
  <contact>
    <name value="MedCom"/>
    <telecom>
      <system value="url"/>
      <value value="https://www.medcom.dk"/>
    </telecom>
  </contact>
  <description
               value="GET [EAS-base]/Organization?_profile=http://medcomfhir.dk/ig/messaging/StructureDefinition-medcom-messaging-organization&amp;Patient?Identifier.value=[Patient_Identifier]&amp;system=urn:oid:1.2.208.176.1.2
This search will produce a MedComMessagingOrganization as a response
EAS will in order to produce this response run through a sequence of calls from"/>
  <jurisdiction>
    <coding>
      <system value="urn:iso:std:iso:3166"/>
      <code value="DK"/>
      <display value="Denmark"/>
    </coding>
  </jurisdiction>
  <code value="getSikrGrp1_getReceivingOrganizationByPatientId"/>
  <comment
           value="eas_SikrGrp1_getReceivingOrganizationByPatientId return MedComMessagingOrganization"/>
  <resource value="CapabilityStatement"/>
  <system value="true"/>
  <type value="false"/>
  <instance value="true"/>
  <inputProfile
                value="http://medcomehmi.dk/ig/dk-ehmi-eas/StructureDefinition/EasCorePatient"/>
  <outputProfile
                 value="http://medcomehmi.dk/ig/dk-ehmi-eas/StructureDefinition/EasOperationOutcome"/>
  <parameter>
    <name value="target"/>
    <use value="in"/>
    <min value="1"/>
    <max value="1"/>
    <documentation
                   value="submitting the Patients Id would evoke this search operation"/>
    <type value="Patient"/>
  </parameter>
  <parameter>
    <name value="return"/>
    <use value="out"/>
    <min value="0"/>
    <max value="1"/>
    <documentation
                   value="The response is an OperationOutcome due to non-existing EER-data"/>
    <type value="OperationOutcome"/>
  </parameter>
</OperationDefinition>