Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 26 Next »

21 May 2015 - Meeting Preparation

Problem Report discussion. SEC members: please add new PRs to this table as required, and update Vote / Discussion columns.

PRStatusDescriptionVOTE TO
PROGRESS 
Discussion

SPECPR-2

startedRemarks on architecture overview.pdf section 5.2.1TBRoll into SPECRM-25
SPECPR-5startedIn 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 
SPECPR-6 Should the aom.ARCHETYPE_SLOT have a function any_allowed?TBJust add any_allowed to ARCHETYPE_SLOT in AOM 1.5
SPECPR-10startedPARTICIPATION is not LOCATABLE, so has no archetype_node_id, but occurs in archetyped structures TB, IM, ES, DB, KA,BNASolution / impact not 100% clear, but I think it has to be done
     
SPECPR-21startedNeed to record archetype licensing in a standard fashionTB, IM, ES, DB, KA,BNA 
SPECPR-23startedMandatory mode in participationTB, IM, ES, DB, BL, KA, BNA
 
SPECPR-24 Improving Translation details and other_contributorsTBCreate CR, even though exact details not yet worked out
SPECPR-26startedopenEHR RM schema doesn't include EHR_STATUS and EHR_ACCESSTB, IM, ES, BL, KA, BNA
 
     
SPECPR-33startedDV_IDENTIFIER has mandatory features that are rarely used at presentTB, IM, ES, DB, BL, KA,BNA
 

SPECPR-34

 terminology.xml does not contain Khmer language.
create CR to create better representation of external
code-sets for use in openEHR.
SPECPR-35 (Dup of 34; closed)  
SPECPR-44startedAdd support for Real values in DV_ORDINALTB, IM, ES, DB, KA,BNAThere are several issues related to ordinals, probably need a
better discussion
SPECPR-54 Conflict between PARTY_RELATIONSHIP.type() requirements and item-path specificationTB, HF, SI, KAConvert to CR on RM to relax name uniqueness rule
SPECPR-56startedTypos in EHR Extract IMTB, IM, ES, DB, KA, BNA
 
SPECPR-64startedDV_DATE magnitude origin is wrongTB, 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-65startedBaseTypes.xsd allows empty values in element that have an not empty Invariant in RMTB, HF, KA, BNAConvert to CR on XSD (ITS) with HF as owner
SPECPR-66startedBaseTypes.xsd allows ISO8601DateTime T separator as optionalTB, IM, ES, DB, BL, KA, BNA
 
SPECPR-69startedOverview.pdf refers to wrong section when introducing LOCATABLE_REFTB, IM, ES, KA, BNA
 
SPECPR-71 Typo in AOM specification 1.1  duplicated EXPR_ITEMTB, IM, ES, KA, BNA
 

SPECPR-73

SPECPR-74

SPECPR-106

 These are all to do with simplifying the 'lower model' of the RM (ITEM_XXX classes)KADesignate 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)

SPECPR-78

SPECPR-88

 

Composition invariant precludes other_context in Persistent Composition

Correction to COMPOSITION.category description

TB, IM, HF, KA, BNAConvert to CR on RM; exact change still to be determined.
SPECPR-97 Need new application content types (mime types)TB, HF, BNAClose as duplicate of SPECPR-25 (add reverse ref)
SPECPR-110 VERSION.uid.object_id / VERSIONED_OBJECT.uid type mismatchTB, HF, BNAClose as dup of SPECPR-1 (add reverse ref)
SPECPR-118 Support Clinical Finding pattern in RMKAHelp reduce unnecessary clutter and improve modelling

 



  • No labels