Create a condition

post

/Condition

Creates a new condition.

Note:

  • The following restrictions are in place based on Condition.category:
    • For conditions with a category code of diagnosis:
      • Condition.encounter is required.
      • Condition.abatementDateTime is not supported.
    • For conditions with a category code of problem:
      • If Condition.dateRecorded is set in the request body, its value is currently ignored.
    • Creating conditions with a category code of health-concern is not currently supported.
  • The code.coding field can have at most two codings.
    • One of the codings must have userSelected: true.
    • The other coding must have userSelected: false.
  • A condition with a category code of diagnosis is automatically prioritized as the least significant priority by the Millennium electronic health record.

Authorization Types

This operation supports the following authorization types:

  • Provider
  • System

Request

Supported Media Types
Header Parameters
Body ()
The body of the create operation
Root Schema : ConditionCreateBody
Type: object
Show Source
  • Indicates if the condition is resolved or has gone into remission.
    Example: true
  • The date or estimated date that the condition resolved or went into remission.
    Example: 2015-10-14T13:13:20-06:00
  • A category assigned to the condition.
    Example: { "coding": [ { "system": "http://hl7.org/fhir/condition-category", "code": "diagnosis", "display": "Diagnosis" } ], "text": "Diagnosis" }
  • The clinical status of the condition.
    Example: resolved
  • Identification of the condition, problem, or diagnosis.
    Example: { "coding": [ { "system": "http://hl7.org/fhir/sid/icd-9-cm", "code": "345.0", "display": "Generalized nonconvulsive epilepsy", "userSelected": true } ], "text": "Absence seizures" }
  • The encounter during which the condition was first asserted.
    Note: Required when the condition category code is encounter-diagnosis.
    Example: { "reference": "Encounter/1309819" }
  • Additional information about the condition.
    Example: Information related to condition
  • The estimated or actual date or date and time when the condition began, in the opinion of the clinician.
    Note:
    • Only a type of dateTime is supported.
    • The dateTime is converted to a GMT date.
    Example: 2015-10-14T13:13:20-06:00
  • Who has the condition.
    Example: { "reference": "Patient/2744123", "display": "Joe, Test" }
  • The FHIR resource type. resourceType must be Condition.
    Example: Condition
  • The assessment of the severity of the condition as evaluated by the clinician.
    Example: { "coding": [ { "system": "http://snomed.info/sct", "code": "371923003", "display": "Mild to moderate" } ], "text": "Mild to moderate" }
  • The verification status to support or decline the clinical status of the condition or diagnosis.
    Example: confirmed
Example:
{
  "resourceType": "Condition",
  "patient": {
    "reference": "Patient/12724066"
  },
  "code": {
    "text": "Freetext Diagnosis"
  },
  "category": {
    "coding": [
      {
        "system": "http://hl7.org/fhir/condition-category",
        "code": "diagnosis",
        "display": "Diagnosis"
      }
    ],
    "text": "Diagnosis"
  },
  "clinicalStatus": "active",
  "verificationStatus": "differential",
  "encounter": {
    "reference": "Encounter/97953477"
  }
}
Back to Top

Response

Supported Media Types

201 Response

Example Request:
POST https://fhir-ehr-code.cerner.com/dstu2/ec2458f2-1e24-41c8-b71b-0e701af7583d/Condition
Example Response:
  Date: Tue, 28 Feb 2017 21:26:37 GMT
  Cache-Control: no-cache
  Vary: Origin,User-Agent,Accept-Encoding
  Strict-Transport-Security: max-age=631152000
  X-Xss-Protection: 1; mode=block
  Pragma: no-cache
  Etag: W/"6809861"
  X-Frame-Options: SAMEORIGIN
  X-Content-Type-Options: nosniff
  Expires: Mon, 01 Jan 1990 00:00:00 GMT
  Last-Modified: Tue, 28 Feb 2017 21:26:44 GMT
  Location: https://fhir-ehr-code.cerner.com/dstu2/ec2458f2-1e24-41c8-b71b-0e701af7583d/Condition/p6809861
  Content-Length: 0
  Content-Type: application/json
  X-Request-Id: 11111111111111111111111111111111
The ETag response header indicates the current If-Match version to use on a subsequent update.
Back to Top