SIMPLIFIER.NET - FHIRPath Playground

FHIRPath

If you Log in or sign up, you can edit this script yourself.

<StructureDefinition xmlns="http://hl7.org/fhir">
  <id value="ba6c70e2-9880-445d-ac1e-e3d0f3f9f2a9" />
  <meta>
    <versionId value="1" />
    <lastUpdated value="2018-06-05T18:02:52.778+00:00" />
  </meta>
  <url value="http://rivta.se/fhir/StructureDefinition/core/se-core-vitalsigns-v1/BodyWeight" />
  <name value="PoCBodyWeight" />
  <status value="draft" />
  <date value="2018-06-05T18:02:51.279Z" />
  <description value="Measurement of the body weight of an individual.&#xD;&#xA;&#xD;&#xA;http://[domain]/fhir/[ConformanceResource]/[project]-[name]-[semver.major] " />
  <fhirVersion value="3.0.1" />
  <kind value="resource" />
  <abstract value="false" />
  <type value="Observation" />
  <baseDefinition value="http://rivta.se/fhir/StructureDefinition/se-core-vitalsigns-v1/Observation " />
  <derivation value="constraint" />
  <differential>
    <element id="Observation.category">
      <path value="Observation.category" />
      <code>
        <system value="http://hl7.org/fhir/observation-category" />
        <code value="vital-signs" />
      </code>
      <definition value="A code that classifies the general type of observation being made.&#xD;&#xA;//Vital sign är det värde//" />
    </element>
    <element id="Observation.code.coding.system">
      <path value="Observation.code.coding.system" />
      <fixedUri value="http://snomed.info/sct" />
    </element>
    <element id="Observation.code.coding.code">
      <path value="Observation.code.coding.code" />
      <fixedCode value="27113001" />
    </element>
    <element id="Observation.code.coding.display">
      <extension url="http://hl7.org/fhir/StructureDefinition/elementdefinition-translatable">
        <valueBoolean value="true" />
      </extension>
      <path value="Observation.code.coding.display" />
      <fixedString value="g" />
      <binding>
        <strength value="required" />
        <description value="UCUM" />
      </binding>
    </element>
    <element id="Observation.context">
      <path value="Observation.context" />
      <definition value="The healthcare event  (e.g. a patient and healthcare provider interaction) during which this observation is made.&#xD;&#xA;//konceptet saknar motsvarighet i svensk vård och omsorg system-EpisodOfCare, det kan likna närmaste hälsoärende//" />
      <type>
        <code value="Reference" />
        <targetProfile value="http://hl7.org/fhir/StructureDefinition/Encounter" />
        <aggregation value="referenced" />
      </type>
    </element>
    <element id="Observation.context.reference">
      <path value="Observation.context.reference" />
      <fixedString value="urn:oid:hsa//kallsystemet" />
    </element>
    <element id="Observation.context.identifier">
      <path value="Observation.context.identifier" />
      <comment value="When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. &#xA;&#xA;When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference&#xA;&#xA;Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.&#xD;&#xA;// en referens eller identifierare till en vårdkontakt, internid, logiskreferens, en id det ska användas, källsystemetsHSAid och id- system och value, //" />
      <fixedIdentifier>
        <system value="urn:oid:hsaoid?" />
      </fixedIdentifier>
    </element>
    <element id="Observation.effective[x]">
      <path value="Observation.effective[x]" />
      <definition value="The time or time-period the observed value is asserted as being true. For biological subjects - e.g. human patients - this is usually called the &quot;physiologically relevant time&quot;. This is usually either the time of the procedure or of specimen collection, but very often the source of the date/time is not known, only the date/time itself. // vi använder date time för observation.tid//" />
    </element>
    <element id="Observation.performer">
      <path value="Observation.performer" />
      <comment value="References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Motsvarar deltagare typ ...// i barnhälsodataanvänds bara practitioner och organisation, titta p exemple profilen//" />
    </element>
    <element id="Observation.performer.identifier:HSAid">
      <path value="Observation.performer.identifier" />
      <sliceName value="HSAid" />
      <comment value="When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. &#xA;&#xA;When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference&#xA;&#xA;Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.&#xD;&#xA;//HSAid kan vara både person och organisation- hur kopplar vi att det är en organsiation eller en person//&#xD;&#xA;" />
    </element>
    <element id="Observation.value[x]:valueQuantity">
      <path value="Observation.valueQuantity" />
      <sliceName value="valueQuantity" />
      <type>
        <code value="Quantity" />
      </type>
    </element>
    <element id="Observation.specimen">
      <path value="Observation.specimen" />
      <max value="0" />
    </element>
    <element id="Observation.device">
      <path value="Observation.device" />
      <comment value="An extension should be used if further typing of the device is needed.  Devices used to support obtaining an observation can be represented using either an extension or through the Observation.related element.// vi har inte och kommer inte att ha någon tjänstekontrakt för att leverera information om det!//vi beslutar vi att inte ange device- det ska finnas en implementationsguide//" />
    </element>
    <element id="Observation.component">
      <path value="Observation.component" />
      <comment value="For a discussion on the ways Observations can be assembled in groups together see [Notes](observation.html#notes) below. (Referens till journaluppgift)// det kan användas för sysytolisk och diastolisk blodtryck//" />
      <max value="0" />
    </element>
  </differential>
</StructureDefinition>

name : PoCBodyWeight

{

}

<name value="PoCBodyWeight" />