All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Health Admin Capacity Completeness ReconciliationUse when the healthcare capacity and resource planning workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the capacity constraint brief with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; capacity assumptions are labeled and no operational assignment or patient prioritization is issued. Use configured search, ...Votes: 0GitHub stars: 2
- Health Admin Capacity Exception Triage QueueUse when the healthcare capacity and resource planning workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the capacity constraint brief with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; capacity assumptions are labeled and no operational assignment or patient prioritization is issued. Use configured search, fetch, read, ...Votes: 0GitHub stars: 2
- Health Admin Capacity Recovery Readiness DrillUse when the healthcare capacity and resource planning workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the capacity constraint brief with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; capacity assumptions are labeled and no operational assignment or patient prioritization is issued. Use configured search, fe...Votes: 0GitHub stars: 2
- Health Admin Capacity Scenario Sensitivity MatrixUse when the healthcare capacity and resource planning team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the capacity constraint brief with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; capacity assumptions are labeled and no operational assignment or patient prioritization is issued. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Health Admin Capacity Scope Intake GateUse when a new healthcare capacity and resource planning request needs a bounded work scope to produce a scoped intake card for the capacity constraint brief. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; capacity assumptions are labeled and no operational assignment or patient prioritization is issued. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, ...Votes: 0GitHub stars: 2
- Health Admin Capacity Source Provenance LedgerUse when a decision about healthcare capacity and resource planning depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the capacity constraint brief. Success means each material claim has a source, version/date, location, and confidence note; capacity assumptions are labeled and no operational assignment or patient prioritization is issued. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and a...Votes: 0GitHub stars: 2
- Health Admin Capacity Threshold Rule CheckUse when a healthcare capacity and resource planning decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the capacity constraint brief showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; capacity assumptions are labeled and no operational assignment or patient prioritization is issued. Use configured se...Votes: 0GitHub stars: 2
- Health Admin Care Coordination Approval Evidence PacketUse when a care-coordination handoff administration result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the care handoff checklist containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; administrative ownership is explicit without generating clinical advice or adding unstated facts. Use configured searc...Votes: 0GitHub stars: 2
- Health Admin Care Coordination Change Impact TraceUse when a version, rule, source, or stakeholder change may affect care-coordination handoff administration to produce a before/after change record and impact map for the care handoff checklist. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; administrative ownership is explicit without generating clinical advice or adding unstated facts. Use configured search, fetch, read, browser, test, and write capabiliti...Votes: 0GitHub stars: 2
- Health Admin Care Coordination Closeout Handoff LedgerUse when a care-coordination handoff administration work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the care handoff checklist with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; administrative ownership is explicit without generating clinical advice or adding unstated facts. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Health Admin Care Coordination Completeness ReconciliationUse when the care-coordination handoff administration workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the care handoff checklist with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; administrative ownership is explicit without generating clinical advice or adding unstated facts. Use configured search, fetch,...Votes: 0GitHub stars: 2
- Health Admin Care Coordination Exception Triage QueueUse when the care-coordination handoff administration workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the care handoff checklist with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; administrative ownership is explicit without generating clinical advice or adding unstated facts. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Health Admin Care Coordination Recovery Readiness DrillUse when the care-coordination handoff administration workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the care handoff checklist with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; administrative ownership is explicit without generating clinical advice or adding unstated facts. Use configured search, fetch, r...Votes: 0GitHub stars: 2
- Health Admin Care Coordination Scenario Sensitivity MatrixUse when the care-coordination handoff administration team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the care handoff checklist with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; administrative ownership is explicit without generating clinical advice or adding unstated facts. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Health Admin Care Coordination Scope Intake GateUse when a new care-coordination handoff administration request needs a bounded work scope to produce a scoped intake card for the care handoff checklist. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; administrative ownership is explicit without generating clinical advice or adding unstated facts. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit ...Votes: 0GitHub stars: 2
- Health Admin Care Coordination Source Provenance LedgerUse when a decision about care-coordination handoff administration depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the care handoff checklist. Success means each material claim has a source, version/date, location, and confidence note; administrative ownership is explicit without generating clinical advice or adding unstated facts. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authori...Votes: 0GitHub stars: 2
- Health Admin Care Coordination Threshold Rule CheckUse when a care-coordination handoff administration decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the care handoff checklist showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; administrative ownership is explicit without generating clinical advice or adding unstated facts. Use configured search, ...Votes: 0GitHub stars: 2
- Health Admin Health It Approval Evidence PacketUse when a health-information technology incident administration result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the health IT incident handoff containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; observed technical evidence is separated from clinical impact assumptions and the incident owner conf...Votes: 0GitHub stars: 2
- Health Admin Health It Change Impact TraceUse when a version, rule, source, or stakeholder change may affect health-information technology incident administration to produce a before/after change record and impact map for the health IT incident handoff. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; observed technical evidence is separated from clinical impact assumptions and the incident owner confirms closure. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Health Admin Health It Closeout Handoff LedgerUse when a health-information technology incident administration work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the health IT incident handoff with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; observed technical evidence is separated from clinical impact assumptions and the incident owner confirms closure. Use confi...Votes: 0GitHub stars: 2
- Health Admin Health It Completeness ReconciliationUse when the health-information technology incident administration workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the health IT incident handoff with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; observed technical evidence is separated from clinical impact assumptions and the incident owner confirms clos...Votes: 0GitHub stars: 2
- Health Admin Health It Exception Triage QueueUse when the health-information technology incident administration workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the health IT incident handoff with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; observed technical evidence is separated from clinical impact assumptions and the incident owner confirms closure. Use conf...Votes: 0GitHub stars: 2
- Health Admin Health It Recovery Readiness DrillUse when the health-information technology incident administration workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the health IT incident handoff with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; observed technical evidence is separated from clinical impact assumptions and the incident owner confirms closur...Votes: 0GitHub stars: 2
- Health Admin Health It Scenario Sensitivity MatrixUse when the health-information technology incident administration team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the health IT incident handoff with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; observed technical evidence is separated from clinical impact assumptions and the incident owner confirms closure. Use configured...Votes: 0GitHub stars: 2
- Health Admin Health It Scope Intake GateUse when a new health-information technology incident administration request needs a bounded work scope to produce a scoped intake card for the health IT incident handoff. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; observed technical evidence is separated from clinical impact assumptions and the incident owner confirms closure. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and a...Votes: 0GitHub stars: 2
- Health Admin Health It Source Provenance LedgerUse when a decision about health-information technology incident administration depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the health IT incident handoff. Success means each material claim has a source, version/date, location, and confidence note; observed technical evidence is separated from clinical impact assumptions and the incident owner confirms closure. Use configured search, fetch, read, browser, test, and write capabilit...Votes: 0GitHub stars: 2
- Health Admin Health It Threshold Rule CheckUse when a health-information technology incident administration decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the health IT incident handoff showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; observed technical evidence is separated from clinical impact assumptions and the incident owner confirm...Votes: 0GitHub stars: 2
- Health Admin Patient Access Approval Evidence PacketUse when a patient access and referral administration result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the access backlog handoff containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; each case has an accurate administrative status and clinical urgency is not inferred. Use configured search, fetch, ...Votes: 0GitHub stars: 2
- Health Admin Patient Access Change Impact TraceUse when a version, rule, source, or stakeholder change may affect patient access and referral administration to produce a before/after change record and impact map for the access backlog handoff. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each case has an accurate administrative status and clinical urgency is not inferred. Use configured search, fetch, read, browser, test, and write capabilities only wh...Votes: 0GitHub stars: 2
- Health Admin Patient Access Closeout Handoff LedgerUse when a patient access and referral administration work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the access backlog handoff with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; each case has an accurate administrative status and clinical urgency is not inferred. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Health Admin Patient Access Completeness ReconciliationUse when the patient access and referral administration workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the access backlog handoff with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; each case has an accurate administrative status and clinical urgency is not inferred. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Health Admin Patient Access Exception Triage QueueUse when the patient access and referral administration workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the access backlog handoff with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; each case has an accurate administrative status and clinical urgency is not inferred. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Health Admin Patient Access Recovery Readiness DrillUse when the patient access and referral administration workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the access backlog handoff with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; each case has an accurate administrative status and clinical urgency is not inferred. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Health Admin Patient Access Scenario Sensitivity MatrixUse when the patient access and referral administration team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the access backlog handoff with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each case has an accurate administrative status and clinical urgency is not inferred. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Health Admin Patient Access Scope Intake GateUse when a new patient access and referral administration request needs a bounded work scope to produce a scoped intake card for the access backlog handoff. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each case has an accurate administrative status and clinical urgency is not inferred. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement...Votes: 0GitHub stars: 2
- Health Admin Patient Access Source Provenance LedgerUse when a decision about patient access and referral administration depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the access backlog handoff. Success means each material claim has a source, version/date, location, and confidence note; each case has an accurate administrative status and clinical urgency is not inferred. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Recor...Votes: 0GitHub stars: 2
- Health Admin Patient Access Threshold Rule CheckUse when a patient access and referral administration decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the access backlog handoff showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; each case has an accurate administrative status and clinical urgency is not inferred. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Health Admin Payer Contract Approval Evidence PacketUse when a payer contract and underpayment review result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the payer variance evidence brief containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; each variance is a reproducible comparison and contract interpretation is escalated to authorized counsel or cont...Votes: 0GitHub stars: 2
- Health Admin Payer Contract Change Impact TraceUse when a version, rule, source, or stakeholder change may affect payer contract and underpayment review to produce a before/after change record and impact map for the payer variance evidence brief. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each variance is a reproducible comparison and contract interpretation is escalated to authorized counsel or contracting staff. Use configured search, fetch, read, ...Votes: 0GitHub stars: 2
- Health Admin Payer Contract Closeout Handoff LedgerUse when a payer contract and underpayment review work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the payer variance evidence brief with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; each variance is a reproducible comparison and contract interpretation is escalated to authorized counsel or contracting staff. Use conf...Votes: 0GitHub stars: 2
- Health Admin Payer Contract Completeness ReconciliationUse when the payer contract and underpayment review workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the payer variance evidence brief with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; each variance is a reproducible comparison and contract interpretation is escalated to authorized counsel or contracting s...Votes: 0GitHub stars: 2
- Health Admin Payer Contract Exception Triage QueueUse when the payer contract and underpayment review workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the payer variance evidence brief with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; each variance is a reproducible comparison and contract interpretation is escalated to authorized counsel or contracting staff. Use con...Votes: 0GitHub stars: 2
- Health Admin Payer Contract Recovery Readiness DrillUse when the payer contract and underpayment review workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the payer variance evidence brief with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; each variance is a reproducible comparison and contract interpretation is escalated to authorized counsel or contracting sta...Votes: 0GitHub stars: 2
- Health Admin Payer Contract Scenario Sensitivity MatrixUse when the payer contract and underpayment review team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the payer variance evidence brief with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each variance is a reproducible comparison and contract interpretation is escalated to authorized counsel or contracting staff. Use configure...Votes: 0GitHub stars: 2
- Health Admin Payer Contract Scope Intake GateUse when a new payer contract and underpayment review request needs a bounded work scope to produce a scoped intake card for the payer variance evidence brief. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each variance is a reproducible comparison and contract interpretation is escalated to authorized counsel or contracting staff. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and ...Votes: 0GitHub stars: 2
- Health Admin Payer Contract Source Provenance LedgerUse when a decision about payer contract and underpayment review depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the payer variance evidence brief. Success means each material claim has a source, version/date, location, and confidence note; each variance is a reproducible comparison and contract interpretation is escalated to authorized counsel or contracting staff. Use configured search, fetch, read, browser, test, and write capabili...Votes: 0GitHub stars: 2
- Health Admin Payer Contract Threshold Rule CheckUse when a payer contract and underpayment review decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the payer variance evidence brief showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; each variance is a reproducible comparison and contract interpretation is escalated to authorized counsel or contrac...Votes: 0GitHub stars: 2
- Health Admin Pharmacy Admin Approval Evidence PacketUse when a pharmacy program and inventory administration result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the pharmacy operations exception list containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; administrative discrepancies are traceable and no therapeutic, dosing, or substitution recommendation...Votes: 0GitHub stars: 2
- Health Admin Pharmacy Admin Change Impact TraceUse when a version, rule, source, or stakeholder change may affect pharmacy program and inventory administration to produce a before/after change record and impact map for the pharmacy operations exception list. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; administrative discrepancies are traceable and no therapeutic, dosing, or substitution recommendation is made. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Health Admin Pharmacy Admin Closeout Handoff LedgerUse when a pharmacy program and inventory administration work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the pharmacy operations exception list with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; administrative discrepancies are traceable and no therapeutic, dosing, or substitution recommendation is made. Use configure...Votes: 0GitHub stars: 2