Skip to:

Skip to Jira Navigation
Skip to Side Navigation
Skip to Main Content

Specifications: Implementation Technologies

Software project

Back to project

Default Filters

Resolved recently

Updated recently

View all filters

You're in a company-managed project

Projects
Specifications: Implementation Technologies

Issues

Go to all issues

Select view

List view

Detail view

Select search mode

Basic

JQL

Add admin support to delete EHR
SPECITS-80
Add support for TAGS
SPECITS-77
Fix inconsistent and invalid header names
SPECITS-75
Add specs Content-Location header as a replacement of Location
SPECITS-74
Change structure and improve yaml specs
SPECITS-73
Resolved issue: SPECITS-73
Add demographic endpoint
SPECITS-70
Add "SMART on openEHR" specifications
SPECITS-69
Make PUT Idempotent
SPECITS-68
Migrate REST API specs to OpenAPI format
SPECITS-66
Resolved issue: SPECITS-66
Fixing typos, formatting and minor documentary errors
SPECITS-65
Support for JSON and SDF serialization formats on request headers
SPECITS-64
Add support for FOLDERs under EHR
SPECITS-63
Document handling of client-side generated UIDs on POST Composition
SPECITS-62
Cleanup and consolidate (or merge) SDF and SDT specs
SPECITS-61
Fix inconsistent return status code on creating resources
SPECITS-60
Specify mimeType used by adl2 template
SPECITS-59
Resolved issue: SPECITS-59
Add support for /example sub-resource
SPECITS-58
Update info about simplified JSON formats
SPECITS-57
Resolved issue: SPECITS-57
Fixing typos, formatting and minor documentary errors
SPECITS-56
Resolved issue: SPECITS-56
Sync BASE XML schema with Release 1.2.0
SPECITS-55
Resolved issue: SPECITS-55
Fix wrong optional flag for ACTIVITY.action_archetype_id in XML schema
SPECITS-54
Resolved issue: SPECITS-54
Fix wrong type on DV_QUANTITY.magnitude in XML schema
SPECITS-53
Resolved issue: SPECITS-53
JSON-schema: define DV_MULTIMEDIA.data as base64, not an array of string
SPECITS-51
Return very minimal REST responses to avoid 204 No content codes.
SPECITS-50
describing Resource Identification; add clarification over getting compositions by with version_uid vs versioned_object_uid
SPECITS-49
Resolved issue: SPECITS-49
Define case of updating a COMPOSITION referencing a different OPT
SPECITS-48
Fix inconsistency over query_parameter(s)
SPECITS-47
Resolved issue: SPECITS-47
Fix conflictual query execution endpoint-resolution when query name is 'aql'
SPECITS-46
Describe more clearly the datetime format for REST API
SPECITS-45
Resolved issue: SPECITS-45
Add status 409 to POST .../ehr/{ehr_id}/directory
SPECITS-44
Add support to delete an update TEMPLATE
SPECITS-43
Fix TEMPLATE_ID value format in examples
SPECITS-42
Resolved issue: SPECITS-42
Add double quotes to ETag and If-Match headers
SPECITS-41
Resolved issue: SPECITS-41
Correct and improve documentation on EHR
SPECITS-40
Resolved issue: SPECITS-40
Register and specify supported content-types
SPECITS-39
Add support for 422 Unprocessable Entity
SPECITS-38
Resolved issue: SPECITS-38
Fix few other query related issues
SPECITS-37
Resolved issue: SPECITS-37
Improve Query REST API
SPECITS-36
Add has_xxx operations to the REST API
SPECITS-35
use SM derived models as REST API resources
SPECITS-34
Add Simplified Data Template format specification
SPECITS-33
Resolved issue: SPECITS-33
Correct text or fix various typos of REST APIs
SPECITS-32
Resolved issue: SPECITS-32
REST API documentation has a layout glitch
SPECITS-31
Resolved issue: SPECITS-31
Cleanup /query endpoint
SPECITS-30
Resolved issue: SPECITS-30
Align REST API look & feel other openEHR specifications
SPECITS-29
Resolved issue: SPECITS-29
Improve REST Api crosslinks
SPECITS-25
Resolved issue: SPECITS-25
Add change log information on doc-pages.
SPECITS-24
Resolved issue: SPECITS-24
DV_ENCAPSULATED.size attribute is missing
SPECITS-23
Resolved issue: SPECITS-23
Enforce an ELEMENT to require choice of value or null_flavour
SPECITS-22
Resolved issue: SPECITS-22
Specify constraints of DV_QUANTIFIED.magnitude_status
SPECITS-21
Resolved issue: SPECITS-21

50 of 70

Remove ADDRESS.as_string() and PARTY_IDENTITY.as_string() functions

Done

Raise

Analysis

Raise

Analysis

Description

The returned format of this functions can be left to implementation and can be country/local/vendor specific, but some guidance or example in the specification could be useful. During discussions on the mailing list, suggested approach was to either use another archetyped attribute to carry a formatting template or alternatively an external mapping system to solve the serialization.
See http://lists.chime.ucl.ac.uk/mailman/private/openehr-technical/2010-August/005297.html for more info.

Linked issues

PR is addressed in

Remove ADDRESS.as_string() and PARTY_IDENTITY.as_string() functions

Rong Chen

Details

Reporter

Sebastian Iancu

Sebastian Iancu

Components

Affects versions

RM Release 1.0.2

Priority

Minor

Created November 18, 2010 at 2:51 PM

Updated December 10, 2015 at 10:33 AM

Resolved December 10, 2015 at 10:33 AM

Activity

Show:

Heath FrankelMay 8, 2015 at 1:02 AM

Do we really need this function at the RM level? It is archetype specific so it would be difficult to specify any templates at the RM level unless they are generic rules based on RM. I don't believe the latter will be a user friendly option.