# openEHR on FHIR and vice versa

**URL:** https://discourse.openehr.org/t/openehr-on-fhir-and-vice-versa/15548
**Category:** Technical (archive)
**Created:** [14 December 2018 10:18 UTC](https://discourse.openehr.org/t/openehr-on-fhir-and-vice-versa/15548 "2018-12-14T10:18:17Z")
**Posts on this page:** 2
**Page:** 2

<div class="post-metadata">

### Author: ![yampeku](https://discourse.openehr.org/user_avatar/discourse.openehr.org/yampeku/32/25_2.png) [@yampeku](https://discourse.openehr.org/u/yampeku)
#### Post date: [19 December 2018 15:10 UTC](https://discourse.openehr.org/t/openehr-on-fhir-and-vice-versa/15548/21 "2018-12-19T15:10:47Z")

</div>

Yeah, it is processable, and it isn’t based on any specific refrence model so any pair of models should be fine (even non-standard ones)

---

<div class="post-metadata">

### Author: ![system](https://discourse.openehr.org/uploads/default/original/2X/f/f0a1dedb20c42747bddcafd6c7df9db5f34f003c.svg) [@system](https://discourse.openehr.org/u/system)
#### Post date: [19 December 2018 15:32 UTC](https://discourse.openehr.org/t/openehr-on-fhir-and-vice-versa/15548/22 "2018-12-19T15:32:13Z")

</div>

FYI See example JSON based //openEHR ↔ FHIR mapping template //for Allergy content attached and more here  
[https://github.com/RippleOSI/Ripple-FHIR/tree/master/FHIR-Ripple\_Mapping/examples/templates](https://github.com/RippleOSI/Ripple-FHIR/tree/master/FHIR-Ripple_Mapping/examples/templates)

This approach has also been designed with npm in mind for easy distribution and usage, as per video here  
[https://www.youtube.com/watch?v=iaGGGgJdWvM&list=PLNxHSK29ViKLrrhdPTqbYr6XGTya4uGBv&index=9](https://www.youtube.com/watch?v=iaGGGgJdWvM&list=PLNxHSK29ViKLrrhdPTqbYr6XGTya4uGBv&index=9)

regards

Tony

> **(attachments)**
>
> [openEHR\_to\_FHIR\_Allergies.json](https://discourse.openehr.org/404) (2.41 KB)

[Previous page](https://discourse.openehr.org/t/openehr-on-fhir-and-vice-versa/15548.md?page=1)