L Dxs table: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
Line 8: Line 8:


==Contents of L_Dxs==
==Contents of L_Dxs==
L_Dxs is populated with diagnoses from the [[s_Alldiagnoses]] table. The diagnoses are sttructured in a system of  main- and sub-diagnoses. Which diagnoses end up on the list is determined by the [[steering committee]].
L_Dxs is populated with diagnoses from the [[s_Alldiagnoses]] table. The diagnoses are sttructured in a system of  main- and sub-diagnoses. Which diagnoses end up on the list is determined by the [[:Category:Steering Committee|steering committee]].


Because our main repository [[TMSX]] is not relational, it is limited to 6 admit diagnoses and 9 complications per patient. L_DXs contains a field "priority" which is for ranking of the comorbids to decide which will be sent.
Because our main repository [[TMSX]] is not relational, it is limited to 6 admit diagnoses and 9 complications per patient. L_DXs contains a field "priority" which is for ranking of the comorbids to decide which will be sent.
Line 60: Line 60:
|rhdrid_  ||  required for HanDBase sync
|rhdrid_  ||  required for HanDBase sync
|}
|}


==Still needs to be done...==
==Still needs to be done...==

Revision as of 22:37, 2008 May 26

L_Dxs is the data structure where patients' diagnoses are stored.

Instances of L_Dxs

There are several instances of L_Dxs

  • a HanDBase file on each PDA
    • containing a HanDBase table
  • a table in each copy of the CCMDB.mdb

Contents of L_Dxs

L_Dxs is populated with diagnoses from the s_Alldiagnoses table. The diagnoses are sttructured in a system of main- and sub-diagnoses. Which diagnoses end up on the list is determined by the steering committee.

Because our main repository TMSX is not relational, it is limited to 6 admit diagnoses and 9 complications per patient. L_DXs contains a field "priority" which is for ranking of the comorbids to decide which will be sent.

Due to limitations to our technology, we also track Tasks among our diagnoses because the data structure was set up to accept them.


L_Dxs HanDBase File and Table

L_Dxs on HanDBase contains the fields

Pat_ID Unique patient identifier
??? to designate whether this is a

diagnosis, complication or task

???Main as chosen from s_AllDiagnoses
???Sub as chosen from s_AllDiagnoses
???Code as chosen from s_AllDiagnoses
Linked used by HanDBase to relate tables
Priority to sort to limit to 6 diagnoses, resp 9 complications


L_Como Table in the CCMDB.mdb

L_Como in the CCMDB.mdb Access program contains the fields

Dx_ID unique id for relationships and indexes
Pat_ID unique patient identifier
??? to designate whether this is a

diagnosis, complication or task |-

??? DxCode as chosen from s_AllDiagnoses

main- and sub diagnoses get pulled for display from s_Alldiagnoses

???Priority used to sort to limit to 6 diagnoses resp. 9 complications
rank used to rank to limit to 6 diagnoses resp. 9 complications
rhdrinfo_ required for HanDBase sync
rhdrid_ required for HanDBase sync

Still needs to be done...

  • confirm field names


Template:Stub