Condition

Base profile: https:/www.hl7.org/fhir/condition.html;

Common use cases include:

• Find all Conditions for a Patient
• Add a Condition to a Patient’s record
• Update a Condition’s status
• Route a Condition to a specific clipboard section (Problem List, Past Medical History, Ocular History, and others — see Clipboard Section Routing below)

The following attributes are supported:

The Following Operations are supported:

• Condition READ
• Condition SEARCH
• Condition CREATE
• Condition UPDATE

Clipboard Section Routing

By default, a Condition is filed under Problem List. To route it to a different clipboard section on create, include an identifier with system set to condition-type and value set to one of the codes below:

"identifier": [
  {
    "system": "condition-type",
    "value": "PMC"
  }
]

Notes:

• Routing is create-only. If the identifier is missing, or its value isn't one of the codes above, the Condition is silently filed under Problem List — this does not raise an error, so double-check the section a Condition lands in if you're relying on routing.
• On update, the clipboard section is instead determined by the Condition's own id (e.g. PMC|12345), not by identifier — you can't move an existing Condition to a different section via update.
• Availability of a given section can vary by specialty/practice configuration.

Filtering search by section: add identifier=condition-type|<code> to a Condition search to restrict results to one section (same codes as the table above, plus PROB for Problem List). Unlike create, an unrecognized code here returns an error rather than silently falling back. Omitting identifier entirely defaults to PROB (Problem List) — it does not mean "all sections."

For Past Surgical History and Ocular Surgical History specifically, use the separate Procedure resource instead of Condition — see that page for details.

Condition CREATE

Note that Conditions added or updated through the API will need to be reconciled by the Practice before those additions or changes will be added to the Patient’s chart. There is a UI to handle this on the front end.

The following attributes are required for a CREATE:

identifier is optional — see Clipboard Section Routing above for what happens when it's omitted or unrecognized.

Condition UPDATE

Note that Conditions added or updated through the API will need to be reconciled by the Practice before those additions or changes will be added to the Patient’s chart. There is a UI to handle this on the front end.

For the purposes of clarity, the following fields are immutable:

For the purposes of clarity, the following fields are supported for UPDATE: