Publishers and mapping to the common model - Revision history

AdminJo at 10:28, 5 February 2026

2026-02-05T10:28:47Z

← Older revision		Revision as of 10:28, 5 February 2026
Line 45:		Line 45:
	=== EMIS ===		=== EMIS ===
	''Main article:'' [[EMIS GP published data transformation and mapping]]		''Main article:'' [[EMIS GP published data transformation and mapping]]
			===NEMS===
			''Main article:'' [[NEMS Extract FHIR Mapping]]
	=== TPP ===		=== TPP ===
	''Main article:'' [[TPP Extract FHIR Mapping]]		''Main article:'' [[TPP Extract FHIR Mapping]]

AdminJo at 14:07, 18 November 2025

2025-11-18T14:07:16Z

← Older revision		Revision as of 14:07, 18 November 2025
Line 48:		Line 48:
	=== TPP ===		=== TPP ===
	''Main article:'' [[TPP Extract FHIR Mapping]]		''Main article:'' [[TPP Extract FHIR Mapping]]


	== Historic data feeds ==		== Historic data feeds ==

AdminJo at 14:06, 18 November 2025

2025-11-18T14:06:47Z

← Older revision		Revision as of 14:06, 18 November 2025
Line 49:		Line 49:
	''Main article:'' [[TPP Extract FHIR Mapping]]		''Main article:'' [[TPP Extract FHIR Mapping]]

	~~=== Vision ===~~
	~~''Main article:'' [[Vision GP Extract FHIR Mapping]]~~

	== Historic data feeds ==		== Historic data feeds ==
Line 64:		Line 62:
	=== Homerton ADT ===		=== Homerton ADT ===
	''Main article:'' [[Homerton ADT FHIR Mapping]]		''Main article:'' [[Homerton ADT FHIR Mapping]]

			=== Vision ===
			''Main article:'' [[Vision GP Extract FHIR Mapping]]

AdminJo: /* General approach */

2025-06-02T09:17:58Z

General approach

← Older revision		Revision as of 09:17, 2 June 2025
Line 10:		Line 10:
	== General approach ==		== General approach ==

	The initial transformation in the VHP is to an extended FHIR format i.e. a FHIR model with extensions, the extensions to ~~accomodate~~ the many dozens of properties and data types for ~~particular~~ specialist systems or specialties within providers. From the interim FHIR format, a further structural and semantic mapping occurs to a relational data model, stored in a form that can be efficiently queried and retrieved. This can be illustrated as follows:		The initial transformation in the VHP is to an extended FHIR format i.e. a FHIR model with extensions, the extensions to accommodate the many dozens of properties and data types for specialist systems or specialties within providers. From the interim FHIR format, a further structural and semantic mapping occurs to a relational data model, stored in a form that can be efficiently queried and retrieved. This can be illustrated as follows:

	[[File:Inbound.png\|center\|1600x500px\|Inbound.png]]		[[File:Inbound.png\|center\|1600x500px\|Inbound.png]]

AdminJo at 09:28, 21 May 2025

2025-05-21T09:28:57Z

← Older revision		Revision as of 09:28, 21 May 2025
Line 26:		Line 26:
	=== Acute ===		=== Acute ===
	''Main article:'' [[Publisher API HL7 Messages]]		''Main article:'' [[Publisher API HL7 Messages]]

			=== CDS Data ===
			''Main article:'' [[CDS Data]]

	=== Community Data ===		=== Community Data ===

AdminJo at 09:25, 21 May 2025

2025-05-21T09:25:19Z

← Older revision		Revision as of 09:25, 21 May 2025
Line 23:		Line 23:

	== New publisher data standards ==		== New publisher data standards ==

			=== Acute ===
			''Main article:'' [[Publisher API HL7 Messages]]

	=== Community Data ===		=== Community Data ===

AdminJo: /* High level (non-technical) overview */

2025-05-02T10:30:53Z

High level (non-technical) overview

← Older revision		Revision as of 10:30, 2 May 2025
Line 17:		Line 17:
	# The data is received from the publisher (various different publishers, systems, and versions) and is sent, in various different formats by various different mechanisms, into the VHP.		# The data is received from the publisher (various different publishers, systems, and versions) and is sent, in various different formats by various different mechanisms, into the VHP.
	# The gateway controls the IG and flow of data into the VHP file store and inbound/publisher queue.		# The gateway controls the IG and flow of data into the VHP file store and inbound/publisher queue.
	#The inbound queue reader (transform) is notified, by the inbound publisher queue, that there is new data, takes that new data and uses the FHIR maps to transform it, stores it in the FHIR store, and then puts a notification on the outbound/subscriber queue.		#The inbound queue reader (transform) is notified, by the inbound publisher queue, that there is new data.
	#The outbound queue reader (subscriber) is notified, by the outbound subscriber queue, that there is new FHIR data, takes that new data and uses the ontology, maps, and data models to make it available in a relational data store.		#The inbound queue reader (transform) takes that new data and uses the FHIR maps to transform it, stores it in the FHIR store, and then puts a notification on the outbound/subscriber queue.
			#The outbound queue reader (subscriber) is notified, by the outbound subscriber queue, that there is new FHIR data.
			#The outbound queue reader (subscriber) takes that new data and uses the ontology, maps, and data models to make it available in a relational data store.

	== New publisher data standards ==		== New publisher data standards ==

AdminJo: /* High level (non-technical) overview */

2025-05-02T10:29:46Z

High level (non-technical) overview

← Older revision		Revision as of 10:29, 2 May 2025
Line 18:		Line 18:
	# The gateway controls the IG and flow of data into the VHP file store and inbound/publisher queue.		# The gateway controls the IG and flow of data into the VHP file store and inbound/publisher queue.
	#The inbound queue reader (transform) is notified, by the inbound publisher queue, that there is new data, takes that new data and uses the FHIR maps to transform it, stores it in the FHIR store, and then puts a notification on the outbound/subscriber queue.		#The inbound queue reader (transform) is notified, by the inbound publisher queue, that there is new data, takes that new data and uses the FHIR maps to transform it, stores it in the FHIR store, and then puts a notification on the outbound/subscriber queue.
	#The outbound queue reader (subscriber) is notified, by the outbound subscriber queue, that there is new FHIR data, takes that new data, and uses the ontology, maps, and data models to make it available in a relational data store.		#The outbound queue reader (subscriber) is notified, by the outbound subscriber queue, that there is new FHIR data, takes that new data and uses the ontology, maps, and data models to make it available in a relational data store.

	== New publisher data standards ==		== New publisher data standards ==

AdminJo: /* High level (non-technical) overview */

2025-05-02T10:28:45Z

High level (non-technical) overview

← Older revision		Revision as of 10:28, 2 May 2025
Line 18:		Line 18:
	# The gateway controls the IG and flow of data into the VHP file store and inbound/publisher queue.		# The gateway controls the IG and flow of data into the VHP file store and inbound/publisher queue.
	#The inbound queue reader (transform) is notified, by the inbound publisher queue, that there is new data, takes that new data and uses the FHIR maps to transform it, stores it in the FHIR store, and then puts a notification on the outbound/subscriber queue.		#The inbound queue reader (transform) is notified, by the inbound publisher queue, that there is new data, takes that new data and uses the FHIR maps to transform it, stores it in the FHIR store, and then puts a notification on the outbound/subscriber queue.
	#The outbound queue reader (subscriber) is notified, by the outbound subscriber queue, that there is new FHIR data ~~and~~ takes that new data, and uses the ontology, maps, and data models to make it available in a relational data store.		#The outbound queue reader (subscriber) is notified, by the outbound subscriber queue, that there is new FHIR data, takes that new data, and uses the ontology, maps, and data models to make it available in a relational data store.

	== New publisher data standards ==		== New publisher data standards ==

AdminJo: /* High level (non-technical) overview */

2025-05-02T10:28:12Z

High level (non-technical) overview

← Older revision		Revision as of 10:28, 2 May 2025
Line 17:		Line 17:
	# The data is received from the publisher (various different publishers, systems, and versions) and is sent, in various different formats by various different mechanisms, into the VHP.		# The data is received from the publisher (various different publishers, systems, and versions) and is sent, in various different formats by various different mechanisms, into the VHP.
	# The gateway controls the IG and flow of data into the VHP file store and inbound/publisher queue.		# The gateway controls the IG and flow of data into the VHP file store and inbound/publisher queue.
	#The inbound queue reader (transform) is notified that there is new data ~~and~~ takes ~~the~~ new data and uses the FHIR maps to transform it, stores it in the FHIR store, and then puts a notification on the outbound/subscriber queue.		#The inbound queue reader (transform) is notified, by the inbound publisher queue, that there is new data, takes that new data and uses the FHIR maps to transform it, stores it in the FHIR store, and then puts a notification on the outbound/subscriber queue.
	#The outbound queue reader (subscriber) is notified, by the outbound subscriber queue, that there is new FHIR data and takes that new data, and uses the ontology, maps, and data models to make it available in a relational data store.		#The outbound queue reader (subscriber) is notified, by the outbound subscriber queue, that there is new FHIR data and takes that new data, and uses the ontology, maps, and data models to make it available in a relational data store.