Publishers and mapping to the common model: Difference between revisions
No edit summary |
|||
| (16 intermediate revisions by 2 users not shown) | |||
| Line 4: | Line 4: | ||
Some providers have systems that have a common mechanism of publishing data. Typical examples of this are GP system suppliers such as EMIS, TPP or Vision. In this case the transformation and mapping can be standardised and used for any publisher. | Some providers have systems that have a common mechanism of publishing data. Typical examples of this are GP system suppliers such as EMIS, TPP or Vision. In this case the transformation and mapping can be standardised and used for any publisher. | ||
Some providers have systems that do not have a mechanism of publishing data, or where they do, a particular provider may not have purchased it. In this case a transformation and mapping exercise has to be undertaken | Some providers have systems that do not have a mechanism of publishing data, or where they do, a particular provider may not have purchased it. In this case a transformation and mapping exercise has to be undertaken specifically for that provider. In many cases that also means a variety of source systems are involved. | ||
These articles summarise the necessary transformations and mappings needed for each provider system. | These articles summarise the necessary transformations and mappings needed for each provider system. | ||
| Line 14: | Line 14: | ||
[[File:Inbound.png|center|800x250px|Inbound.png]] | [[File:Inbound.png|center|800x250px|Inbound.png]] | ||
== | == New publisher data standards == | ||
== | === Acute === | ||
''Main article:'' [[Publisher API HL7 Messages]] | |||
== | === CDS Data === | ||
''Main article:'' [[CDS Data]] | |||
== | === Community Data === | ||
''Main article:'' [[Community data FHIR mapping]] | |||
== | === Mental Health === | ||
''Main | ''Main article:'' [[Mental Health FHIR Store Mappings]] | ||
== | === Social Care === | ||
''Main article:'' [[Social Care FHIR Store Mappings]] | |||
== | === Unstructured Secondary Care === | ||
''Main article:'' [[Unstructured secondary care data FHIR mapping]] | |||
== Live data feeds == | |||
== | === Adastra === | ||
''Main | ''Main article:'' [[Adastra Extract FHIR Mapping]] | ||
== | === BHRUT Medway === | ||
''Main article:'' [[BHRUT Medway Extract FHIR Mapping]] | |||
== Vision == | === Cerner Imperial === | ||
=== EMIS === | |||
''Main article:'' [[EMIS GP published data transformation and mapping]] | |||
=== TPP === | |||
''Main article:'' [[TPP Extract FHIR Mapping]] | |||
=== Vision === | |||
''Main article:'' [[Vision GP Extract FHIR Mapping]] | |||
== Historic data feeds == | |||
=== Barts Health ADT === | |||
''Main article:'' [[HL7 ADT]] (Draft) | |||
=== Barts Health CDS === | |||
''Main article'': [[Barts Health CDS FHIR Mapping]] | |||
=== Barts Health Cerner === | |||
=== Homerton ADT === | |||
''Main article:'' [[Homerton ADT FHIR Mapping]] | |||
Latest revision as of 15:08, 11 December 2023
Publishers are defined as any provider system, or provider/ system/version combination that sends data to Discovery or provides an API for Discovery to use to obtain data.
Some providers have systems that have a common mechanism of publishing data. Typical examples of this are GP system suppliers such as EMIS, TPP or Vision. In this case the transformation and mapping can be standardised and used for any publisher.
Some providers have systems that do not have a mechanism of publishing data, or where they do, a particular provider may not have purchased it. In this case a transformation and mapping exercise has to be undertaken specifically for that provider. In many cases that also means a variety of source systems are involved.
These articles summarise the necessary transformations and mappings needed for each provider system.
General approach
The initial transformation in Discovery 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 the common model and the data is stored in a form that can be efficiently queried and retrieved. This can be illustrated as follows:
New publisher data standards
Acute
Main article: Publisher API HL7 Messages
CDS Data
Main article: CDS Data
Community Data
Main article: Community data FHIR mapping
Mental Health
Main article: Mental Health FHIR Store Mappings
Social Care
Main article: Social Care FHIR Store Mappings
Unstructured Secondary Care
Main article: Unstructured secondary care data FHIR mapping
Live data feeds
Adastra
Main article: Adastra Extract FHIR Mapping
BHRUT Medway
Main article: BHRUT Medway Extract FHIR Mapping
Cerner Imperial
EMIS
Main article: EMIS GP published data transformation and mapping
TPP
Main article: TPP Extract FHIR Mapping
Vision
Main article: Vision GP Extract FHIR Mapping
Historic data feeds
Barts Health ADT
Main article: HL7 ADT (Draft)
Barts Health CDS
Main article: Barts Health CDS FHIR Mapping
Barts Health Cerner
Homerton ADT
Main article: Homerton ADT FHIR Mapping