1 / 8

Creation of a FHIR facade

Creation of a FHIR facade. for a legacy database backend. René Spronk Trainer / Senior Consultant Ringholm , the Netherlands eMail: Rene.Spronk@Ringholm.com Web: http://www.Ringholm.com. Based (in part) on the work of Brian Postlethwaithe and others.

leannh
Télécharger la présentation

Creation of a FHIR facade

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Creation of a FHIR facade for a legacy database backend René Spronk Trainer / Senior Consultant Ringholm, the Netherlands eMail: Rene.Spronk@Ringholm.com Web: http://www.Ringholm.com Based (in part) on thework of Brian Postlethwaitheandothers.

  2. Scenario: FHIR Facade / Assumptions FHIR Facade GUIs Facade database Business Services API ER Legacy database • Developers of Facademaynotbethesameones as thedevelopers of thelegacyapplication. • Assume 90-100% of all “data retrievals” tobedirectlyfromthe ER database. • Assume most (but notall) “data storage” tobedone via theapplicationsown API (business ruleenforcement). • Don’tduplicate full data in a separate FHIR-based database / minimize “caching”.

  3. (non-query) Content Conversion • On the fly conversion • Data types, terminologies, granularity of data • On export: additional ‘columns’ to FHIR extensions ? • If using database views, updates can be challenging. • Use Provenance to document what (third party) translation tool has been used

  4. Resource Identity (resource.id) • Use primary Key • If exists (for a particular resource type), primary key should not be a business identifier (which may be subject to change) • Add resource_id table to facade database

  5. Query Conversion, Searching • On the fly query conversion • Lossy query conversion is fine • Indexes can be either: • in replicated content • views on the source data • Synchronized from source data

  6. History • Decide not to support history, each and every retrieval is a ‘new’ version • Cache the content that was returned • History can remain in the cache • If a subsequent retrieve results in the same (byte wise) data, the cached version can be returned

  7. Other issues Security / access control

  8. Questions?

More Related