Comment:

Seemed like a burdensome set of potential attributes (would consume an extra big increment of provider time if many of them had to be entered). Worse, there were no examples of the answer lists (value set, coding systems) that were being considered to give a clearer idea of how it would be used. I realize that most are optional, but some guidance about when they would not have to be used could prevent aggressive administrators/compliance officers from requiring them.

In many respects it could serve as a problem oriented note almost en toto. Have not yet seen how notes are evolving so there may have been some method to the madness. Would have helped a lot to show what might be the minimum of these attributes required for a typical problem list...

There were no examples of the kinds of codes that would actually be used, to give meaning to the purpose. Was particularly concerned about: Condition.clinicalStatus and Condition.verificationStatus, both of which were required. Could guess that the first might have codes saying active or inactive- and that makes sense, but no code list, even as examples were given. Have never heard of condition verification status in 40 years of practice.

Regarding the condition body site. Though it is optional, it would help to assert that it the body site is often embedded in the problem ID/name. As is true of Pneumonia, Heart attack. Acute pancreatitis. And even things like hip fracture and acute abdomen

Summary:

Overall Condition.clinicalStatus and Condition.verificationStatus Condition body site