JanuSync Implementation Guide
1.0.0 - trial-use Korea, Republic of flag

JanuSync Implementation Guide - Local Development build (v1.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

: janusync-servicerequest-surgery-example - XML Representation

Raw xml | Download


<ServiceRequest xmlns="http://hl7.org/fhir">
  <id value="janusync-servicerequest-surgery-example"/>
  <meta>
    <profile
             value="http://connectdtx.kr/fhir/StructureDefinition/janusync-servicerequest"/>
  </meta>
  <extension
             url="http://connectdtx.kr/fhir/StructureDefinition/JanuSyncAdministrationAnesthesias">
    <valueCodeableConcept>
      <coding>
        <system value="http://snomed.info/sct"/>
        <code value="50697003"/>
        <display value="General anesthesia"/>
      </coding>
    </valueCodeableConcept>
  </extension>
  <identifier>
    <system value="urn:oid:1.2.410.100110.10.11100123"/>
    <value value="order12345"/>
  </identifier>
  <status value="active"/>
  <intent value="order"/>
  <category>
    <coding>
      <system value="http://snomed.info/sct"/>
      <code value="387713003"/>
      <display value="Surgical procedure"/>
    </coding>
  </category>
  <code>
    <coding>
      <system value="urn:oid:1.2.410.100110.10.11100123"/>
      <code value="S0101"/>
      <display value="Whipple procedure"/>
    </coding>
  </code>
  <subject>🔗 
    <reference value="Patient/janusync-patient-example"/>
  </subject>
  <encounter>🔗 
    <reference value="Encounter/janusync-encounter-imp-example"/>
  </encounter>
  <occurrenceDateTime value="2024-02-23T16:00:00+09:00"/>
  <authoredOn value="2024-02-01T14:05:00+09:00"/>
  <requester>🔗 
    <reference
               value="PractitionerRole/janusync-medicaldoctor-practitionerrole-example"/>
  </requester>
  <performer>🔗 
    <reference
               value="PractitionerRole/janusync-medicaldoctor-practitionerrole-example"/>
  </performer>
  <reasonReference>🔗 
    <reference value="Condition/janusync-condition-example"/>
  </reasonReference>
</ServiceRequest>