Skip to main content

How to Create and Use Macros in MedMe

Macros let you save reusable pieces of text like common SIG instructions or note templates, and insert them instantly while documenting, just by typing a short keyword.

Written by Albert Lam

Table of Contents

What is a macro?

A macro is a keyword-and-content pair you set up once and reuse anywhere. For example, you could create a macro with the keyword peridex that expands into a full set of Peridex SIG instructions, so you never have to type it out again.

Creating and managing macros

  1. Go to Settings > Organization > Macros.

  2. Click Add Macro.

  3. Enter a Keyword (up to 50 characters) and the Content you want it to expand into (up to 5,000 characters).

  4. Click Save.

You can also Edit or Delete any macro from this list, and use the search bar to filter macros by keyword. Any pharmacist at your pharmacy can create, edit, or delete macros – they're shared across the whole pharmacy, not tied to one user.

Do not include any patient information (PHI) in a macro's content. Macros are stored and reused as-is and are not patient-specific.

Each pharmacy can have up to 100 macros.

Using a macro

While typing in any pharmacist-side text field such as in the documentation/notes editor — type a plus sign followed by the start of your keyword, for example +peri.

  • A suggestion menu appears listing matching macros.

  • Use the arrow keys to move between suggestions.

  • Press Enter or Tab to insert the highlighted macro at your cursor.

  • Press Escape to dismiss the menu without inserting anything.

Matching is case-insensitive and only triggers when the plus sign starts a new word (so it won't accidentally trigger mid-sentence).


Frequently asked questions

Who can see and use macros?

Everyone at your pharmacy shares the same list of macros, there are no personal, per-user macros yet.

Can I use macros in every text field?

Macros work in plain text and rich text fields across the pharmacist side, including the documentation/notes editor.

Did this answer your question?