...
| PR | Status | Description | VOTE TO PROGRESS | Discussion |
|---|---|---|---|---|
| SPECPR-1 | The type of VERSIONED_OBJECT.uid doesn't match the type of VERSION.uid.object_id | Release 1.1? | ||
| started | Remarks on architecture overview.pdf section 5.2.1 | TB | Roll into SPECRM-25 | |
| XML-schema not available for openEHR terminology xml file. | TB, DB | |||
| SPECPR-5 | started | In both 1.0.1 and 1.0.2 release, the aom.ARCHETYPE_ONTOLOGY class description doesn't have term_definition function. | TB, IM, ES, KA, DB | |
| SPECPR-6 | Should the aom.ARCHETYPE_SLOT have a function any_allowed? | TB, DB | Just add any_allowed to ARCHETYPE_SLOT in AOM 1.5 | |
| SPECPR-10 | started | PARTICIPATION is not LOCATABLE, so has no archetype_node_id, but occurs in archetyped structures | TB, IM, ES, DB, KA,BNA | Solution / impact not 100% clear, but I think it has to be done |
| SPECPR-21 | started | Need to record archetype licensing in a standard fashion | TB, IM, ES, DB, KA,BNA | |
| SPECPR-23 | started | Mandatory mode in participation | TB, IM, ES, DB, BL, KA, BNA | |
| SPECPR-24 | Improving Translation details and other_contributors | TB | Create CR, even though exact details not yet worked out | |
| started | Need to use the Terminology Resource file developed by Java implementation group as openEHR terminology resource Need new application content types (mime types) terminology.xml does not contain Khmer language. | TB, HF, BNA, IM TB, HF, BNA | create CR to create better representation of external | |
| SPECPR-26 | started | openEHR RM schema doesn't include EHR_STATUS and EHR_ACCESS | TB, IM, ES, BL, KA, BNA | |
| SPECPR-33 | started | DV_IDENTIFIER has mandatory features that are rarely used at present | TB, IM, ES, DB, BL, KA,BNA | |
| ||||
| SPECPR-35 | (Dup of 34; closed) | |||
| SPECPR-44 | started | Add support for Real values in DV_ORDINAL | TB, IM, ES, DB, KA,BNA | There are several issues related to ordinals, probably need a better discussion |
| SPECPR-54 | Conflict between PARTY_RELATIONSHIP.type() requirements and item-path specification | TB, HF, SI, KA | Convert to CR on RM to relax name uniqueness rule | |
| SPECPR-56 | started | Typos in EHR Extract IM | TB, IM, ES, DB, KA, BNA | |
| SPECPR-64 | started | DV_DATE magnitude origin is wrong | TB, IM, ES, DB, KA, BNA | Convert to CR on the RM (and ITS?) that defines a correct 'year 0' date for all of openEHR |
| SPECPR-65 | started | BaseTypes.xsd allows empty values in element that have an not empty Invariant in RM | TB, HF, KA, BNA | Convert to CR on XSD (ITS) with HF as owner |
| SPECPR-66 | started | BaseTypes.xsd allows ISO8601DateTime T separator as optional | TB, IM, ES, DB, BL, KA, BNA | |
| SPECPR-69 | started | Overview.pdf refers to wrong section when introducing LOCATABLE_REF | TB, IM, ES, KA, BNA | |
| SPECPR-71 | Typo in AOM specification 1.1 duplicated EXPR_ITEM | TB, IM, ES, KA, BNA | ||
| These are all to do with simplifying the 'lower model' of the RM (ITEM_XXX classes) | KA | Designate one as the main PR, close and reference the two others, and create a single CR in the RM component (exact change unknown so far) | ||
| started | Composition invariant precludes other_context in Persistent Composition Correction to COMPOSITION.category description | TB, IM, HF, KA, BNA | Convert to CR on RM; exact change still to be determined. | |
| SPECPR-110 | VERSION.uid.object_id / VERSIONED_OBJECT.uid type mismatch | TB, HF, BNA | Close as dup of SPECPR-1 (add reverse ref) | |
| SPECPR-118 | Support Clinical Finding pattern in RM | KA | Help reduce unnecessary clutter and improve modelling |
...