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.

_______________________________________________
Gpc-dev mailing list
[email protected]
http://listserv.kumc.edu/mailman/listinfo/gpc-dev

Reply via email to