Mock up of US Core Condition, Problem, SDOH Problem and Encounter

What will change?:

What is same:

Downstream consequences:

Proposal is to Split US Core Condition Profile in Problems/HC and Encounter Conditions







hierarchy



US Core Condition Profile

US Core Condition Profile



US Core Problems/Health Concerns Profile \n(Includes SDOH Health Concerns)

US Core Problems/Health Concerns Profile 
(Includes SDOH Health Concerns)



US Core Condition Profile->US Core Problems/Health Concerns Profile \n(Includes SDOH Health Concerns)





US Core Encounter Diagnosis Profile

US Core Encounter Diagnosis Profile



US Core Condition Profile->US Core Encounter Diagnosis Profile





  1. We will require support for each profile separately
  2. Can customize documentation of QuickStart for each, but in CapabilityStatements search is defined by type.

US Core Problems/Health Concerns Profile

Each Condition must have:

  1. a category code of ‘problem-list-item’ or ‘health-concern’
  2. a code that identifies the condition
  3. a patient

Each Condition must support:

  1. a clinical status of the condition* (e.g., “active” or “resolved”)
  2. a verification status
  3. a category code of ‘sdoh’*
  4. a date of diagnosis*
  5. a date of resolution
  6. a date when recorded*

*see implementation guidance

Examples:

US Core Encounter Diagnosis Profile

Each Condition must have:

  1. a category code of ‘encounter-diagnosis’
  2. a code that identifies the condition
  3. a patient

Each Condition must support:

  1. a clinical status of the condition* (e.g., “active” or “resolved”)
  2. a verification status
  3. an encounter
  4. a date of diagnosis*
  5. a date of resolution
  6. a date when recorded*

*see implementation guidance

Example: