Monday, January 7, 2008
Volume 7 of the pan-Canadian standards - the SHR
FYI - Just wanted to let you know that Vol. 7 will become the official Shared Health Record (SHR) Implementation Guide (IG)and the iEHR Standards IG will become part of Vol. 7. In my note to you on Dec. 26th responding to your questions, I indicated that Vol. 7 should be made part of the iEHR Standards IG, but the decision has now been made to incorporate the iEHR IG into volume 7. This was only clarified recently for Dragana and me [Marion Lyver].
Thursday, January 3, 2008
Extending XML
So, bit of key info from Lloyd McK on extensions - apparently there are rules saying (somewhere) that extensions must be derived from RIM and existing datatypes. Not sure how this is expected to be enforced and certainly provides an unfair constraint on the implementer to have the solution space pre-defined. I am a strongly against this beyond "should".
Scope and Tracking Framework - effective Dates
Use of effective from and effective to columns in the Scope and Tracking Framework.
The intention is to identify what the allowed values are for the effectiveTime in the ControlAct. If AllowFutureDate is true, the effective time can be different from the author time. E.g. Send a message now asking for a prescription to be suspended next Tuesday. The "allow end" means you can specify and end date as well. E.g. Suspend this on Tuesday and release it a week later.
The intention is to identify what the allowed values are for the effectiveTime in the ControlAct. If AllowFutureDate is true, the effective time can be different from the author time. E.g. Send a message now asking for a prescription to be suspended next Tuesday. The "allow end" means you can specify and end date as well. E.g. Suspend this on Tuesday and release it a week later.
Wednesday, January 2, 2008
v3 Generator
The v3 Generator may not generate nodes in the same order if the sortOrder of the objects varies. The sort order in java may change for a lot of reasons:
Your fundamental assertion is correct. However "inputs" can be interpreted fairly broadly:
- Sort order has changed based on the JVM (one of the 1.4 versions did wonky things)
- Sort order can change when you generate with new RIM vocabulary and formal naming input files
- Sort order can change when you manipulate a Visio file, as changing the z-order of shapes within the diagram can affect class names, which in turn affects sort order. Adding or removing classes can do the same.
- Changes to the tools, reflecting updated methodology or fixes to bugs can also change names and thus sort order
However, if all of those variables remain constant, the sort order will remain the same from generation to generation. Hope that answers your question (Lloyd MacKenzie)
Your fundamental assertion is correct. However "inputs" can be interpreted fairly broadly:
- Sort order has changed based on the JVM (one of the 1.4 versions did wonky things)
- Sort order can change when you generate with new RIM vocabulary and formal naming input files
- Sort order can change when you manipulate a Visio file, as changing the z-order of shapes within the diagram can affect class names, which in turn affects sort order. Adding or removing classes can do the same.
- Changes to the tools, reflecting updated methodology or fixes to bugs can also change names and thus sort order
However, if all of those variables remain constant, the sort order will remain the same from generation to generation. Hope that answers your question (Lloyd MacKenzie)
Subscribe to:
Posts (Atom)