Frequently asked questions - Revision history

JoC: Removed redirect to FAQ

2021-03-22T10:03:19Z

Removed redirect to FAQ

← Older revision		Revision as of 10:03, 22 March 2021
Line 1:		Line 1:
	~~#REDIRECT [[FAQ]]~~

	=== How does the DDS deal with left and dead patients? ===		=== How does the DDS deal with left and dead patients? ===
	Left and dead patients are retained in the database; information in those records may be needed for retrospective analytics such as trends.		Left and dead patients are retained in the database; information in those records may be needed for retrospective analytics such as trends.

JoC: Redirected page to FAQ

2021-03-22T10:01:14Z

Redirected page to FAQ

← Older revision		Revision as of 10:01, 22 March 2021
Line 1:		Line 1:
			#REDIRECT [[FAQ]]

	=== How does the DDS deal with left and dead patients? ===		=== How does the DDS deal with left and dead patients? ===
	Left and dead patients are retained in the database; information in those records may be needed for retrospective analytics such as trends.		Left and dead patients are retained in the database; information in those records may be needed for retrospective analytics such as trends.

JoC at 11:55, 4 September 2020

2020-09-04T11:55:46Z

← Older revision		Revision as of 11:55, 4 September 2020
Line 7:		Line 7:
	This may be due to a particular field not being the safest option; for example, practice codes instead of names and GP registration codes instead of GP names.		This may be due to a particular field not being the safest option; for example, practice codes instead of names and GP registration codes instead of GP names.

	{{info\|[[Discovery_Remote_Subscriber_Database_Familiarisation#Data_Mapping\|Mapping documents are available for each source system.}}		{{info\|[[Discovery_Remote_Subscriber_Database_Familiarisation#Data_Mapping\|Mapping documents]] are available for each source system.}}

			[[Discovery_Remote_Subscriber_Database_Familiarisation#Data_Mapping\|Mapping documents are available for each source system.]]

	Where a field is missing from the DDS please discuss with us as we may have access to the data but are yet to be asked to transform it.		Where a field is missing from the DDS please discuss with us as we may have access to the data but are yet to be asked to transform it.

JoC: /* Why are some fields not transformed in DDS? */

2020-09-04T11:50:13Z

Why are some fields not transformed in DDS?

← Older revision		Revision as of 11:50, 4 September 2020
Line 7:		Line 7:
	This may be due to a particular field not being the safest option; for example, practice codes instead of names and GP registration codes instead of GP names.		This may be due to a particular field not being the safest option; for example, practice codes instead of names and GP registration codes instead of GP names.

	{{info\|Mapping documents are available for each source system.}}		{{info\|[[Discovery_Remote_Subscriber_Database_Familiarisation#Data_Mapping\|Mapping documents are available for each source system.}}

	Where a field is missing from the DDS please discuss with us as we may have access to the data but are yet to be asked to transform it.		Where a field is missing from the DDS please discuss with us as we may have access to the data but are yet to be asked to transform it.

JoC: /* Why are some fields not transformed in DDS? */

2020-09-04T11:48:40Z

Why are some fields not transformed in DDS?

← Older revision		Revision as of 11:48, 4 September 2020
Line 7:		Line 7:
	This may be due to a particular field not being the safest option; for example, practice codes instead of names and GP registration codes instead of GP names.		This may be due to a particular field not being the safest option; for example, practice codes instead of names and GP registration codes instead of GP names.

	{{~~[[Discovery Remote Subscriber Database Familiarisation~~\|Mapping documents~~]]}}~~ are available for each source system.		{{info\|Mapping documents are available for each source system.}}

	Where a field is missing from the DDS please discuss with us as we may have access to the data but are yet to be asked to transform it.		Where a field is missing from the DDS please discuss with us as we may have access to the data but are yet to be asked to transform it.

JoC at 11:47, 4 September 2020

2020-09-04T11:47:49Z

← Older revision		Revision as of 11:47, 4 September 2020
Line 4:		Line 4:
	Inner NEL have applied to EMIS for left and dead patients for the past 10 years; EMIS have quoted for all 3 STPs but an order has not yet been placed.		Inner NEL have applied to EMIS for left and dead patients for the past 10 years; EMIS have quoted for all 3 STPs but an order has not yet been placed.

	=== ~~Fields that~~ are not transformed ~~into the~~ DDS? ===		=== Why are some fields not transformed in DDS? ===
	This may be due to ~~the~~ field not being the safest option, ~~e.g. we pick up~~ practice codes ~~rather than~~ names and GP registration ~~code rather than the~~ GP names.		This may be due to a particular field not being the safest option; for example, practice codes instead of names and GP registration codes instead of GP names.
	Mapping documents are available for each source system.
			{{[[Discovery Remote Subscriber Database Familiarisation\|Mapping documents]]}} are available for each source system.

	Where a field is missing from the DDS please discuss with us as we may have access to the data but are yet to be asked to transform it.		Where a field is missing from the DDS please discuss with us as we may have access to the data but are yet to be asked to transform it.

JoC at 15:59, 3 September 2020

2020-09-03T15:59:23Z

← Older revision		Revision as of 15:59, 3 September 2020
Line 1:		Line 1:
	=== How does the DDS deal with left and dead patients? ===		=== How does the DDS deal with left and dead patients? ===
	~~We retain left~~ and dead patients in the database ~~as the~~ information in those records may be needed for retrospective analytics ~~e.g.~~ trends.		Left and dead patients are retained in the database; information in those records may be needed for retrospective analytics such as trends.
	Inner NEL have applied to EMIS for left and dead patients for the past 10 years.
	EMIS have quoted for all 3 STPs but an order has not yet been placed.		Inner NEL have applied to EMIS for left and dead patients for the past 10 years; EMIS have quoted for all 3 STPs but an order has not yet been placed.

	=== Fields that are not transformed into the DDS? ===		=== Fields that are not transformed into the DDS? ===
Line 16:		Line 16:

	Answered in Jira - https://endeavourhealth.atlassian.net/secure/RapidBoard.jspa?rapidView=80&projectKey=HIPRP&modal=detail&selectedIssue=HIPRP-29		Answered in Jira - https://endeavourhealth.atlassian.net/secure/RapidBoard.jspa?rapidView=80&projectKey=HIPRP&modal=detail&selectedIssue=HIPRP-29
	~~<br />~~
			=== Records with missing NHS numbers, are they kept in DDS, are they reported to the publisher or subscriber? ===
			Yes, records do exist without NHS numbers within DDS, we do not currently report back to publishers on this. On a project by project basis we can set the subscriber cohort to either send these to a remote subscriber database or hold them back. If an NHS number is added to that record, it would be updated within DDS and the whole patient record would pass to the subscriber as a delta update.

JoC at 15:02, 3 September 2020

2020-09-03T15:02:04Z

← Older revision		Revision as of 15:02, 3 September 2020
Line 1:		Line 1:
			=== How does the DDS deal with left and dead patients? ===
	How does the DDS deal with left and dead patients?


	We retain left and dead patients in the database as the information in those records may be needed for retrospective analytics e.g. trends.		We retain left and dead patients in the database as the information in those records may be needed for retrospective analytics e.g. trends.
	Inner NEL have applied to EMIS for left and dead patients for the past 10 years.		Inner NEL have applied to EMIS for left and dead patients for the past 10 years.
	EMIS have quoted for all 3 STPs but an order has not yet been placed.		EMIS have quoted for all 3 STPs but an order has not yet been placed.

			=== Fields that are not transformed into the DDS? ===
	Fields that are not transformed into the DDS?

	This may be due to the field not being the safest option, e.g. we pick up practice codes rather than names and GP registration code rather than the GP names.		This may be due to the field not being the safest option, e.g. we pick up practice codes rather than names and GP registration code rather than the GP names.
	Mapping documents are available for each source system.		Mapping documents are available for each source system.
	Where a field is missing from the DDS please discuss with us as we may have access to the data but are yet to be asked to transform it.		Where a field is missing from the DDS please discuss with us as we may have access to the data but are yet to be asked to transform it.

			=== Is the 10 MB/sec HSCN network connection shared between STPs or just NWL? Does that create a data bottleneck? ===
			Currently the HSCN link is 10MB/Sec as that is all that is required, it is shared across all STP clients. This can be scaled as required in increments of 1MB/Sec up to 1GB/Sec, This costs £70 per 1MB/Sec per month +VAT & can be scaled with about 2 weeks notice, current load is peaking at ~60% of capacity for brief periods. Peak usage is normally TPP bulks being sent to us, Emis bulks would also be similar in profile, these are very short peaks (less than 5 minutes).

			=== HL7 matching - How does DDS match ORUs/ADTs to existing patient data and what will happen to the ORU/ADT if no patient is found or there are multiple matches? ===
			We don't match, every source organisation has its own instance of a patient.

			Answered in Jira - https://endeavourhealth.atlassian.net/secure/RapidBoard.jspa?rapidView=80&projectKey=HIPRP&modal=detail&selectedIssue=HIPRP-29
			<br />

JoC: Created page with " How does the DDS deal with left and dead patients? We retain left and dead patients in the database as the information in those records may be needed for retrospective anal..."

2020-09-03T14:56:24Z

Created page with " How does the DDS deal with left and dead patients? We retain left and dead patients in the database as the information in those records may be needed for retrospective anal..."

New page

How does the DDS deal with left and dead patients?

We retain left and dead patients in the database as the information in those records may be needed for retrospective analytics e.g. trends.
Inner NEL have applied to EMIS for left and dead patients for the past 10 years.
EMIS have quoted for all 3 STPs but an order has not yet been placed.

Fields that are not transformed into the DDS?

This may be due to the field not being the safest option, e.g. we pick up practice codes rather than names and GP registration code rather than the GP names.
Mapping documents are available for each source system.
Where a field is missing from the DDS please discuss with us as we may have access to the data but are yet to be asked to transform it.