Database structure - Revision history

HubertCzobodzinski: Extended data set.

2012-11-13T20:38:17Z

Extended data set.

HubertCzobodzinski: Structure changed.

2012-11-13T14:44:59Z

Structure changed.

HubertCzobodzinski: Structure changed.

2012-11-13T14:44:35Z

Structure changed.

HubertCzobodzinski: Stucture changed.

2012-11-13T14:43:56Z

Stucture changed.

HubertCzobodzinski: Structure changed.

2012-11-13T14:42:43Z

Structure changed.

HubertCzobodzinski: Operation details updated.

2012-11-13T14:38:25Z

Operation details updated.

HubertCzobodzinski: Patient and admission properties updated.

2012-11-13T14:19:53Z

Patient and admission properties updated.

MaciejBlizinski: +Burton

2006-02-13T10:38:36Z

+Burton

MaciejBlizinski: +terminology

2006-01-11T11:26:50Z

+terminology

MaciejBlizinski at 07:38, 30 September 2005

2005-09-30T07:38:23Z

@@ Line 62: / Line 62: @@
 * Prior operations information
 * Comment (free text)
 === Procedures ===

@@ Line 79: / Line 79: @@
 AAEs behave in similar way to procedures. One operation can have many AAEs.
-=== Data entry order ===
+== Data entry order ==
 The data entry order is determined by its structure. You cannot enter operation without first entering the patient. As the patient is entered, you can proceed and enter the admission. When the admission is entered, you may enter operations performed during this admission.
 [[category:terminology]]

@@ Line 45: / Line 45: @@
 * Readmission reason (if applicable)
-=== Operations ===
+== Operations ==
 Admissions have operations. One admission can have many operations. One operation is assigned to one, and only one admission. Operation's properties are:

@@ Line 7: / Line 7: @@
 [[Image:Patients-and-braces.png|thumb|right|The data structure in Burton-like representation]]
-=== Patients ===
+== Patients ==
 The main object in the database is the Patient. Every other objects, like admission or operation, are always entered in the context of the specific patient and cannot exist without him/her. Therefore, the procedure of data entry always starts with entering the patient into the database. Patient's properties are:
@@ Line 22: / Line 22: @@
 * Date of death (if applicable)
-== Diagnoses ==
+=== Diagnoses ===
 Diagnoses are related to the patient and always entered in the context of the specific patient. For example, if you see “John Doe” on the top of the program window, it means that you can see and enter John Doe's diagnoses (and nobody's else). When you want to enter other patient's diagnoses, you have to pick him/her from the list on the left. When you do so, the label on the top changes to the new name.
@@ Line 28: / Line 28: @@
 One patient can have many diagnoses. Diagnoses are ordered, more important diagnoses are on top, least important are on the bottom of the diagnoses list. The first diagnosis is the patient's FundamentalDiagnosis.
-== Non Cardiac Abnormalities ==
+=== Non Cardiac Abnormalities ===
 NCA behave in similar way to the diagnoses. One patient can have many NCA.
-== Statuses Post ==
+=== Statuses Post ===
 Statuses Post behave in similar way to the diagnoses. One patient can have many Statuses Post.
-=== Admissions ===
+== Admissions ==
 Patients have admissions (sojourns). One patient can have many admissions. One admission is assigned to one, and only one patient. Admission's properties are:

@@ Line 22: / Line 22: @@
 * Date of death (if applicable)
-=== Diagnoses ===
+== Diagnoses ==
 Diagnoses are related to the patient and always entered in the context of the specific patient. For example, if you see “John Doe” on the top of the program window, it means that you can see and enter John Doe's diagnoses (and nobody's else). When you want to enter other patient's diagnoses, you have to pick him/her from the list on the left. When you do so, the label on the top changes to the new name.
@@ Line 28: / Line 28: @@
 One patient can have many diagnoses. Diagnoses are ordered, more important diagnoses are on top, least important are on the bottom of the diagnoses list. The first diagnosis is the patient's FundamentalDiagnosis.
-=== Non Cardiac Abnormalities ===
+== Non Cardiac Abnormalities ==
 NCA behave in similar way to the diagnoses. One patient can have many NCA.
-=== Statuses Post ===
+== Statuses Post ==
 Statuses Post behave in similar way to the diagnoses. One patient can have many Statuses Post.

@@ Line 30: / Line 30: @@
 === Non Cardiac Abnormalities ===
-NCA behave in similar way to the diagnoses. One patient can have many NCA, but they are not ordered.
+NCA behave in similar way to the diagnoses. One patient can have many NCA.
 === Statuses Post ===
-Statuses Post behave in similar way to the diagnoses. One patient can have many Statuses Post, but they are not ordered.
+Statuses Post behave in similar way to the diagnoses. One patient can have many Statuses Post.
 === Admissions ===
@@ Line 43: / Line 43: @@
 * Date of discharge
 * Discharge location
-* Readmission Reason (if applicable)
+* Readmission reason (if applicable)
 === Operations ===
@@ Line 49: / Line 49: @@
 Admissions have operations. One admission can have many operations. One operation is assigned to one, and only one admission. Operation's properties are:
 * Date of surgery
-* ICU discharge
+* ICU discharge date
 * Surgeon
 * Patient's weight at the time of surgery
 * Patient's height at the time of surgery
-* Case Category
+* Status at 30 days
 * CPB Time (if applicable)
 * AOX Time (if applicable)
 * Circulatory Arrest Time (if applicable)
 * Comment (free text)
@@ Line 66: / Line 66: @@
 Operation can “have” many procedures. Procedures are ordered, from most important (on the top) to least important (on the bottom). The procedure on the top is called the PrimaryProcedure. One operation must have at least one procedure.
 === General Preoperative Risk Factors ===
 GPRFs behave in similar way to procedures. One operation can have many GPRFs.
 === Data entry order ===

@@ Line 15: / Line 15: @@
 * Gender
 * Date of birth
-* Antenatal Diagnosis
+* Antenatal diagnosis
 * Date of death (if applicable)
@@ Line 26: / Line 30: @@
 === Non Cardiac Abnormalities ===
-NCA behave in similar way to the diagnoses. One patient can have many NCA and they are ordered.
+NCA behave in similar way to the diagnoses. One patient can have many NCA, but they are not ordered.
 === Admissions ===
@@ Line 34: / Line 42: @@
 * Date of admission
 * Date of discharge
 === Operations ===

←Older revision		Revision as of 10:38, 13 February 2006
Line 4:		Line 4:

	[[Image:DataStructure.png\|thumb\|right\|The database structure diagram, by example]]		[[Image:DataStructure.png\|thumb\|right\|The database structure diagram, by example]]
		+
		+	[[Image:Patients-and-braces.png\|thumb\|right\|The data structure in Burton-like representation]]

	=== Patients ===		=== Patients ===

←Older revision		Revision as of 11:26, 11 January 2006
Line 62:		Line 62:

	The data entry order is determined by its structure. You cannot enter operation without first entering the patient. As the patient is entered, you can proceed and enter the admission. When the admission is entered, you may enter operations performed during this admission.		The data entry order is determined by its structure. You cannot enter operation without first entering the patient. As the patient is entered, you can proceed and enter the admission. When the admission is entered, you may enter operations performed during this admission.
		+
		+	[[category:terminology]]

@@ Line 3: / Line 3: @@
 Data entry is the main purpose of ECDBC. The user's interface is designed in such a way, that it reflects the logical structure of entered data, which is described in following sections of the manual.
-[[Image:DataStructure.png]]
+[[Image:DataStructure.png|thumb|right|The database structure diagram, by example]]
 === Patients ===