athenahealth / apiserver-athenaFlex

Software developers can use sample code and documentation to use athenahealth's athenaPractice/athenaFlow FHIR API Server.
https://mydata.athenahealth.com/home
17 stars 7 forks source link

Condition API - How do we differentiate between Current Problem and Past Medical History from the response. #264

Closed satishjayakumar closed 1 year ago

satishjayakumar commented 1 year ago

We generally use condition.category to differentiate between Current Problem and Past Medical History, but here I see the category value is always ‘problem-list-item’ for both Problem and Past medical history.

Torin-Shepard-athena commented 1 year ago

@satishjayakumar With athenaPractice and athenaFlow, it is best to use clinicalstatus, verificationstatus, onset[x], abatement[x], recordedDate elements to understand the history and evolution of Condition resources that represent the Problem list in a patient Chart.

The 3 concepts in US Core Condition Category Codes value set are not intended to give information about past medical history.

The FHIR and US Core distinction between problem-list-item and encounter-diagnosis is very subtle and not easy to understand. A future version athenaPractice and athenaFlow may interpret these as identical and list both FHIR categories for each problem. All Condition resources have a link to an Encounter and that are all considered to be both problem list items and encounter diagnoses.

problem-list-item entries are items put on the problem list by practitioners.

health-concern entries are items explained by a patient, are uncoded, and can be associated with Goal resources.

AjeetYadav07 commented 1 year ago

@satishjayakumar, Closing this ticket. If you any questions further please register a new issue.