FHIR Chat · Condition.category · argonaut

Stream: argonaut

Topic: Condition.category


view this post on Zulip Jay Lyle (Feb 07 2018 at 21:41):

Argonaut Condition.category lists four values on the resource page (complaint | symptom | finding | diagnosis) and two on the linked value set page (problem & health-concern). The value set page also defines it as all codes from the system, which link contains the four values from the first page.

The binding is 'preferred.' What are Argonaut implementers choosing to use?

view this post on Zulip Michelle (Moseman) Miller (Feb 08 2018 at 02:04):

Cerner uses category codes of diagnosis, problem, and health-concern

Argonaut specific guidance says "The DAF Condition Category Codes support the separate concepts of problems and health concerns so API consumers can separate health concerns and problems. However this is not mandatory for 2015 certification"

Note: I have an outstanding change request, GF#13772, logged to clean up some of the US-Core duplicate codes (problem and problem-list-item), which manifested when Patient Care updated the DSTU3 value set.

view this post on Zulip Dave Carlson (Feb 08 2018 at 02:20):

Hi Michelle, can you clarify how and when 'diagnosis' category code is used? How does it differ from 'problem'?

view this post on Zulip Jay Lyle (Feb 08 2018 at 12:41):

Thanks. So, supporting the linked value set values, but taking advantage of the 'preferred' flexibility. Others?

view this post on Zulip Michelle (Moseman) Miller (Feb 08 2018 at 14:28):

@Dave Carlson

  • diagnosis -- encounter-specific conditions, which are typically coded in ICD-10 (or ICD-9) in the US. For example, E11.621 Type 2 diabetes mellitus with foot ulcer.
  • problem -- conditions that have been added to the problem list, which are typically coded in SNOMED and are not specific to a single encounter like diagnoses are. For example, 44054006 Diabetes mellitus type 2
  • health-concern -- any additional concerns expressed by the patient or related person, which are typically freetext (no coding).

In R4, a new extension has been added for condition-related, which would enable us to relate the encounter-specific diagnoses (e.g. E11.621 Type 2 diabetes mellitus with foot ulcer) with the problem (e.g. 44054006 Diabetes mellitus type 2)

view this post on Zulip Dave Carlson (Feb 09 2018 at 01:25):

Thank you @Michelle (Moseman) Miller this aligns with my general understanding of use, but your specific definitions and examples are very helpful!


Last updated: Apr 12 2022 at 19:14 UTC