Let's be careful when trusting to memory when it comes to what we discussed or
agreed to at
HackathonOne<https://informatics.gpcnetwork.org/trac/Project/wiki/HackathonOne>.
Records clearly show that what we discussed in the Quality Assurance scripting
for i2b2
ETLs<https://docs.google.com/document/d/135oMEgKQYOI-2LdVI9VQMuT-_XAu6mh75QQsC-yikas/edit#heading=h.m90tj0fznhzw>
session was not "secondary":
* ENCOUNTER DX
* PRIMARY DX
* NONPRIMARY DX
* BILLING DX
* DISCHARGE PRINCIPAL 52534-5 8319008|Principal diagnosis(qualifier)|
* DISCHARGE NONPRINCIPAL
* PROFESSIONAL DX PRIMARY
* PROFESSIONAL DX NONPRIMARY
That proposal also got sent to gpc-dev March 04, 2014 1:17 PM and minutes 18
Mar<http://listserv.kumc.edu/pipermail/gpc-dev/2014q1/000012.html> show we
RESOLVED to adopt it.
But then we didn't, actually, adopt it. So here we are, discussing what to
adopt.
--
Dan
________________________________________
From: Campbell, James R [[email protected]]
Sent: Tuesday, November 18, 2014 8:07 AM
To: Apathy,Nate; <[email protected]>
Cc: Dan Connolly; [email protected]
Subject: RE: [gpc-informatics] #90: Diagnoses Modifiers for data attribution
I agree that 'secondary' is potentially misleading and only ask for affirmation
from the GPC ETL managers since that was the modifier term we affirmed at
hackathon I
Jim
________________________________________
From: Apathy,Nate [[email protected]]
Sent: Tuesday, November 18, 2014 7:40 AM
To: Campbell, James R; <[email protected]>
Cc: [email protected]; [email protected]
Subject: Re: [gpc-informatics] #90: Diagnoses Modifiers for data attribution
That sounds like a reasonable convergence of cancelled/deleted terms to
me. Laurel, those terms work for Marshfield as well, correct?
My only adjustment would be on your second point to simplify it to
³non-primary² since it seems that the ³secondary² term is not truly
reflective of an ordinal relationship in any of our source systems. It
could confuse users if we have both secondary and non-primary in the term.
Thanks,
Nate Apathy
Program Manager, Cerner Research
-----Original Message-----
From: <Campbell>, "[email protected]" <[email protected]>
Date: Tuesday, November 18, 2014 at 8:28 AM
To: "[email protected]" <[email protected]>
Cc: Nate Apathy <[email protected]>, Dan Connolly
<[email protected]>, Laurel Verhagen <[email protected]>
Subject: Re: [gpc-informatics] #90: Diagnoses Modifiers for data
attribution
So, if I am hearing you correctly Nate, we will change 'Deleted' to
''Deleted/Cancelled' and use across Cerner and Epic and change 'Secondaty'
to 'Secondary/Nonprimary' for convergence since in Epic we are using
Secondary to annotate diagnoses 2-N and it does not mean 'second'
JIM
James R. Campbell MD
[email protected]
Office: 402-559-7505
Secretary: 402-559-7299
Pager: 402-888-1230
> On Nov 17, 2014, at 2:33 PM, "GPC Informatics" <[email protected]> wrote:
>
> #90: Diagnoses Modifiers for data attribution
> --------------------------+----------------------------
> Reporter: campbell | Owner: nateapathy
> Type: design-issue | Status: assigned
> Priority: major | Milestone: data-domains2
> Component: data-stds | Resolution:EC
> Keywords: | Blocked By:
> Blocking: 70, 91, 120 |
> --------------------------+----------------------------
>
> Comment (by nateapathy):
>
> That's correct - in the Cerner Millennium Problem List the valid statuses
> are Active, Cancelled, and Resolved, and Cancelled would be used for the
> use case you are describing re: "Deleted" from Epic.
>
> We keep the Problems List and Diagnoses List separate (you can turn
> problems into diagnoses in the chart, of course, but on the database side
> there are distinct and separate tables (PROBLEM and DIAGNOSIS). For
> modifiers on diagnosis codes, we only specify between primary and non-
> primary, as Laurel described earlier in this thread, so I wouldn't vote
> for Secondary as the modifier of choice. We are using "Primary" and "non-
> Primary" in our current i2b2 projects. It's not reflected in Babel yet
> because we haven't finished the deployment but I'll have an updated
> diagnosis ontology in December.
>
> --
> Ticket URL:
><http://informatics.gpcnetwork.org/trac/Project/ticket/90#comment:16>
> gpc-informatics <http://informatics.gpcnetwork.org/>
> Greater Plains Network - Informatics
The information in this e-mail may be privileged and confidential,
intended only for the use of the addressee(s) above. Any unauthorized use
or disclosure of this information is prohibited. If you have received this
e-mail by mistake, please delete it and immediately contact the sender.
CONFIDENTIALITY NOTICE This message and any included attachments are from
Cerner Corporation and are intended only for the addressee. The information
contained in this message is confidential and may constitute inside or
non-public information under international, federal, or state securities laws.
Unauthorized forwarding, printing, copying, distribution, or use of such
information is strictly prohibited and may be unlawful. If you are not the
addressee, please promptly delete this message and notify the sender of the
delivery error by e-mail or you may call Cerner's corporate offices in Kansas
City, Missouri, U.S.A at (+1) (816)221-1024.
The information in this e-mail may be privileged and confidential, intended
only for the use of the addressee(s) above. Any unauthorized use or disclosure
of this information is prohibited. If you have received this e-mail by mistake,
please delete it and immediately contact the sender.
_______________________________________________
Gpc-dev mailing list
[email protected]
http://listserv.kumc.edu/mailman/listinfo/gpc-dev
