Inbound Data Transform Specifications - Revision history

JoC at 11:29, 4 May 2021

2021-05-04T11:29:23Z

JoC at 10:29, 4 May 2021

2021-05-04T10:29:51Z

JoC at 13:41, 29 April 2021

2021-04-29T13:41:06Z

← Older revision		Revision as of 13:41, 29 April 2021
Line 7,733:		Line 7,733:
	\|TODO: Is any mapping or formatting required?		\|TODO: Is any mapping or formatting required?
	\|}		\|}

			=== Observation ===

			=== Procedure ===

			=== Questionnaire Response ===

			=== Specimen ===

			=== Schedule ===

			=== Slot ===

			=== Appointment ===

JoC at 13:39, 29 April 2021

2021-04-29T13:39:08Z

← Older revision		Revision as of 13:39, 29 April 2021
Line 25:		Line 25:

	== DDS inbound overview ==		== DDS inbound overview ==
	[[File:Inbound view.png\|640x640px\|alt=\|DDS inbound overview\|thumb]]		[[File:Inbound view.png\|640x640px\|alt=\|DDS inbound overview\|thumb\|none]]
	This diagram provides an overview of the way the DDS processes a sample of existing inbound data feeds. Each data publisher has their own transport mechanism for getting data into the DDS estate (SFTP push, SFTP pull, bespoke software) which is then sent through a common pipeline that performs a number of checks (most importantly validating that DDS has a data processing agreement to accept the data). Once the checks are passed, the data is handed over to the DDS transformation application, that then invokes the relevant transform code for the published data format. The result of the transformation code is standardised FHIR that is saved to the DDS database; this may be further transformed for any subscribers to that publisher’s data.		This diagram provides an overview of the way the DDS processes a sample of existing inbound data feeds. Each data publisher has their own transport mechanism for getting data into the DDS estate (SFTP push, SFTP pull, bespoke software) which is then sent through a common pipeline that performs a number of checks (most importantly validating that DDS has a data processing agreement to accept the data). Once the checks are passed, the data is handed over to the DDS transformation application, that then invokes the relevant transform code for the published data format. The result of the transformation code is standardised FHIR that is saved to the DDS database; this may be further transformed for any subscribers to that publisher’s data.

JoC at 13:37, 29 April 2021

2021-04-29T13:37:28Z

Show changes

JoC at 13:32, 29 April 2021

2021-04-29T13:32:03Z

← Older revision		Revision as of 13:32, 29 April 2021
Line 7,306:		Line 7,306:
	\|}		\|}

	=== ~~'''~~Resource: Medication Dispense~~'''~~ ===		=== Resource: Medication Dispense ===
	Represents the dispensing of medication, links to a Medication Statement. See <nowiki>http://hl7.org/fhir/medicationdispense.html</nowiki>		Represents the dispensing of medication, links to a Medication Statement. See <nowiki>http://hl7.org/fhir/medicationdispense.html</nowiki>

JoC at 13:28, 29 April 2021

2021-04-29T13:28:39Z

← Older revision		Revision as of 13:28, 29 April 2021
Line 7,199:		Line 7,199:
	'''Authorisation type'''		'''Authorisation type'''
	{\| class="wikitable"		{\| class="wikitable"
	\|Field name:		!Field name:
	\|Authorisation type		\|Authorisation type
	\|-		\|-
	\|Type:		!Type:
	\|Value set		\|Value set
	\|-		\|-
	\|Cardinality:		!Cardinality:
	\|1..1		\|1..1
	\|-		\|-
	\|Required:		!Required:
	\|Yes		\|Yes
	\|-		\|-
	\|Description:		!Description:
	\|Type of prescription ~~e.g.~~ acute, repeat. See ~~<nowiki>~~https://github.com/endeavourhealth/Fhir/blob/master/src/main/java/org/endeavourhealth/common/fhir/schema/MedicationAuthorisationType.java~~</nowiki>~~		\|Type of prescription (such as acute, repeat).
			See https://github.com/endeavourhealth/Fhir/blob/master/src/main/java/org/endeavourhealth/common/fhir/schema/MedicationAuthorisationType.java
	\|-		\|-
	\|Source location:		!Source location:
	\|~~TODO:~~ What file and field contains this?		\|What file and field contains this?
	\|-		\|-
	\|Mapping:		!Mapping:
	\|~~TODO:~~ Is any mapping or formatting required?		\|Is any mapping or formatting required?
	\|}		\|}
	Confidential		'''Confidential'''
	{\| class="wikitable"		{\| class="wikitable"
	\|Field name:		!Field name:
	\|Confidential		\|Confidential
	\|-		\|-
	\|Type:		!Type:
	\|Boolean		\|Boolean
	\|-		\|-
	\|Cardinality:		!Cardinality:
	\|0..1		\|0..1
	\|-		\|-
	\|Required:		!Required:
	\|No		\|No
	\|-		\|-
	\|Description:		!Description:
	\|Confidentiality flag		\|Confidentiality flag
	\|-		\|-
	\|Source location:		!Source location:
	\|~~TODO:~~ What file and field contains this?		\|What file and field contains this?
	\|-		\|-
	\|Mapping:		!Mapping:
	\|~~TODO:~~ Is any mapping or formatting required?		\|Is any mapping or formatting required?
	\|}		\|}
	Quantity		'''Quantity'''
	{\| class="wikitable"		{\| class="wikitable"
	\|Field name:		!Field name:
	\|Quantity		\|Quantity
	\|-		\|-
	\|Type:		!Type:
	\|Sub-element		\|Sub-element
	\|-		\|-
	\|Cardinality:		!Cardinality:
	\|1..1		\|1..1
	\|-		\|-
	\|Required:		!Required:
	\|Yes		\|Yes
	\|-		\|-
	\|Description:		!Description:
	\|Quantity of prescribed drug to be dispensed. For repeat medications, this is the quantity per issue.		\|Quantity of prescribed drug to be dispensed. For repeat medications, this is the quantity per issue.
	\|}		\|}
	{\| class="wikitable"		{\| class="wikitable"
	\|Field name:		!Field name:
	\|Value		\|Value
	\|-		\|-
	\|Type:		!Type:
	\|Number		\|Number
	\|-		\|-
	\|Cardinality:		!Cardinality:
	\|1..1		\|1..1
	\|-		\|-
	\|Required:		!Required:
	\|Yes		\|Yes
	\|-		\|-
	\|Description:		!Description:
	\|Numeric quantity component		\|Numeric quantity component
	\|-		\|-
	\|Source location:		!Source location:
	\|~~TODO:~~ What file and field contains this?		\|What file and field contains this?
	\|-		\|-
	\|Mapping:		!Mapping:
	\|~~TODO:~~ Is any mapping or formatting required?		\|Is any mapping or formatting required?
	\|}		\|}
	{\| class="wikitable"		{\| class="wikitable"
	\|Field name:		!Field name:
	\|Units		\|Units
	\|-		\|-
	\|Type:		!Type:
	\|Text		\|Text
	\|-		\|-
	\|Cardinality:		!Cardinality:
	\|0..1		\|0..1
	\|-		\|-
	\|Required:		!Required:
	\|Recommended		\|Recommended
	\|-		\|-
	\|Description:		!Description:
	\|Quantity units of measure ~~e.g.~~ tablets		\|Quantity units of measure (such as tablets)
	\|-		\|-
	\|Source location:		!Source location:
	\|~~TODO:~~ What file and field contains this?		\|What file and field contains this?
	\|-		\|-
	\|Mapping:		!Mapping:
	\|~~TODO:~~ Is any mapping or formatting required?		\|Is any mapping or formatting required?
	\|}		\|}

			=== '''Resource: Medication Dispense''' ===
			Represents the dispensing of medication, links to a Medication Statement. See <nowiki>http://hl7.org/fhir/medicationdispense.html</nowiki>

JoC at 13:22, 29 April 2021

2021-04-29T13:22:22Z

Show changes

JoC at 12:16, 29 April 2021

2021-04-29T12:16:02Z

← Older revision		Revision as of 12:16, 29 April 2021
Line 1:		Line 1:
	{{TOC ~~left~~}}		{{TOC right}}
	== Introduction ==		== Introduction ==
	This article forms the basis of the technical implementation of any new inbound transform of data into the Discovery Data Service (DDS), specifically for non-transactional flat file formats.		This article forms the basis of the technical implementation of any new inbound transform of data into the Discovery Data Service (DDS), specifically for non-transactional flat file formats.

JoC at 12:14, 29 April 2021

2021-04-29T12:14:31Z

← Older revision		Revision as of 12:14, 29 April 2021
Line 1:		Line 1:
	~~__TOC__~~		{{TOC left}}
	== Introduction ==		== Introduction ==
	This article forms the basis of the technical implementation of any new inbound transform of data into the Discovery Data Service (DDS), specifically for non-transactional flat file formats.		This article forms the basis of the technical implementation of any new inbound transform of data into the Discovery Data Service (DDS), specifically for non-transactional flat file formats.