# Building and saving Compostitions

**URL:** https://discourse.openehr.org/t/building-and-saving-compostitions/14318
**Category:** Implementers (archive)
**Created:** [30 April 2013 10:29 UTC](https://discourse.openehr.org/t/building-and-saving-compostitions/14318 "2013-04-30T10:29:11Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Ze\_Silva](https://discourse.openehr.org/letter_avatar_proxy/v4/letter/z/b5ac83/32.png) [@Ze\_Silva](https://discourse.openehr.org/u/Ze_Silva)
#### Post date: [30 April 2013 10:29 UTC](https://discourse.openehr.org/t/building-and-saving-compostitions/14318/1 "2013-04-30T10:29:11Z")

</div>

Hi,

In my project, I built my templates with Template Designer and then I exported them to Operational Templates.

Using [openEHR.NET](http://openEHR.NET) library I can load the Operational Template building my composition.

Once the composition is built I can insert values in the leafs that I need.

For now I’m using brute force values.

I hope this is a good method to build compositions. There is not much information about this.

Now I’m thinking on how to save compositions in my database. I’m using NOSQL mongodb. I think i just need to save information that I can not obtain from the template, so for every composition I should save the id of the template (example: openEHR-EHR-COMPOSITION.medication\_list.v1) and the values inserted in each leaf.

If I’m thinking wrong I would like to know what. I’m new in this field and probably many things may not be correctly understood in my head.

Regards,  
José Silva

---

<div class="post-metadata">

### Author: ![Koray\_Atalag](https://discourse.openehr.org/user_avatar/discourse.openehr.org/koray_atalag/32/70_2.png) [@Koray\_Atalag](https://discourse.openehr.org/u/Koray_Atalag)
#### Post date: [17 May 2013 05:21 UTC](https://discourse.openehr.org/t/building-and-saving-compostitions/14318/2 "2013-05-17T05:21:08Z")

</div>

Hi Jose,

It seemed to me you’re trying to do a similar thing we did with GastrOS project.

It is an open source endoscopy reporting application fully driven by openEHR models (and operational template at runtime). Used and extended [openEHR.Net](http://openEHR.Net) library.

Take a look: [http://gastros.codeplex.com](http://gastros.codeplex.com)

Also:

1. 

Atalag K, Yang HY, Tempero E, Warren J. Model Driven Development of Clinical Information Sytems using openEHR. Stud Health Technol Inform. 2011;169:849–53.

[http://www.ncbi.nlm.nih.gov/pubmed/21893867](http://www.ncbi.nlm.nih.gov/pubmed/21893867)

1. 

Atalag K, Yang HY. From openEHR Domain Models to Advanced User Interfaces: a Case Study in Endoscopy. Wellington; 2010.

[http://www.hinz.org.nz/uploads/file/2010conference/P17\_Atalag.pdf](http://www.hinz.org.nz/uploads/file/2010conference/P17_Atalag.pdf)

Cheers,

-koray