Data flow - Revision history

MaciejBlizinski: /* The validation rules */

2005-09-28T17:59:02Z

‎The validation rules

MaciejBlizinski: /* Data validation */

2005-09-28T17:58:28Z

‎Data validation

MaciejBlizinski at 17:58, 28 September 2005

2005-09-28T17:58:12Z

MaciejBlizinski: /* Data Validation Procedure */

2005-09-28T17:50:15Z

‎Data Validation Procedure

MaciejBlizinski: /* Data Validation Procedure */ Link

2005-09-28T17:47:43Z

‎Data Validation Procedure: Link

MaciejBlizinski: /* Data Validation Procedure */

2005-09-28T17:46:31Z

‎Data Validation Procedure

MaciejBlizinski at 22:16, 23 September 2005

2005-09-23T22:16:12Z

MaciejBlizinski: /* The validation rules */

2005-09-23T21:34:18Z

‎The validation rules

MaciejBlizinski at 21:33, 23 September 2005

2005-09-23T21:33:50Z

MaciejBlizinski at 21:32, 23 September 2005

2005-09-23T21:32:22Z

@@ Line 32: / Line 32: @@
 =The validation rules=
-See also: [[Data validation]].
+''See the article: [[Validation rules]].''
 [[category:terminology]]

@@ Line 22: / Line 22: @@
 Web Client Interface, also referred as the Data Entry Form is intended to be substitute to the client application. It is written in  [http://www.python.org Python programming language] and allows users to enter the data directly into the main database, without need of exporting. However, the data is not visible in the reports immediately, because it must first pass [[data validation]] procedure.
-=[[Data validation]]=
+=Data validation=
 ''See the article: [[data validation]].''

@@ Line 3: / Line 3: @@
 = The Data Flow until the end of 2004 =
-There were two basic ways of submitting data to the database.
+[[Image:DataFlow.png|500px]]
-== echdd6.exe ==
+''The data-flow graph.'' -- This graph shows the data flow, concentrating on the data validation procedure.
 This is the piece of software used to collect and submit data. echdd6 is written in C++, and is available to download in binary form from ECDB's website. This application is avaliable only for Windows platform, and it's intended to be installed locally in the
@@ Line 12: / Line 16: @@
 The echdd6 application makes use of the Windows database libraries and stores its data in MDB file, which can be read with Access97 application. Hence the need for database libraries.
-This application allows users to enter the data and export it. Exporting means sending the data to the data manager, who imports the it into main database. Not all of the data is exported. The patients' names for instance, remain in the local PC.
+This application allows users to enter the data and export it. Exporting means sending the data to the data manager, who imports the it into main database. Not all of the data is exported. The patients' names for instance, remain in the local PC and they are not transfered to the [[central database]].
-== Web interface ==
+==Web interface==
-Web Client Interface, also referred as the Data Entry Form is intended to be substitute to the client application. It is written in  [http://www.python.org Python] language and allows users to enter the data directly into the main database, without need of exporting. However, the data is not visible in the reports immediately, because it must first pass validation procedure.
+Web Client Interface, also referred as the Data Entry Form is intended to be substitute to the client application. It is written in  [http://www.python.org Python programming language] and allows users to enter the data directly into the main database, without need of exporting. However, the data is not visible in the reports immediately, because it must first pass [[data validation]] procedure.
-= Data Validation Procedure =
+=[[Data validation]]=
 ''See the article: [[data validation]].''
 =Data entry from year 2005=
-From year 2005 data is gathered with [[EACTS Database Software]] version 7.0.
+From year 2005 data is gathered with [[EACTS Database Software]] version 7.0 only.
-The Validation Rules file is in XML format for flexibility and easy editing. You can read the rules here:
+=The validation rules=
 See also: [[Data validation]].
 [[category:terminology]]

@@ Line 20: / Line 20: @@
 = Data Validation Procedure =
-The DataValidation Procedure was designed to improve the quality of data by finding inconsistencies in the data. For example, the patient's birth date can't be later than the date of the operation. There is a number of validation rules that the record has to meet in order to be published. Some of the data may  be labeled "incorrect" by the computer by may in fact be correct which the ownewrs of the data can confirm, for example unusuall age and weight combinations. In such case, the hospital can mark the record as correct, despite not meeting the validation rule (see [[validation rules]]). The last word belongs to the data manager. He is the one to finally accept or reject the record.
+''See the article: [[data validation]].''
 [[Image:DataFlow.png|500px]]

@@ Line 20: / Line 20: @@
 = Data Validation Procedure =
-The DataValidation Procedure was designed to improve the quality of data by finding inconsistencies in the data. For example, the patient's birth date can't be later than the date of the operation. There is a number of validation rules that the record has to meet in order to be published. Some of the data may  be labeled "incorrect" by the computer by may in fact be correct which the ownewrs of the data can confirm, for example unusuall age and weight combinations. In such case, the hospital can mark the record as correct, despite not meeting the validation rule (see ValidationRules). The last word belongs to the data manager. He is the one to finally accept or reject the record.
+The DataValidation Procedure was designed to improve the quality of data by finding inconsistencies in the data. For example, the patient's birth date can't be later than the date of the operation. There is a number of validation rules that the record has to meet in order to be published. Some of the data may  be labeled "incorrect" by the computer by may in fact be correct which the ownewrs of the data can confirm, for example unusuall age and weight combinations. In such case, the hospital can mark the record as correct, despite not meeting the validation rule (see [[validation rules]]). The last word belongs to the data manager. He is the one to finally accept or reject the record.
 Please note that data validation does not ensure that the data reflects the reality of the facts. It only prevents the data from containing obvious inconsistencies. Another method of improving the quality of data is called the DataVerification.

←Older revision		Revision as of 22:16, 23 September 2005
Line 1:		Line 1:
		+	{{terminology-infobox}}
		+
	= The Data Flow until the end of 2004 =		= The Data Flow until the end of 2004 =

←Older revision		Revision as of 21:33, 23 September 2005
Line 25:		Line 25:

	''The data-flow graph.'' -- This graph shows the data flow, concentrating on the data validation procedure.		''The data-flow graph.'' -- This graph shows the data flow, concentrating on the data validation procedure.
		+
		+	=Data entry from year 2005=
		+
		+	From year 2005 data is gathered with [[EACTS Database Software]] version 7.0.

	= The validation rules =		= The validation rules =

←Older revision		Revision as of 21:32, 23 September 2005
Line 32:		Line 32:
	The Validation Rules file is in XML format for flexibility and easy editing. You can read the rules here:		The Validation Rules file is in XML format for flexibility and easy editing. You can read the rules here:
	[http://www.eactscongenitaldb.org/db/ValidationRules.xml ValidationRules.xml]. The validation mechanism was re-written from old CSV-like config file in August 2004.		[http://www.eactscongenitaldb.org/db/ValidationRules.xml ValidationRules.xml]. The validation mechanism was re-written from old CSV-like config file in August 2004.
		+
		+	[[category:terminology]]