{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/583bc1d66a8d4ded9f0b90516ba27a38\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1440,"width":1920,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1440,"thumbnail_width":1920,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/583bc1d66a8d4ded9f0b90516ba27a38-d0016300d1668f65.jpg","duration":488.512,"title":"How competency outcomes, learning records and requirements relate","description":"This Loom demonstrates how competency outcomes recorded in AusMed Competency drive or do not drive compliance requirement completion in the manager portal. For Benjamin on 18 May, a competent outcome for Manage and Prevent Skin Tears with a linked requirement due 30 May is automatically marked Completed because the assessment date falls within the compliance timeline; a learning record is created and includes the competency outcome as evidence. If there is a competent outcome with no linked compliance requirement, a learning record is still created but shows zero requirements. If a not yet competent outcome is recorded for Tim, no learning record or compliance completion occurs because the requirement is not met."}