Procedure Library

The procedure library gives a definition a controlled step reference. Each step has a name, code, effective dates, policy reference and owning organization. The team can agree when a step becomes active and when an older step stops applying. A definition then points to the specific step that governs its planned execution, which gives the reviewer a stable point of reference.

Source mappings connect incoming evidence fields to definition fields. Their version, effective date and transform rule should be reviewed with the procedure itself. For example, if a source calls a measure by a different name, the mapping shows the intended destination. The owner should make the mapping decision explicit before using that evidence for a review or execution. A later mapping revision can then be distinguished from the procedure revision.

• Controlled step. A named step belongs to an organization and carries its code, policy reference and effective dates.
• Definition link. The Procedure Owner selects that step on the definition so the reviewer sees the intended procedure context.
• Source mapping. A mapping records the source and target fields, types, version, effective date and transform rule for incoming evidence.

The Procedure Owner and Admin should agree how codes are assigned and who can retire a step. Set the effective period before the step is used in a new definition. Where evidence comes from another system, review each source mapping with an actual sample: compare the source field, target field and transform rule with the intended destination. A mapping record describes the rule; the team still needs to set up and test the connection that supplies the evidence. Keep the policy reference as a pointer to the controlled instruction your team uses.

Take a field inspection procedure with a revised instruction. Check the step code, organization and effective dates, then create a definition that references it. Have the Independent Reviewer follow the definition link to the step and compare the policy reference with the instruction being reviewed. If a source document calls an observation by a different name, inspect the mapping and check the transformed value against a known example. Change the mapping version when the source changes and rehearse that example again before using it in another execution.

• Controlled steps — Check the step code, organization and effective period.
• Source mappings — Inspect the source and target fields used for incoming evidence.

See the first handoff and the next decision.