# ITS **URL:** https://discourse.openehr.org/c/specifications/its/41.md?page=1 [Latest](https://discourse.openehr.org/latest.md) · [Categories](https://discourse.openehr.org/categories.md) · [Tags](https://discourse.openehr.org/tags.md) **Page:** 2 --- ## [Sending UID in a new composition](https://discourse.openehr.org/t/sending-uid-in-a-new-composition/2312)
**Author:** [@joseph.kane](https://discourse.openehr.org/u/joseph.kane)\ **Replies:** 5\ **Last updated:** [2 February 2022 05:26 UTC](https://discourse.openehr.org/t/sending-uid-in-a-new-composition/2312 "2022-02-02T05:26:12Z")
In the API specs for creating a new composition via POST, the example shows an included uid. This seems strange to me, since it should be the responsibility of the receiving system to create the uid. Because the root nee… --- ## [Adding HEAD methods to support RM has\_\*() operations](https://discourse.openehr.org/t/adding-head-methods-to-support-rm-has-operations/2143)
**Author:** [@sebastian.iancu](https://discourse.openehr.org/u/sebastian.iancu)\ **Replies:** 3\ **Last updated:** [17 December 2021 01:38 UTC](https://discourse.openehr.org/t/adding-head-methods-to-support-rm-has-operations/2143 "2021-12-17T01:38:38Z")
I am working on REST specifications to support \[SPECPR-307\] Add has\_xxx operations to the REST API spec - openEHR JIRA. The idea is to add HEAD method, similar to GET, to check whether a resource exists, but without ret… --- ## [REST API: definition operations query version ids](https://discourse.openehr.org/t/rest-api-definition-operations-query-version-ids/2191)
**Author:** [@thomas.beale](https://discourse.openehr.org/u/thomas.beale)\ **Replies:** 3\ **Last updated:** [13 December 2021 22:18 UTC](https://discourse.openehr.org/t/rest-api-definition-operations-query-version-ids/2191 "2021-12-13T22:18:00Z")
I just realised after we dropped the call that on the question of query formalism version id - if it’s a non-numeric version id, i.e. just some name or string like ‘2019-3’ or whatever, then the string could be nameversi… --- ## [Invariants are not part of the BMM files](https://discourse.openehr.org/t/invariants-are-not-part-of-the-bmm-files/2132)
**Author:** [@borut.jures](https://discourse.openehr.org/u/borut.jures)\ **Replies:** 10\ **Last updated:** [2 December 2021 17:18 UTC](https://discourse.openehr.org/t/invariants-are-not-part-of-the-bmm-files/2132 "2021-12-02T17:18:28Z")
I just learned about the “Invariants” section of the specifications. I would like to use them when generating solutions based on the BMM specifications. I know this is probably a big undertaking but can the invariants … --- ## [Modularisation vs openEHR monoliths. What would be interesting today?](https://discourse.openehr.org/t/modularisation-vs-openehr-monoliths-what-would-be-interesting-today/2057)
**Author:** [@erik.sundvall](https://discourse.openehr.org/u/erik.sundvall)\ **Replies:** 8\ **Last updated:** [12 November 2021 12:34 UTC](https://discourse.openehr.org/t/modularisation-vs-openehr-monoliths-what-would-be-interesting-today/2057 "2021-11-12T12:34:25Z")
Data can flow just fine between different openEHR implementations already, e.g. via the openEHR REST APIs. Those APIs also allow frontend and backend to come from different implementations. But for backend products/dep… --- ## [Can POST /directory have an empty body?](https://discourse.openehr.org/t/can-post-directory-have-an-empty-body/1994)
**Author:** [@pablo](https://discourse.openehr.org/u/pablo)\ **Replies:** 12\ **Last updated:** [29 October 2021 20:45 UTC](https://discourse.openehr.org/t/can-post-directory-have-an-empty-body/1994 "2021-10-29T20:45:26Z")
The POST /directory doesn’t specify if the body can be empty. https://specifications.openehr.org/releases/ITS-REST/Release-1.0.2/ehr.html#directory-directory-post Testing EHRBASE it seems the current implementation req… --- ## [Validating against RM schemas in the REST API](https://discourse.openehr.org/t/validating-against-rm-schemas-in-the-rest-api/1992)
**Author:** [@pablo](https://discourse.openehr.org/u/pablo)\ **Replies:** 0\ **Last updated:** [26 October 2021 21:38 UTC](https://discourse.openehr.org/t/validating-against-rm-schemas-in-the-rest-api/1992 "2021-10-26T21:38:26Z")
How are we handling differences in API request / response payloads to the schemas for canonical JSON and XML? Some payloads won’t validate against the schemas, for instance, missing contribution.uid on POST /contributio… --- ## [Flatform and Composition](https://discourse.openehr.org/t/flatform-and-composition/1794)
**Author:** [@Yash](https://discourse.openehr.org/u/Yash)\ **Replies:** 3\ **Last updated:** [26 August 2021 00:55 UTC](https://discourse.openehr.org/t/flatform-and-composition/1794 "2021-08-26T00:55:56Z")
Hello Forum , I am very confused as to what are flat forms , how are they created from a template , how are they different from compositions and what are they used for ? Thank You --- ## [Simplified Data Template (SDT) - Behavior](https://discourse.openehr.org/t/simplified-data-template-sdt-behavior/905)
**Author:** [@birger.haarbrandt](https://discourse.openehr.org/u/birger.haarbrandt)\ **Replies:** 15\ **Last updated:** [14 May 2021 11:26 UTC](https://discourse.openehr.org/t/simplified-data-template-sdt-behavior/905 "2021-05-14T11:26:19Z")
Hi everybody, we are currently implementing the simSDT format in EHRbase respectively the openEHR SDK. However, we found some behavior that is not defined in the current spec. For example, in the Better implementation,… --- ## [Return=minimal - 204 no-content is confusing](https://discourse.openehr.org/t/return-minimal-204-no-content-is-confusing/1056)
**Author:** [@ian.mcnicoll](https://discourse.openehr.org/u/ian.mcnicoll)\ **Replies:** 18\ **Last updated:** [26 March 2021 19:28 UTC](https://discourse.openehr.org/t/return-minimal-204-no-content-is-confusing/1056 "2021-03-26T19:28:08Z")
Although the current REST behaviour, providing a lto of 204 codes, on successful transactions, is correct, it is pretty confusing for developers, and there seems to be no agreement on minimal responses that might trigger… --- ## [JSON/XML data representation considering ADL constraints](https://discourse.openehr.org/t/json-xml-data-representation-considering-adl-constraints/1427)
**Author:** [@pablo](https://discourse.openehr.org/u/pablo)\ **Replies:** 6\ **Last updated:** [25 March 2021 18:27 UTC](https://discourse.openehr.org/t/json-xml-data-representation-considering-adl-constraints/1427 "2021-03-25T18:27:08Z")
Hi all, today we found a case when sharing observations between different systems, for instance Blood Pressure. In the archetype, systolic and diastolic precision is limited to zero, which means DV\_QUANTITY.magnitude is… --- ## [Simplified JSON data formats for openEHR](https://discourse.openehr.org/t/simplified-json-data-formats-for-openehr/915)
**Author:** [@thomas.beale](https://discourse.openehr.org/u/thomas.beale)\ **Replies:** 21\ **Last updated:** [25 March 2021 13:16 UTC](https://discourse.openehr.org/t/simplified-json-data-formats-for-openehr/915 "2021-03-25T13:16:34Z")
For those interested, here is a wiki page on which we are refining so-called simplified (JSON) data formats for representing EHR data when talking through openEHR REST APIs, and maybe in other contexts. This is likely t… --- ## [Template Data Document and Schema?](https://discourse.openehr.org/t/template-data-document-and-schema/1107)
**Author:** [@bna](https://discourse.openehr.org/u/bna)\ **Replies:** 3\ **Last updated:** [5 January 2021 11:22 UTC](https://discourse.openehr.org/t/template-data-document-and-schema/1107 "2021-01-05T11:22:26Z")
I am working on an integration with the national Cancer registry. They have a proprietary xml specification. They will do the mapping from canonical openehr xml themselves. The tool they use for mapping is Altova Map For… --- ## [API template version](https://discourse.openehr.org/t/api-template-version/941)
**Author:** [@vjoba](https://discourse.openehr.org/u/vjoba)\ **Replies:** 3\ **Last updated:** [25 August 2020 19:51 UTC](https://discourse.openehr.org/t/api-template-version/941 "2020-08-25T19:51:53Z")
Hello, I want to implement POST call /definition/template/adl2/{?version}. As I understand, the template version inside the template file and URL can be different. The URL version is optional. So what version should b… --- ## [Simplified Data Template (SDT) - data types](https://discourse.openehr.org/t/simplified-data-template-sdt-data-types/546)
**Author:** [@thomas.beale](https://discourse.openehr.org/u/thomas.beale)\ **Replies:** 23\ **Last updated:** [12 August 2020 11:41 UTC](https://discourse.openehr.org/t/simplified-data-template-sdt-data-types/546 "2020-08-12T11:41:57Z")
Following our decision to provide a more basic specification of the Simplified Data Template (SDT), I thought I would start at the ‘easy’ end, i.e. data types and various low level RM types. Here is a wiki page that I am… --- ## [REST: POST EHR directory twice, what happens?](https://discourse.openehr.org/t/rest-post-ehr-directory-twice-what-happens/432)
**Author:** [@matijap](https://discourse.openehr.org/u/matijap)\ **Replies:** 3\ **Last updated:** [3 August 2020 10:00 UTC](https://discourse.openehr.org/t/rest-post-ehr-directory-twice-what-happens/432 "2020-08-03T10:00:31Z")
What should happen in the EHR directory is created (POST) twice? PUT is used for updates and requires If-Match to prevent conflicting concurrent updates. POST should probably return 409 Conflict if EHR already has a dire… --- ## [JSON schema format, is attribute order considered for validating JSON?](https://discourse.openehr.org/t/json-schema-format-is-attribute-order-considered-for-validating-json/731)
**Author:** [@pablo](https://discourse.openehr.org/u/pablo)\ **Replies:** 5\ **Last updated:** [31 May 2020 07:10 UTC](https://discourse.openehr.org/t/json-schema-format-is-attribute-order-considered-for-validating-json/731 "2020-05-31T07:10:04Z")
Hi, I’m working on generating the canonical JSON format, and I’m not sure if the attribute order should be the same as the one declared in the JSON Schemas, or if for JSON the order is not important. I know for XML XSD… --- ## [JSON - howto serialise enumerations?](https://discourse.openehr.org/t/json-howto-serialise-enumerations/596)
**Author:** [@bna](https://discourse.openehr.org/u/bna)\ **Replies:** 1\ **Last updated:** [24 April 2020 08:47 UTC](https://discourse.openehr.org/t/json-howto-serialise-enumerations/596 "2020-04-24T08:47:48Z")
When serialising openEHR types to JSON should we use the numbered code or the name of the type? I.e. when serialising VALIDITY\_KIND enumeration I know we discussed this sometime ago, but I wasn’t able to find the resou… --- ## [Does ETag in composition response header really need quotes?](https://discourse.openehr.org/t/does-etag-in-composition-response-header-really-need-quotes/404)
**Author:** [@johnmeredith](https://discourse.openehr.org/u/johnmeredith)\ **Replies:** 10\ **Last updated:** [8 March 2020 10:09 UTC](https://discourse.openehr.org/t/does-etag-in-composition-response-header-really-need-quotes/404 "2020-03-08T10:09:03Z")
It’s all in the title but I note that the compositionUID comes back within quotes e.g. "acf0a908-71b0-4e17-9d77-005cca119672::local.ehrbase.org::1". What’s the reason behind the quotes as this obviously puts another step… [Previous page](https://discourse.openehr.org/c/specifications/its/41.md)