1 / 11

Concern Tracking

Concern Tracking. What is it and why??. Concern Tracking. I already have observation timing. Why do I need another structure?. <concern classCode='CONC' moodCode='EVN'> <activityTime xsi:type="ITVL' value='' /> <subject typeCode='SUBJ'> <observation classcode=OBS moodCode='EVN'>

satin
Download Presentation

Concern Tracking

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Concern Tracking What is it and why??

  2. Concern Tracking I already have observation timing. Why do I need another structure? <concern classCode='CONC' moodCode='EVN'> <activityTime xsi:type="ITVL' value='' /> <subject typeCode='SUBJ'> <observation classcode=OBS moodCode='EVN'> <templateId root='prob_obs_template;'> <code code='' codeSystem='' displayName='ASSERTION'/> <value xsi:type='CD' code='' codeSystem='' displayName='CHEST PAIN'> <originalText><ref id=''/></originalText> </value> <entryRelation classCode='REFR'> <observation classCode='OBS' moodCode='EVN'> <code code='' displayName='CLINICAL STATUS'> <value code='Intermittent'> </observation> </entryRelation> <entryRelation classCode='REFR'> <observation classCode='OBS' moodCode='EVN'> <code code='' displayName='SEVERITY'> <value code='SEVERE'> </observation> </entryRelation> <effectiveTime> <low value=''> <high value='' </effectiveTime> <activityTime xsi:type="TS" value=''> <statusCode code='completed'/> </observation> </subject> </concern> Chest Pain, severe Problem Observation Observation.code Observation.activityTime Concern WHY? Patient Symptoms Visit time Observation.effectiveTime.low Observation.effectiveTime.high

  3. Concern Tracking Its not the Named /Coded observation recorded in system at a single point in time. It spans time and the name/codes may change. Answer: Need way to track multiple observations with different names and times For example: Patient admitted, with R/O MI, Discharged with GERD, then has Follow up EGD where Barretts is found. Chest Pain r/o MI GERD Observation Barretts • Concern= • A subjective judgment of sameness in the observations reflecting the clinicians understanding of the disease process in the patient. • Only occurs In physicians mind – must be asserted • Indication of underlying disease process • Spans time • A problem list is a list of concerns, not a list of observations Concern Guideline: Aspirin, Heparin Guideline: Follow up EGD in 6 weeks Patient Symptoms Visit Its not good to assume that the reasons for therapy at one point in time apply to another. But how long does a observation hold? time

  4. Concern Tracking Patient admitted, with R/O MI, Discharged with GERD, then has Follow up EGD where Barretts is found. Chest Pain r/o MI GERD Observation Barretts It's not the disease course Disease may begin long before it is noticed (eg pregnancy), and may be of concern long after the disease is resolved (eg hx of cancer). Concern Patient Symptoms Visit time It's not related to the encounter. It may be completely within an encounter (eg transient hypokalemia) Or across multiple encounters (eg Diabetes)

  5. Concern Tracking Chest Pain r/o MI GERD Observation Barretts Diabetes, controlled Diabetes, uncontrolled Hypokalemia Other observations may occur at the same patient, but subjectively are not the same concern. Physicians typically think of and follow a single concern separate from another concern. Concern Patient Symptoms Visit time

  6. Concern Tracking Observation Chest Pain Diabetes, uncontrolled Diabetes, controlled Anxiety Anxiety Concerns May be merged Concern Patient Symptoms Visit time

  7. Concern Tracking Dyspnea CAD Observation Diabetes, controlled Diabetes, uncontrolled Hypokalemia Concerns may be split Asthma Concern Patient Symptoms Visit time

  8. Concern Tracking Chest Pain r/o MI GERD Observation Barretts Diabetes, controlled Diabetes, uncontrolled Hypokalemia Hypokalemia Concerns may be Related, or recurrent Concern SEQL Patient Symptoms Visit time

  9. Concern Tracking Aortic Stenosis (MEDCIN for clinical care) Aortic Stenosis or Regurgitation, Non-Rheumatic (ICD billing) Problem Observation The same concern may have multiple different, related observations for different purposes. The clinician should not be forced to code or post coordinate at the highest granularity because someone else has a different classification scheme. (ie "aortic stenosis with heart failure not from rheumatic disease.") Better to pick code for a purpose, where possible. This may be an inferred relationship, or mapped Heart Failure from Valvular disease (SNOMED classification for a rule trigger) Concern Patient Symptoms Visit time

  10. Concern Tracking Patient admitted, with R/O MI, Discharged with GERD, then has Follow up EGD where Barretts is found. Observation Prinovil 10mg "Another Blood pressure pill" Atenolol 50mg Atenolol 50mg Aspirin 325 Pepcid 20mg Concern Concern tracking isn't always problems. Medication Reconciliation has the same problem Visit time

  11. Concern Tracking Patient admitted, with R/O MI, Discharged with GERD, then has Follow up EGD where Barretts is found. Observation EES "An antibiotic" PCN Ancef IV Contrast Peanuts Concern Concern tracking isn't always problems. Allergy lists -- maybe?? Visit time

More Related