[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M714XSYTY9G58JWAB5GDF8XF":3,"skill-same:01M714XSYTY9G58JWAB5GDF8XF":66},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M714XSYTY9G58JWAB5GDF8XF","medical-laboratory-science-feedback-complaints",null,"Collect feedback from patients whose diagnosis depends on laboratory results, via clinical teams and handle complaints fairly and visibly.\nTRIGGERS - Use when a biomedical scientist needs a feedback & complaints handling for patients whose diagnosis depends on laboratory results, via clinical teams in a hospital pathology laboratory.","lionelsimai\u002Fclaude-skills-collection","lionelsimai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260158848?v=4","01M6CHZPS8G9TSB113TT0BBM6E","Lionel ","01M6CHZPXGW2SPE3BHQTGJ0S8J",38,"MIT","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fmedical-laboratory-science-feedback-complaints\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"feedback","medical laboratory science feedback complaints","medical","science","biomedical","for","collect","pathology","triggers","teams","clinical","use","when","results","via","diagnosis","2026-11-10 10:12:30",false,"---\nname: medical-laboratory-science-feedback-complaints\ndescription: |\n  Collect feedback from patients whose diagnosis depends on laboratory results, via clinical teams and handle complaints fairly and visibly.\n  TRIGGERS - Use when a biomedical scientist needs a feedback & complaints handling for patients whose diagnosis depends on laboratory results, via clinical teams in a hospital pathology laboratory.\ncategory: Medical Laboratory Science\nlicense: MIT\nversion: 1.0\n---\n# Feedback & Complaints Handling — Medical Laboratory Science\n\nCollect feedback from patients whose diagnosis depends on laboratory results, via clinical teams and handle complaints fairly and visibly. The deliverable is a feedback and complaints process with response standards and learning log.\nThis skill is written for a biomedical scientist working with patients whose diagnosis depends on laboratory results, via clinical teams in a hospital pathology laboratory.\n\n## When to use\n- You are a biomedical scientist preparing, delivering or reviewing this part of your work in a hospital pathology laboratory.\n- You need a defensible, repeatable approach that produces a feedback and complaints process with response standards and learning log.\n- A colleague, auditor or client asks how this was done and what evidence supports it.\n\n## Key Concepts\n| Term | Meaning |\n|------|---------|\n| Quality control | checks that a test system is performing correctly |\n| Turnaround time | time from sample receipt to result |\n| Haemolysis | breakdown of red blood cells that can spoil a sample |\n\n## Workflow\n1. **Step 1** - Invite feedback routinely — not only when things go wrong — and make it easy to give in a hospital pathology laboratory\n2. **Step 2** - Acknowledge complaints quickly, thank the person, and explain the process and timeframe honestly\n3. **Step 3** - Investigate from evidence in test requests; separate the facts from the feelings, and respect both\n4. **Step 4** - Respond with findings, an apology where warranted, and concrete remedies or explanations\n5. **Step 5** - Log themes and feed them into quality work — repeated complaints about sample mislabelling are an early-warning system, not a nuisance\n\n## Profession-Specific Components\n| Component | Details for Medical Laboratory Science |\n|-----------|-------------------------------|\n| Core documentation | test requests; analyser maintenance logs; quality control records; result reports |\n| Core tools & equipment | laboratory analysers; centrifuges; microscopes; laboratory information systems |\n| People involved | patients whose diagnosis depends on laboratory results, via clinical teams; the biomedical scientist; colleagues and other services in a hospital pathology laboratory |\n| Primary record | test requests — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in a hospital pathology laboratory] | **Objective:** [What this must achieve] | **Audience:** [patients whose diagnosis depends on laboratory results, via clinical teams and other stakeholders]\n\nThe finished output is a feedback and complaints process with response standards and learning log, structured as:\n1. Summary of position and evidence\n2. Detail, following the workflow above\n3. Decisions, actions, owners and dates\n4. Review point and escalation route\n\n### Action Plan\n1. **Immediate:** Confirm scope, consent and the evidence available in test requests.\n2. **Short-term:** Complete the workflow steps and record outcomes against result turnaround time.\n3. **Medium-term:** Review results, close actions, and update local procedures in a hospital pathology laboratory.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| result turnaround time | Agree a local target and track the trend | Measured from test requests and reviewed on a set cycle |\n| analyser downtime | Agree a local target and track the trend | Measured from test requests and reviewed on a set cycle |\n| quality control pass rate | Agree a local target and track the trend | Measured from test requests and reviewed on a set cycle |\n| critical result communication | Agree a local target and track the trend | Measured from test requests and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: sample mislabelling.\n- Never let this happen: delayed critical results.\n- Never let this happen: analyser faults unnoticed.\n- Work only within the competence and authority of a biomedical scientist; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to a hospital pathology laboratory's rules.\n- Verify names, dates, figures and measurements twice before anything is issued or signed off.\n- Use only real, verified information from the case in hand — never invent results, credentials or evidence.\n\n## Example (illustrative)\nA biomedical scientist in a hospital pathology laboratory applies this workflow for patients whose diagnosis depends on laboratory results, via clinical teams: they open\ntest requests, work through the five steps using laboratory analysers, and close by recording\nthe outcome against result turnaround time and agreeing the next review date. (Illustrative example only —\nreplace with the real details of the case in hand.)\n","# Feedback & Complaints Handling — Medical Laboratory Science\n\nCollect feedback from patients whose diagnosis depends on laboratory results, via clinical teams and handle complaints fairly and visibly. The deliverable is a feedback and complaints process with response standards and learning log.\nThis skill is written for a biomedical scientist working with patients whose diagnosis depends on laboratory results, via clinical teams in a hospital pathology laboratory.\n\n## When to use\n- You are a biomedical scientist preparing, delivering or reviewing this part of your work in a hospital pathology laboratory.\n- You need a defensible, repeatable approach that produces a feedback and complaints process with response standards and learning log.\n- A colleague, auditor or client asks how this was done and what evidence supports it.\n\n## Key Concepts\n| Term | Meaning |\n|------|---------|\n| Quality control | checks that a test system is performing correctly |\n| Turnaround time | time from sample receipt to result |\n| Haemolysis | breakdown of red blood cells that can spoil a sample |\n\n## Workflow\n1. **Step 1** - Invite feedback routinely — not only when things go wrong — and make it easy to give in a hospital pathology laboratory\n2. **Step 2** - Acknowledge complaints quickly, thank the person, and explain the process and timeframe honestly\n3. **Step 3** - Investigate from evidence in test requests; separate the facts from the feelings, and respect both\n4. **Step 4** - Respond with findings, an apology where warranted, and concrete remedies or explanations\n5. **Step 5** - Log themes and feed them into quality work — repeated complaints about sample mislabelling are an early-warning system, not a nuisance\n\n## Profession-Specific Components\n| Component | Details for Medical Laboratory Science |\n|-----------|-------------------------------|\n| Core documentation | test requests; analyser maintenance logs; quality control records; result reports |\n| Core tools & equipment | laboratory analysers; centrifuges; microscopes; laboratory information systems |\n| People involved | patients whose diagnosis depends on laboratory results, via clinical teams; the biomedical scientist; colleagues and other services in a hospital pathology laboratory |\n| Primary record | test requests — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in a hospital pathology laboratory] | **Objective:** [What this must achieve] | **Audience:** [patients whose diagnosis depends on laboratory results, via clinical teams and other stakeholders]\n\nThe finished output is a feedback and complaints process with response standards and learning log, structured as:\n1. Summary of position and evidence\n2. Detail, following the workflow above\n3. Decisions, actions, owners and dates\n4. Review point and escalation route\n\n### Action Plan\n1. **Immediate:** Confirm scope, consent and the evidence available in test requests.\n2. **Short-term:** Complete the workflow steps and record outcomes against result turnaround time.\n3. **Medium-term:** Review results, close actions, and update local procedures in a hospital pathology laboratory.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| result turnaround time | Agree a local target and track the trend | Measured from test requests and reviewed on a set cycle |\n| analyser downtime | Agree a local target and track the trend | Measured from test requests and reviewed on a set cycle |\n| quality control pass rate | Agree a local target and track the trend | Measured from test requests and reviewed on a set cycle |\n| critical result communication | Agree a local target and track the trend | Measured from test requests and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: sample mislabelling.\n- Never let this happen: delayed critical results.\n- Never let this happen: analyser faults unnoticed.\n- Work only within the competence and authority of a biomedical scientist; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to a hospital pathology laboratory's rules.\n- Verify names, dates, figures and measurements twice before anything is issued or signed off.\n- Use only real, verified information from the case in hand — never invent results, credentials or evidence.\n\n## Example (illustrative)\nA biomedical scientist in a hospital pathology laboratory applies this workflow for patients whose diagnosis depends on laboratory results, via clinical teams: they open\ntest requests, work through the five steps using laboratory analysers, and close by recording\nthe outcome against result turnaround time and agreeing the next review date. (Illustrative example only —\nreplace with the real details of the case in hand.)\n",{"name":5,"license":15,"version":40,"category":41,"description":42},1,"Medical Laboratory Science","Collect feedback from patients whose diagnosis depends on laboratory results, via clinical teams and handle complaints fairly and visibly.\nTRIGGERS - Use when a biomedical scientist needs a feedback & complaints handling for patients whose diagnosis depends on laboratory results, via clinical teams in a hospital pathology laboratory.\n","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Fmedical-laboratory-science-feedback-complaints",5,"https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection","https:\u002F\u002Fgithub.com\u002Flionelsimai","www.theaicapitol.com","Founder at The AI Capitol | I help founders turn AI into 10X revenue through systems, not tools. Ex-Apple • Ex-TikTok 👉 http:\u002F\u002Flionelsim.substack.com","2026-11-09 07:48:48",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add lionelsimai\u002Fclaude-skills-collection --skill medical-laboratory-science-feedback-complaints",{"tool":58,"command":59},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill medical-laboratory-science-feedback-complaints",{"tool":61,"command":62},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill medical-laboratory-science-feedback-complaints","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fmedical-laboratory-science-feedback-complaints\u002FSKILL.md",true,[],[67,88,101,114,131,145],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":35},"01M71E7TB5HAR0K6EXB80YXBT7","youth-work-troubleshooting-guide","Diagnose and resolve common problems a youth worker meets in youth centres, schools and outreach settings.\nTRIGGERS - Use when a youth worker needs a troubleshooting & problem solving for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-troubleshooting-guide\u002FSKILL.md",[],[74,75,76,77,78,79,24,80,81,82,31,83,30,84,27,85,86,87],"youth work troubleshooting guide","work","troubleshooting","troubleshooting guide","guide","problem solving","outreach","settings","common","people","worker","diagnose","problem","communities",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":35},"01M71E7R3YHK4RAQVCRPB4CTXN","youth-work-tools-equipment-checklist","Select, check and maintain the tools and equipment a youth worker relies on.\nTRIGGERS - Use when a youth worker needs a tools & equipment checklist for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-tools-equipment-checklist\u002FSKILL.md",[],[95,75,96,97,31,83,30,98,84,27,99,24,87,100,80,81],"youth work tools equipment checklist","checklist","Tools","maintain","select","check",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":35},"01M71E7NX1BMFEFBH01KCRJDEP","youth-work-supplies-procurement","Specify, source and manage the supplies and materials used in youth centres, schools and outreach settings.\nTRIGGERS - Use when a youth worker needs a supplies & procurement for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-supplies-procurement\u002FSKILL.md",[],[108,109,75,110,111,80,81,83,30,84,27,112,113,24,87,31],"procurement","youth work supplies procurement","materials","source","specify","manage",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":125,"publishedAt":35},"01M71E7JVFP6P96GAT2VT9JY0D","youth-work-stakeholder-presentation","Present youth worker findings and proposals to decision-makers and stakeholders.\nTRIGGERS - Use when a youth worker needs a stakeholder presentation for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-stakeholder-presentation\u002FSKILL.md",[120],{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",[126,75,127,128,24,129,87,27,130,80,81,31,83,30,84],"youth work stakeholder presentation","presentation","decision","proposals","present",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":35},"01M71E7GE5VA1RG4XEM2GAZRFY","youth-work-session-delivery","Prepare for and deliver a professional session or appointment for young people and their communities in youth centres, schools and outreach settings.\nTRIGGERS - Use when a youth worker needs a session delivery guide for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-session-delivery\u002FSKILL.md",[],[138,139,140,75,141,81,78,142,80,31,83,30,84,27,24,143,144,87],"delivery","work session","session","youth work session delivery","prepare","professional","deliver",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":154,"publishedAt":35},"01M71E7DQSMY2ZW1BF3A1Z0VJM","youth-work-service-plan","Design a realistic, measurable service plan for young people and their communities as a youth worker.\nTRIGGERS - Use when a youth worker needs a service plan design for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-service-plan\u002FSKILL.md",[151],{"categoryNo":152,"categoryName":153,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000015","视觉设计",[75,155,156,157,24,27,84,158,159,87,81,80,83,30,31],"service","plan","youth work service plan","design","as"]