Issues

Add Term Binding strengths to RM attributes which specify openEHR Terminology

Align the TERM_MAPPING purpose example with the term mapping purpose values

Code for 'episodic' clashes with 'laboratory' in openEHR terminology

Wrong class definition in Support Information Model documentation

Restart completed activity

Legacy mapping scenarios conversion recommendations can be improved

AUDIT_DETAILS.change_type should be optional

Change VERSION.uid() method to be an attribute VERSION.uid like it is on the subclasses IMPORTED_VERSION and ORIGINAL_VERSION.

OBJECT_VERSION_ID typos in format

test 2

test

ISM possible missing transitions

INTERVAL_EVENT questions about the correctness of the specs‏

Add "last modified" date/time attribute for ENTRY classes in RM

Error in RESOURCE_DESCRIPTION.details class in RM Common IM spec

I have a problem about "openEHR data conversion architecture"

Add some place to put data on the FOLDER object

The definition of summary data is unclear regarding quite what a summary is expected to be

Composition invariant precludes other_context in Persistent Composition

Simplify RM by reducing or removing ITEM_STRUCTURE package

Overview.pdf refers to wrong section when introducing LOCATABLE_REF

Remarks on Architecture Overview section 5.2.1