OpenMRS Core FHIR Implementation Guide
0.1.0 - ci-build

OpenMRS Core FHIR Implementation Guide - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

: Search through condition endpoint by date when the record was created - JSON Representation

Active as of 2024-12-11

Raw json | Download

{
  "resourceType" : "SearchParameter",
  "id" : "condition-recorded-date",
  "text" : {
    "status" : "generated",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: SearchParameter condition-recorded-date</b></p><a name=\"condition-recorded-date\"> </a><a name=\"hccondition-recorded-date\"> </a><a name=\"condition-recorded-date-en-US\"> </a><h2>ConditionRecordedDateSearchParameter</h2><p>Parameter <code>recorded-date</code>:<code>date</code></p><div><p>Searches for condition based on the condition creation date eg) /ws/fhir2/{release}/Condition?recorded-date={date}</p>\n</div><table class=\"grid\"><tr><td>Resource</td><td><a href=\"http://hl7.org/fhir/R4/condition.html\">Condition</a></td></tr><tr><td>Expression</td><td>(none)</td></tr><tr><td>Target Resources</td><td><a href=\"http://hl7.org/fhir/R4/condition.html\">Condition</a></td></tr><tr><td>Multiples</td><td><ul><li>multipleAnd: It's up to the server whether the parameter may repeat in order to specify multiple values that must all be true</li><li>multipleOr: It's up to the server whether the parameter can have multiple values (separated by comma) where at least one must be true</li></ul></td></tr></table></div>"
  },
  "url" : "http://fhir.openmrs.org/core/SearchParameter/condition-recorded-date",
  "version" : "0.1.0",
  "name" : "ConditionRecordedDateSearchParameter",
  "status" : "active",
  "date" : "2024-12-11T17:17:27+00:00",
  "contact" : [
    {
      "name" : "OpenMRS, Inc.",
      "telecom" : [
        {
          "system" : "url",
          "value" : "https://openmrs.org"
        }
      ]
    }
  ],
  "description" : "Searches for condition based on the condition creation date eg) /ws/fhir2/{release}/Condition?recorded-date={date}",
  "code" : "recorded-date",
  "base" : [
    "Condition"
  ],
  "type" : "date",
  "target" : [
    "Condition"
  ]
}