Difference between revisions of "Interpretation of Effective Time for Acts in Definition Mood"
|Line 55:||Line 55:|
There is now guidance in the Implementation section of our wiki. [[Pharmacy
There is now guidance in the Implementation section of our wiki. [[Pharmacy |Timing in Pharmacy Models]]
Revision as of 18:48, 23 September 2013
--Tom de Jong 21:01, 17 January 2012 (UTC)
The problem at hand is most clearly explained by looking at: A_ProductUseGuideline(Canada) from the Common Product Model domain, which has artefact ID POCP_RM060200UV (and which has a name that clearly needs to be updated, by the way). It has a class called AdministrationGuideline, which includes the effectiveTime attribute. The description for that is 'Guideline Issue Date'. Yet the RIM semantics of effectiveTime dictate that the effectiveTime is always about the EVENT (e.g. effectiveTime in an order is about when the ordered event should take place), so this use seems inconsistent with that. Question then remains how we would specify the issue date (or validity interval) of the guideline itself.
Guidance was sought with MnM for this, but has not lead to a resolution.
2012 May WGM - Mon Q2 discussion: [John Hatam] This isn't just about Definition Mood. We should consider all Moods. Following discussion remains about Definition Mood.
[Nicolas] is this about effectiveTime in real time, or as it is defined in HL7 models? There are connections between the two, but they are not identical.
Really need business names for elements here. In this case, "Guideline Issue Date' (really 'Guideline Publication Date') defines the use.
The effectiveTime attribute appears to indicate when the Guideline is effective, 'in force', must be used - which may not be anything to do with the publication.
Recommendation that this is resolved by use of the 'time' on Author participation to the guideline.
There is now guidance in the Implementation section of our wiki. Timing in Pharmacy Models