# Essential Rm attributes - Implementation guideline

**URL:** <https://discourse.openehr.org/t/essential-rm-attributes-implementation-guideline/5054>\
**Category:** Specifications\
**Tags:** rm, aql\
**Created:** [26 March 2024 15:45 UTC](https://discourse.openehr.org/t/essential-rm-attributes-implementation-guideline/5054 "2024-03-26T15:45:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mar.perezcolman](https://discourse.openehr.org/user_avatar/discourse.openehr.org/mar.perezcolman/32/2863_2.png) [@mar.perezcolman](https://discourse.openehr.org/u/mar.perezcolman)\
**Post date:** [26 March 2024 15:45 UTC](https://discourse.openehr.org/t/essential-rm-attributes-implementation-guideline/5054/1 "2024-03-26T15:45:17Z")

</div>

Hi all,

In Wales, we are using openEHR as a structured clinical repository as part of our national platform, and we are trying to build a generic implementation guideline for any system in Wales aiming at storing data in our CDR.

We have established that we need three levels for any specific implementation guideline:

1. Required elements for the openEHR CDR.
2. Required/mandated data elements that are a Welsh standard. (eg: system
3. Specific Rm attributes for each form (eg PARTICIPATIONS for an MDT)

I was wondering if anyone had a document, github repo, code, or any other format with the list of the essential Rm attributes to commit a composition and their tree structure so that we can review it.

Our aim is to build a guideline to point developers from different applications (with their own form builders) to the correct place in the National CDR to store the Rm attributes data and avoid errors.

I am including @johnmeredith and @rach123 who are also working in this.

---

<div class="post-metadata">

**Author:** ![SevKohler](https://discourse.openehr.org/user_avatar/discourse.openehr.org/sevkohler/32/3504_2.png) [@SevKohler](https://discourse.openehr.org/u/SevKohler)\
**Post date:** [26 March 2024 15:48 UTC](https://discourse.openehr.org/t/essential-rm-attributes-implementation-guideline/5054/2 "2024-03-26T15:48:49Z")

</div>

You could check the generic mappers of my FHIR to openEHR ETL software.  
These usually cover the classical RM fields required for a composition.

> **[fhir-bridge/src/main/java/org/ehrbase/fhirbridge/ehr/converter/generic at...](https://github.com/SevKohler/fhir-bridge/tree/develop/src/main/java/org/ehrbase/fhirbridge/ehr/converter/generic)**
>
> FHIR Bridge acts as a broker between an HL7 FHIR client and an openEHR server. - SevKohler/fhir-bridge

The NameToName is FHIRType TO OpenEHRType 😉 so for composition check \*ToComposition.  
These are the [ones](https://github.com/SevKohler/fhir-bridge/blob/develop/src/main/java/org/ehrbase/fhirbridge/ehr/converter/generic/CompositionConverter.java#L35) always required  
Or you can also check what the implementers are defaulting for their flat formats, usually they prefill specific RM-fields to make the flat composition more readable.  
ping @vidi42 @matijap