Create a condition
post
/Condition
Creates a new condition.
Note:
- Only the fields below are supported. Unsupported fields are ignored.
- Do not provide modifier fields because they cause the transaction to fail.
- The
code.coding
field can have multiple codings. However, only one foruserSelected=true
and one foruserSelected=false
are written to Millennium. - Currently, only conditions with a category of
problem-list-item
orencounter-diagnosis
are supported. - An
encounter-diagnosis
condition is automatically prioritized as the least significant priority by the Millennium electronic health record (EHR). - On a FHIR write of an encounter-diagnosis, the diagnosis automatically receives the next available diagnosis priority in the problem list component.
Authorization Types
This operation supports the following authorization types:
Request
Supported Media Types
- application/json+fhir
Header Parameters
-
Authorization(required): string
Contains the credentials to authenticate a consumer to the service. This should be the OAuth2 Bearer token.
-
accept(required): string
The media type to be requested. See what the resource's operation produces for what is supported.
-
content-type(required): string
Specifies the content type of the request entity body.
The body of the create operation
Root Schema : ConditionCreateBody
Type:
Show Source
object
-
abatementDateTime:
string
The date or estimated date that the condition resolved or went into remission.
Note: Not supported for conditions with a category ofencounter-diagnosis
.Example:2015-10-14T13:13:20-06:00
-
category(required):
A category assigned to the condition.
Note:- Only a single category may be provided.
- The
problem-list-item
andencounter-diagnosis
category codes are supported. - Classification codes are not supported.
Example:[ { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/condition-category", "code": "problem-list-item", "display": "Problem List Item" } ], "text": "Problem List Item" } ]
-
clinicalStatus:
The clinical status of the condition.
Note:- A
clinicalStatus
must always be provided while creating a condition. - Only the
active
code is supported when the category isencounter-diagnosis
.
Example:{ "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/condition-clinical", "code": "resolved", "display": "Resolved" } ], "text": "Resolved" }
- A
-
code(required):
Identification of the condition, problem, or diagnosis.Example:
{ "coding": [ { "system": "http://snomed.info/sct", "code": "209832007", "display": "Concussion NOS (disorder)", "userSelected": true } ], "text": "Concussion with loss of consciousness" }
-
encounter:
The encounter during which the condition was first asserted.
Note:- Must be a reference to an encounter.
- Required when the condition category code is
encounter-diagnosis
.
-
note:
Additional information about the condition. This is a general notes or comments entry for a description of the condition, its diagnosis, and prognosis.
Note: Does not allow updates.Example:[ { "authorReference": { "reference": "Practitioner/4594011", "display": "Leroux, Erik" }, "text": "Test Comment 2" } ]
-
onsetDateTime:
string
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
- Only a type of
-
resourceType(required):
string
The FHIR resource type.
resourceType
must beCondition
.Example:Condition
-
severity:
A subjective assessment of the severity of the condition as evaluated by the clinician.Example:
{ "coding": [ { "system": "http://snomed.info/sct", "code": "255604002", "display": "Mild" } ] }
-
subject(required):
The patient who the condition record is associated with. Must be a reference to a patient.Example:
{ "reference": "Patient/631923", "display": "Nilsson, Christine" }
-
verificationStatus:
The verification status to support or decline the clinical status of the condition or diagnosis.
Note:verificationStatus
codes ofentered-in-error
andrefuted
are not supported when creating a condition.Example:{ "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/condition-ver-status", "code": "confirmed", "display": "Confirmed" } ], "text": "Confirmed" }
Example:
{
"resourceType": "Condition",
"abatementDateTime": "2015-10-14T13:13:20-06:00",
"category": [
{
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/condition-category",
"code": "problem-list-item",
"display": "Problem List Item TEST"
}
]
}
],
"clinicalStatus": {
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/condition-clinical",
"code": "resolved",
"display": "Resolved"
}
],
"text": "Resolved"
},
"code": {
"coding": [
{
"system": "http://snomed.info/sct",
"code": "confirmed",
"display": "confirmed_display"
}
],
"text": "confirmed_text"
},
"encounter": {
"reference": "Encounter/98107594"
},
"note": [
{
"text": "ConditionNote"
}
],
"onsetDateTime": "2015-10-14T13:13:20-06:00",
"severity": {
"coding": [
{
"system": "http://snomed.info/sct",
"code": "255604002",
"display": "Mild"
}
]
},
"subject": {
"reference": "Patient/13034092"
},
"verificationStatus": {
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/condition-ver-status",
"code": "confirmed",
"display": "Confirmed"
}
],
"text": "Confirmed"
}
}
Response
Supported Media Types
- application/json+fhir
201 Response
Example Request:
POST https://fhir-ehr-code.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d/Condition
Example Response:
Cache-Control: no-cache
Content-Length: 0
Content-Type: text/html
Date: Wed, 14 Aug 2019 17:23:14 GMT
Etag: W/"12793861"
Location: https://fhir-ehr-code.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d/Condition/p12793861
Last-Modified: Wed, 14 Aug 2019 17:23:14 GMT
Vary: Origin
X-Request-Id: 11111111111111111111111111111111
The ETag response header indicates the current If-Match version to use on a subsequent update.