Problem Based Learning Maastricht Seven Step Process

Named Maastricht seven-jump process coverage/order audit, not clinical differential diagnosis generation. Audit exact supplied observed stages against the independently verified declared order, not pedagogical/performance efficacy. Caller independently verifies learner/context/evidence and reference edition; not causal learning efficacy, disability eligibility or educational certification.

Description

Problem-based learning organizes inquiry around a problem and a declared sequence of discussion and independent study.

Problem-based learning organizes inquiry around a problem and a declared sequence of discussion and independent study.1

This audit compares observed stages with your declared order and reports coverage and local order inversions.

When to use Problem Based Learning Maastricht Seven Step Process

Use this tool to review missing stages and local order inversions. Establish the learning task, observed evidence and applicable framework or policy edition.

How to use Problem Based Learning Maastricht Seven Step Process and understand its results

  1. Establish the learning task, observed evidence and applicable framework or policy edition.
  2. Enter callerObservedMaastrichtStageIds, callerStageDeclaredOrder, using the field meanings and rules below, then run the tool.
  3. Read missingDeclaredStageIds, orderInversionIndices. Inspect nested result fields where present, and review unknown records separately from known matches.
  4. Correct any reported input issue and run again. Before using a successful result, check the stated units, signs, reference scope and observation coverage.
Input fieldMeaningValue typeRequirement
callerObservedMaastrichtStageIdsCaller observed maastricht stage idslist of stringRequired
callerStageDeclaredOrderCaller stage declared orderlist of stringRequired

Require a nonempty unique nonblank declared stage list. An observed list can be empty; otherwise it must also be unique and nonblank. Every observed stage must belong to the declared list. Return declared stages absent from observations, in declared order, and zero-based observed positions whose declared rank is lower than the immediately previous observed rank. This is a local adjacent inversion check, not a count of all inverted pairs. Exact strings are matched without normalization.

missing=declared−observed; inversions={i≥1:declaredRank(observed_i)<declaredRank(observed_(i−1))}

Use the matching field units and the exact boundary, ordering and reference rules above.

Output fieldMeaningValue type
missingDeclaredStageIdsMissing declared stage idslist of string
orderInversionIndicesOrder inversion indices; zero-based positions in the relevant supplied record or adjacent-pair listlist of number
json
{
  "input": {
    "callerObservedMaastrichtStageIds": [
      "clarify-terms",
      "synthesize-discuss"
    ],
    "callerStageDeclaredOrder": [
      "clarify-terms",
      "define-problem",
      "brainstorm",
      "structure-explanations",
      "formulate-learning-objectives",
      "self-study",
      "synthesize-discuss"
    ]
  },
  "output": {
    "missingDeclaredStageIds": [
      "define-problem",
      "brainstorm",
      "structure-explanations",
      "formulate-learning-objectives",
      "self-study"
    ],
    "orderInversionIndices": []
  }
}

Limitations and assumptions

The declared sequence and its source edition are supplied inputs. Coverage does not measure mastery, consent, teaching quality or learning effect. Observed stages must be unique, so record separate cycles separately when the activity revisits a stage.

Missing required fields, unknown fields, wrong types and violated rules return input issues. Numeric values and outputs must be finite. Lists and matrices must be dense, without missing cells. Numeric lists allow at most 10000 entries; ordinary string lists allow at most 128 strings of 128 UTF-16 units each; numeric matrices allow at most 128 rows and 128 columns, subject to narrower requirements above.

Alternative or Complementary methods

For a related step, use Project Based Learning Gold Standard Design Elements Lookup: Project design can be reviewed against explicit evidence requirements for a particular PBL framework edition. For a complementary comparison, use Inquiry Cycle Kath Murdoch Phases Lookup: Inquiry cycles organize questioning, investigation and reflection, and classroom inquiry may revisit earlier phases.

References

  1. Problem Based Learning Maastricht Seven Step Process — tool.io

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies