Rsd Schedule
Lorri Dent
Please note that a substance need not be listed as a controlled substance to be treated as a Schedule I substance for criminal prosecution. A controlled substance analogue is a substance which is intended for human consumption and is structurally or pharmacologically substantially similar to or is represented as being similar to a Schedule I or Schedule II substance and is not an approved medication in the United States. (See 21 U.S.C. 802(32)(A) for the definition of a controlled substance analogue and 21 U.S.C. 813 for the schedule.)
Schedule I drugs, substances, or chemicals are defined as drugs with no currently accepted medical use and a high potential for abuse. Some examples of Schedule I drugs are: heroin, lysergic acid diethylamide (LSD), marijuana (cannabis), 3,4-methylenedioxymethamphetamine (ecstasy), methaqualone, and peyote.
Schedule II drugs, substances, or chemicals are defined as drugs with a high potential for abuse, with use potentially leading to severe psychological or physical dependence. These drugs are also considered dangerous. Some examples of Schedule II drugs are: combination products with less than 15 milligrams of hydrocodone per dosage unit (Vicodin), cocaine, methamphetamine, methadone, hydromorphone (Dilaudid), meperidine (Demerol), oxycodone (OxyContin), fentanyl, Dexedrine, Adderall, and Ritalin
Schedule III drugs, substances, or chemicals are defined as drugs with a moderate to low potential for physical and psychological dependence. Schedule III drugs abuse potential is less than Schedule I and Schedule II drugs but more than Schedule IV. Some examples of Schedule III drugs are: products containing less than 90 milligrams of codeine per dosage unit (Tylenol with codeine), ketamine, anabolic steroids, testosterone
Schedule IV drugs, substances, or chemicals are defined as drugs with a low potential for abuse and low risk of dependence. Some examples of Schedule IV drugs are: Xanax, Soma, Darvon, Darvocet, Valium, Ativan, Talwin, Ambien, Tramadol
Schedule V drugs, substances, or chemicals are defined as drugs with lower potential for abuse than Schedule IV and consist of preparations containing limited quantities of certain narcotics. Schedule V drugs are generally used for antidiarrheal, antitussive, and analgesic purposes. Some examples of Schedule V drugs are: cough preparations with less than 200 milligrams of codeine or per 100 milliliters (Robitussin AC), Lomotil, Motofen, Lyrica, Parepectolin
Updated June 7, 2024: A previously announced markup schedule included a subcommittee markup for the Fiscal Year 2025 Commerce, Justice, Science, and Related Agencies Bill on June 12th. Due to scheduling conflicts with the Congressional Baseball Game, that bill will be marked up in subcommittee on June 26th.
These recommendations must be read with the notes that follow. For those who fall behind or start late, provide catch-up vaccination at the earliest opportunity as indicated by the green bars. To determine minimum intervals between doses, see the catch-up schedule (Table 2).
Recommended by the Advisory Committee on Immunization Practices (ACIP) and approved by the Centers for Disease Control and Prevention (CDC), American Academy of Pediatrics (AAP), American Academy of Family Physicians (AAFP), American College of Obstetricians and Gynecologists (ACOG), American College of Nurse-Midwives (ACNM), American Academy of Physician Associates (AAPA), and National Association of Pediatric Nurse Practitioners (NAPNAP).
Some events have multiple activity types. For these events, you can specify which activity types will trigger a workflow run. For more information about what each activity type means, see "Webhook events and payloads."
Note: More than one activity type triggers this event. For information about each activity type, see "Webhook events and payloads." By default, all activity types trigger workflows that run on this event. You can limit your workflow runs to specific activity types using the types keyword. For more information, see "Workflow syntax for GitHub Actions."
Runs your workflow when branch protection rules in the workflow repository are changed. For more information about branch protection rules, see "About protected branches." For information about the branch protection rule APIs, see "Objects" in the GraphQL API documentation or "REST API endpoints for branches and their settings."
Runs your workflow when activity related to a check run occurs. A check run is an individual test that is part of a check suite. For information, see "Using the REST API to interact with checks." For information about the check run APIs, see "Objects" in the GraphQL API documentation or "REST API endpoints for check runs."
Note: More than one activity type triggers this event. For information about each activity type, see "Webhook events and payloads." Although only the completed activity type is supported, specifying the activity type will keep your workflow specific if more activity types are added in the future. By default, all activity types trigger workflows that run on this event. You can limit your workflow runs to specific activity types using the types keyword. For more information, see "Workflow syntax for GitHub Actions."
Runs your workflow when check suite activity occurs. A check suite is a collection of the check runs created for a specific commit. Check suites summarize the status and conclusion of the check runs that are in the suite. For information, see "Using the REST API to interact with checks." For information about the check suite APIs, see "Objects" in the GraphQL API documentation or "REST API endpoints for check suites."
Runs your workflow when someone creates a Git reference (Git branch or tag) in the workflow's repository. For information about the APIs to create a Git reference, see "Mutations" in the GraphQL API documentation or "REST API endpoints for Git references."
Runs your workflow when someone deletes a Git reference (Git branch or tag) in the workflow's repository. For information about the APIs to delete a Git reference, see "Mutations" in the GraphQL API documentation or "REST API endpoints for Git references."
Runs your workflow when someone creates a deployment in the workflow's repository. Deployments created with a commit SHA may not have a Git ref. For information about the APIs to create a deployment, see "Mutations" in the GraphQL API documentation or "REST API endpoints for repositories."
Runs your workflow when a third party provides a deployment status. Deployments created with a commit SHA may not have a Git ref. For information about the APIs to create a deployment status, see "Mutations" in the GraphQL API documentation or "REST API endpoints for deployments."
Runs your workflow when a discussion in the workflow's repository is created or modified. For activity related to comments on a discussion, use the discussion_comment event. For more information about discussions, see "About discussions." For information about the GraphQL API, see "Objects."
Runs your workflow when a comment on a discussion in the workflow's repository is created or modified. For activity related to a discussion as opposed to comments on the discussion, use the discussion event. For more information about discussions, see "About discussions." For information about the GraphQL API, see "Objects."
Runs your workflow when an issue or pull request comment is created, edited, or deleted. For information about the issue comment APIs, see "Objects" in the GraphQL API documentation or "Webhook events and payloads" in the REST API documentation.
The issue_comment event occurs for comments on both issues and pull requests. You can use the github.event.issue.pull_request property in a conditional to take different action depending on whether the triggering object was an issue or pull request.
For example, this workflow will run the pr_commented job only if the issue_comment event originated from a pull request. It will run the issue_commented job only if the issue_comment event originated from an issue.
Runs your workflow when an issue in the workflow's repository is created or modified. For activity related to comments in an issue, use the issue_comment event. For more information about issues, see "About issues." For information about the issue APIs, see "Objects" in the GraphQL API documentation or "REST API endpoints for issues."
c80f0f1006