# Separating Models from Implementation

**URL:** https://discourse.openehr.org/t/separating-models-from-implementation/2093
**Category:** New to openEHR?
**Created:** [22 November 2021 13:56 UTC](https://discourse.openehr.org/t/separating-models-from-implementation/2093 "2021-11-22T13:56:51Z")
**Posts on this page:** 1
**Showing post:** 75

<div class="post-metadata">

### Author: ![erik.sundvall](https://discourse.openehr.org/user_avatar/discourse.openehr.org/erik.sundvall/32/1961_2.png) [@erik.sundvall](https://discourse.openehr.org/u/erik.sundvall)
#### Post date: [28 November 2021 22:08 UTC](https://discourse.openehr.org/t/separating-models-from-implementation/2093/75 "2021-11-28T22:08:37Z")

</div>

> [@ToStupidForOpenEHR](#):
>
> where can I read more on TDS/TSS?

They are all template-specific “streamlined” things, I belive TD… = Template Data…

- TDS …Schema (XML schema)
- TDD …Document (xml instances adhering to a TDS)
- TDO …Object(s) (Class definitions, used for simplifying programming applications & integrations)

The template specific “streamlined” OpenAPI descriptions discussed in this thread could be used to produce the equivalent of TDO in any programming language (I believe TDO from the back then was usually in some .NET format)

@heath.frankel is likely the main guru on the topic and was involved in creating TDS/TDD/TDO formats many years ago at Ocean Informatics (now called [https://oceanhealthsystems.com/](https://oceanhealthsystems.com/)). I believe many of the reasons for their creation were basically the same as the ones @ToStupidForOpenEHR brought up and that started this thread - to make it easier for developers and others to, for a specific use case, integrate/interact with openEHR systems - using familiar tools and without a learing too much about openEHR or openEHR specific tools.

When [searching for TDS in the old openEHR mailing list archives](https://www.mail-archive.com/search?q=TDS&l=openehr-technical%40lists.openehr.org) you’ll find a lot of the same thoughts as in the current discussion, e.g. in [2008](https://www.mail-archive.com/openehr-technical@lists.openehr.org/msg03394.html) and [2013](https://www.mail-archive.com/openehr-technical@lists.openehr.org/msg07758.html). I believe the main problem regarding adoption was that the TDS/TDD approach was never published as an official specification back then - it was used by Ocean and some of their customers (including Better/Marand for example).

In 2016-2017 things had changed and there was a willingness from Ocean to share/publish the approach and create a specification, work was started, see the wiki page [https://openehr.atlassian.net/wiki/spaces/spec/pages/30408770/Template+Data+Schema+TDS+Specification+and+associated+Template+Data+Document+TDD](https://openehr.atlassian.net/wiki/spaces/spec/pages/30408770/Template+Data+Schema+TDS+Specification+and+associated+Template+Data+Document+TDD) but never finished because of peoples’ busy schedules. Heath (who was very busy then) sent me some files that I (also busy) never got around to analyze and publish on that wiki page as a basis for further standardisation work. Perhaps it is time to pick that up again and let anybody interested help documenting the approach? @heath.frankel could you attach any files/descriptions for curious people to look at - on that wikipage or in this thread?

Others may have more information and links about TDS/TDD/TDO, please share. @Seref may know of current use at Ocean.

---

_[View the full topic](https://discourse.openehr.org/t/separating-models-from-implementation/2093)._