[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69BEZPTQH6XF1025SGE3TRF":3,"skill-same:01M69BEZPTQH6XF1025SGE3TRF":49},{"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":21,"linkOnly":22,"markdownContent":23,"markdownBody":24,"frontMatter":25,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M69BEZPTQH6XF1025SGE3TRF","lookup-patient-history",null,"Load the synthetic patient chart and verbatim prior reports for EHR reporting. Use before measuring the selected current and prior images; this lookup does not perform segmentation or measurements.","microsoft\u002FLAB730-ignite-2026-healthcare-agents","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69BEN2JF8ERT1WJ3PE24FJ6",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FLAB730-ignite-2026-healthcare-agents\u002Fblob\u002Fmain\u002Fchapters\u002Fchapter3-knowledge-sources\u002Fanswer-key-improved-compliance\u002F.github\u002Fskills\u002Flookup-patient-history\u002FSKILL.md",[],[19,20],"lookup patient history","image","2026-11-10 10:12:30",false,"---\nname: lookup-patient-history\ndescription: Load the synthetic patient chart and verbatim prior reports for EHR reporting. Use before measuring the selected current and prior images; this lookup does not perform segmentation or measurements.\nargument-hint: |\n  - image_path: required path to the current image, named `{patient_id}_{study_index}.nii.gz`.\n  - patient_id: optional override if the filename does not follow that convention.\n---\n\n# Lookup Patient History\n\nRead `data\u002Fpatients\u002F{patient_id}.json` relative to the workspace root and inline its referenced prior reports. Return data, not a clinical interpretation.\n\n## Scope and handoff\n\n- File reads and file searches are permitted. Do not call segmentation or measurement tools **during this lookup step**. This restriction ends when the lookup returns; the parent report workflow must then perform its measurement steps.\n- When used by a report skill, return the record internally and resume the parent workflow. Do not treat this helper's completion as the final chat response.\n- When explicitly requested on its own, return only the patient-record block.\n- Keep the block concise, but preserve all study dates, paths, treatment and procedure details, LAST RECORD ENTRY NOTE, and full prior report text. Do not truncate these to meet a word budget.\n\n## How to use\n\n1. **Resolve the identifiers.**\n   - Use a supplied `patient_id`; otherwise infer it by removing `.nii.gz` and the trailing `_NNN` from the filename, for example `SYN0056_006.nii.gz` gives `SYN0056`.\n   - Retain the current `study_id` to identify the matching pending order. If the filename does not identify the patient or study and the caller has not supplied it, request clarification rather than guessing.\n2. **Read the chart.**\n   - Read `data\u002Fpatients\u002F{patient_id}.json`.\n   - If the file does not exist, return `PATIENT RECORD: Not on file for patient_id {patient_id}.` to the parent, which must still measure the current image. This ends only the lookup.\n   - If the file exists but cannot be read or parsed, report the specific error and stop the workflow; do not mislabel it as a missing chart.\n3. **Inline prior reports.**\n   - For each non-null `report_path` in `imaging_studies`, read the report and include its full text verbatim.\n   - Resolve paths from the workspace root. If a report is not there, look for the same filename in the neighboring reports directory; do not substitute a different study.\n   - If a report remains missing, include `[report file missing: {path}]` and continue with the other chart data. The parent must disclose that missing source.\n4. **Return the block below**, preserving the section headers. Mark the pending order that matches the current study.\n\n## Output format\n\n```text\nPATIENT RECORD - {patient_id}, as of {record_as_of}\n\nDEMOGRAPHICS: {demographics.age}{demographics.sex}.\n\nDIAGNOSIS: {diagnosis.primary} {diagnosis.molecular} Established {diagnosis.established}\n\nPRESENTATION: {presentation.date}. {presentation.presenting_complaint}\nHPI: {presentation.hpi_summary}\n\nACTIVE PROBLEMS:\n- {each item from active_problems}\n\nPAST MEDICAL HISTORY:\n- {each item from past_medical_history}\n\nALLERGIES: {allergies.notes}\n\nCURRENT MEDICATIONS:\n- {name} {dose} - {indication}\n  (one line per item from medications)\n\nPROCEDURES:\n- {date}: {procedure}. {result} Complications: {complications}\n  (one line per item from procedures)\n\nTREATMENTS:\n- {start} -> {end, or \"ongoing\" if null}: {treatment}. {notes}\n  (one line per item from treatments)\n\nEXPECTED POST-TREATMENT FINDINGS (per record):\n- {each item from expected_post_treatment_findings}\n\nIMAGING HISTORY (oldest to newest):\n- {study_id} - {date}, {exam}. {summary} Image: {image_path, or \"not retained\"}\n  (one line per imaging_studies entry)\n\nPRIOR REPORTS:\n=== {study_id} ({date}) ===\n{full report text loaded from report_path, or the missing-file notice}\n===\n  (one block per imaging_studies entry with a report_path)\n\nPENDING ORDERS:\n- {study_id} - {date}, {exam}. Indication: {indication} Status: {status}\n  (one line per pending_orders entry; mark the matching study with \"\u003C- current image\")\n\nLAST RECORD ENTRY NOTE: {last_record_entry_note}\n```\n\n## Critical rules\n\n- Do not invent fields. Render missing, empty, or null fields as `(none)` unless the format specifies otherwise.\n- Do not summarize the prior report or substitute its measurements for a current image measurement.\n- Do not interpret findings or decide which lesion is new. The parent report skill combines the record with imaging evidence.\n- Always include LAST RECORD ENTRY NOTE so the report writer knows where the record ends.\n","# Lookup Patient History\n\nRead `data\u002Fpatients\u002F{patient_id}.json` relative to the workspace root and inline its referenced prior reports. Return data, not a clinical interpretation.\n\n## Scope and handoff\n\n- File reads and file searches are permitted. Do not call segmentation or measurement tools **during this lookup step**. This restriction ends when the lookup returns; the parent report workflow must then perform its measurement steps.\n- When used by a report skill, return the record internally and resume the parent workflow. Do not treat this helper's completion as the final chat response.\n- When explicitly requested on its own, return only the patient-record block.\n- Keep the block concise, but preserve all study dates, paths, treatment and procedure details, LAST RECORD ENTRY NOTE, and full prior report text. Do not truncate these to meet a word budget.\n\n## How to use\n\n1. **Resolve the identifiers.**\n   - Use a supplied `patient_id`; otherwise infer it by removing `.nii.gz` and the trailing `_NNN` from the filename, for example `SYN0056_006.nii.gz` gives `SYN0056`.\n   - Retain the current `study_id` to identify the matching pending order. If the filename does not identify the patient or study and the caller has not supplied it, request clarification rather than guessing.\n2. **Read the chart.**\n   - Read `data\u002Fpatients\u002F{patient_id}.json`.\n   - If the file does not exist, return `PATIENT RECORD: Not on file for patient_id {patient_id}.` to the parent, which must still measure the current image. This ends only the lookup.\n   - If the file exists but cannot be read or parsed, report the specific error and stop the workflow; do not mislabel it as a missing chart.\n3. **Inline prior reports.**\n   - For each non-null `report_path` in `imaging_studies`, read the report and include its full text verbatim.\n   - Resolve paths from the workspace root. If a report is not there, look for the same filename in the neighboring reports directory; do not substitute a different study.\n   - If a report remains missing, include `[report file missing: {path}]` and continue with the other chart data. The parent must disclose that missing source.\n4. **Return the block below**, preserving the section headers. Mark the pending order that matches the current study.\n\n## Output format\n\n```text\nPATIENT RECORD - {patient_id}, as of {record_as_of}\n\nDEMOGRAPHICS: {demographics.age}{demographics.sex}.\n\nDIAGNOSIS: {diagnosis.primary} {diagnosis.molecular} Established {diagnosis.established}\n\nPRESENTATION: {presentation.date}. {presentation.presenting_complaint}\nHPI: {presentation.hpi_summary}\n\nACTIVE PROBLEMS:\n- {each item from active_problems}\n\nPAST MEDICAL HISTORY:\n- {each item from past_medical_history}\n\nALLERGIES: {allergies.notes}\n\nCURRENT MEDICATIONS:\n- {name} {dose} - {indication}\n  (one line per item from medications)\n\nPROCEDURES:\n- {date}: {procedure}. {result} Complications: {complications}\n  (one line per item from procedures)\n\nTREATMENTS:\n- {start} -> {end, or \"ongoing\" if null}: {treatment}. {notes}\n  (one line per item from treatments)\n\nEXPECTED POST-TREATMENT FINDINGS (per record):\n- {each item from expected_post_treatment_findings}\n\nIMAGING HISTORY (oldest to newest):\n- {study_id} - {date}, {exam}. {summary} Image: {image_path, or \"not retained\"}\n  (one line per imaging_studies entry)\n\nPRIOR REPORTS:\n=== {study_id} ({date}) ===\n{full report text loaded from report_path, or the missing-file notice}\n===\n  (one block per imaging_studies entry with a report_path)\n\nPENDING ORDERS:\n- {study_id} - {date}, {exam}. Indication: {indication} Status: {status}\n  (one line per pending_orders entry; mark the matching study with \"\u003C- current image\")\n\nLAST RECORD ENTRY NOTE: {last_record_entry_note}\n```\n\n## Critical rules\n\n- Do not invent fields. Render missing, empty, or null fields as `(none)` unless the format specifies otherwise.\n- Do not summarize the prior report or substitute its measurements for a current image measurement.\n- Do not interpret findings or decide which lesion is new. The parent report skill combines the record with imaging evidence.\n- Always include LAST RECORD ENTRY NOTE so the report writer knows where the record ends.\n",{"name":5,"description":7,"argument-hint":26},"- image_path: required path to the current image, named `{patient_id}_{study_index}.nii.gz`.\n- patient_id: optional override if the filename does not follow that convention.","main","30a1709ed305ae7f43775c5cb86f9006a03720f8","chapters\u002Fchapter3-knowledge-sources\u002Fanswer-key-improved-compliance\u002F.github\u002Fskills\u002Flookup-patient-history","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FLAB730-ignite-2026-healthcare-agents","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-10-30 02:36:25",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add microsoft\u002FLAB730-ignite-2026-healthcare-agents --skill lookup-patient-history",{"tool":41,"command":42},"bunx","bunx skills add microsoft\u002FLAB730-ignite-2026-healthcare-agents --skill lookup-patient-history",{"tool":44,"command":45},"pnpm","pnpm dlx skills add microsoft\u002FLAB730-ignite-2026-healthcare-agents --skill lookup-patient-history","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FLAB730-ignite-2026-healthcare-agents\u002Fblob\u002Fmain\u002Fchapters\u002Fchapter3-knowledge-sources\u002Fanswer-key-improved-compliance\u002F.github\u002Fskills\u002Flookup-patient-history\u002FSKILL.md",true,[],[50,69,76,84,93,103],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":66,"publishedAt":21},"01M69BF6AY2E31N5HC0HM7S7YK","write-report-with-ehr","Write a context-aware brain MRI follow-up report from the patient's record, tool-computed lesion measurements, and change from the most recent prior image. Use when asked for a report that uses the patient's history, chart, or EHR.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FLAB730-ignite-2026-healthcare-agents\u002Fblob\u002Fmain\u002Fchapters\u002Fchapter3-knowledge-sources\u002Fanswer-key\u002F.github\u002Fskills\u002Fwrite-report-with-ehr\u002FSKILL.md",[56,61],{"categoryNo":57,"categoryName":58,"taxonomyType":59,"taxonomyTypeDesc":60},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":62,"categoryName":63,"taxonomyType":64,"taxonomyTypeDesc":65},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[67,20,68],"write report with ehr","change",{"skillNo":70,"name":5,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":75,"publishedAt":21},"01M69BF4TR0Z36MNW16DZVZ9YE","Load a synthetic patient EHR record (demographics, diagnosis, treatments, medications, expected post-treatment findings, prior imaging studies and reports, pending orders) for a given brain MRI image. Invoke as the first step of any context-aware reporting flow that needs patient history. No model calls.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FLAB730-ignite-2026-healthcare-agents\u002Fblob\u002Fmain\u002Fchapters\u002Fchapter3-knowledge-sources\u002Fanswer-key\u002F.github\u002Fskills\u002Flookup-patient-history\u002FSKILL.md",[74],{"categoryNo":57,"categoryName":58,"taxonomyType":59,"taxonomyTypeDesc":60},[19,20],{"skillNo":77,"name":52,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":82,"publishedAt":21},"01M69BF2XGK9Z7FCTPSP67TP2C","Write a context-aware brain MRI report using the patient chart and mandatory tool-computed linear and volumetric measurements. Use for EHR reporting with Radiology Assistant (EHR).","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FLAB730-ignite-2026-healthcare-agents\u002Fblob\u002Fmain\u002Fchapters\u002Fchapter3-knowledge-sources\u002Fanswer-key-improved-compliance\u002F.github\u002Fskills\u002Fwrite-report-with-ehr\u002FSKILL.md",[81],{"categoryNo":62,"categoryName":63,"taxonomyType":64,"taxonomyTypeDesc":65},[20,83],"assistant",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":21},"01M69BF14X7RFX39K47N9DAXD9","write-imaging-factsheet-ehr","Produce an EHR imaging factsheet with mandatory segmentation, cleanup, linear dimensions, and volumes. Use when write-report-with-ehr requests imaging evidence or when explicitly asked for this factsheet.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FLAB730-ignite-2026-healthcare-agents\u002Fblob\u002Fmain\u002Fchapters\u002Fchapter3-knowledge-sources\u002Fanswer-key-improved-compliance\u002F.github\u002Fskills\u002Fwrite-imaging-factsheet-ehr\u002FSKILL.md",[],[91,20,92],"write imaging factsheet","cleanup",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":101,"publishedAt":21},"01M69BEY7Q35J8DCZWZYPCN92M","write-report-measured","Write a brain MRI report with tool-computed lesion measurements and, when a prior image is supplied, change from that prior. Use for brain MRI reports when the medimageparse `segment`, `clean_segmentation`, and `describe_lesions` tools are available.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FLAB730-ignite-2026-healthcare-agents\u002Fblob\u002Fmain\u002Fchapters\u002Fchapter2-foundation-models\u002Fstarter\u002F.github\u002Fskills\u002Fwrite-report-measured\u002FSKILL.md",[99,100],{"categoryNo":57,"categoryName":58,"taxonomyType":59,"taxonomyTypeDesc":60},{"categoryNo":62,"categoryName":63,"taxonomyType":64,"taxonomyTypeDesc":65},[102,20,68],"write report measured",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":110,"publishedAt":21},"01M69BEWRG2WTN2V1E6MCVB78V","write-imaging-factsheet","Generate a lesion-only imaging factsheet from a post-contrast T1 MRI, optionally comparing a prior image. Use when asked for a lesion factsheet or a descriptor-based imaging summary.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FLAB730-ignite-2026-healthcare-agents\u002Fblob\u002Fmain\u002Fchapters\u002Fchapter2-foundation-models\u002Fstarter\u002F.github\u002Fskills\u002Fwrite-imaging-factsheet\u002FSKILL.md",[109],{"categoryNo":57,"categoryName":58,"taxonomyType":59,"taxonomyTypeDesc":60},[91,20,111],"generate"]