2RIM2 - 2MVG2: Offline Viewer for Semantic Model RIMVG2_1.6.a (versie 2011-05-02 00:00:00; nl - fr). Alle Modellen

Item: [*PLAN] Regels in verband met plannen

Onderstaande activiteiten, resultaten, toestanden en rekenregels hebben een betekenis bij de berekening van de score van bovenstaand MVGII-item.

Activiteiten

Act CodeOmschrijving

Resultaten

Een resultaat wordt steeds gerapporteerd in de context van een omsluitende activiteit.
Deze activiteit heeft dan de betekenis van rapportering van het resultaat.
CodeOmschrijving

Toestanden

Een toestand wordt steeds gerapporteerd in de context van een omsluitende activiteit.
Deze activiteit heeft dan de betekenis van rapportering van de toestand.
CodeOmschrijving

Rekenregels

Volgende rekenregels zijn van toepassing bij de automatische berekening van de score voor dit item :
(1) regels uit de codeerhandleiding.
(2) de hierna vermelde regels, die rekening houden met de specifieke kenmerken van een elektronisch patiëntendossier.

Regel: [PLAN.R1] Plan conditions to be verified
Acts that should belong to a Plan are qualified for scoring, if the containing Plan satisfies the specific conditions mentioned. In case of an individual plan, these conditions can be verified automatically by the information foreseen by the conceptual model. In case of a standard plan, it should be verified (once for every standard plan) manually that these conditions hold.

Regel: [PLAN.R2] Initial evaluation of plan (problem determination)
Whenever Result *000.F24 should be present, only Acts that occur on the day of the first occurrence of a Result *000.F24 or after the first occurrence of a Result *000.F24 qualify for scoring.
This rules means that only Acts that took place on the same day or after the problem for the plan was determined, qualify for scoring.
Note: initially this rule specified that the all acts before the first occurrence of *000.F23 did not qualify for scoring. Pilots indicated that in typical cases the first education activity was entered in the system, then the observation was entered. This usage scenario would discard these activities incorrectly from scoring. Hence, the refinement of the rule.

Regel: [PLAN.R4] Plan reevaluation (mandatory reevaluation period)
Whenever is indicated that a Plan should be re-evaluated every x days (partly indicated by the requirement for Result *000.F22), only Acts that belong to the Plan and that fall within this period of x days, qualify for scoring.
This x day period is calculated as the period of x days, that follows the ValidAtOrFrom of a Result *000.F22 r which Act r.LastlyReportedDuring belongs to the Plan. This means that all Acts that follow a *000.F22 within an x day period qualify for scoring. Acts that occur outside such a period do not satisfy the reavaluation requirement and qualify not for scoring. The initial evaluations of the Plan *000.F24 and/or *000.F23 (if any) are to be considered as a *000.F22. If no *000.F24, nor a *000.F23 exists for the plan, it is assumed that an implicit *000.F22 exists that falls at the start of the Plan (Plan.From).
If the Plan is stopped before the x day period expires, or if the patient leaves the ward before the x day period expires, no last evaluation is required. We do not require that is checked that a last evaluation is planned for practical reasons.

Regel: [PLAN.R5] Plan reevaluation (optional reevaluation period)
If re-evaluation is required (indicated by the requirement for Result *000.F22), but it is not mentioned within what period the evaluation should take place, we require that at least one Result *000.F22 (whose Act result.LastlyReportedDuring belongs to the Plan) has been planned in the future.
Implementation note: this rule may turn out to be complex to realize in practical systems. Therefore, is it OK if practical systems do not take into account rule PLAN.R5.

Regel: [PLAN.R6] Plan reevaluation (reevaluation within 1 day)
If re-evaluation is required within 1 day, it means that re-evaluation is required during the same registration time span. If the patient is transferred, this means that re-evaluation may need to occur within a period shorter than 24hrs
This rule is introduced to cope with the specific restriction mentioned with item V700.

Regel: [PLAN.R9] Boundary conditions
If the plan has been started before the MNDS registration period by more than the number of days as indicated by the re-evaluation period (indicated by the requirement for Result *000.F20), it is assumed that (1) the initial evaluation has taken place and (2) the re-evaluation is OK until this reference moment, defined as the start of the MNDS registration period minus the re-evaluation period.
This rule simply means that we not consider information that may be a lot older that the information generated during (and around) the MNDS registration period. It would be technically too complex to take this older information into account. It may also be questionsome of e.g. a "very old" initial evaluation is meaningful.