Quick question from tonight’s shift: are you styling Alzheimer disease and Crohn disease without the apostrophe per AHDI, or does your facility still prefer ‘Alzheimer’s’? Trying to settle a friendly QA note in ChartNet — chime in with what your spec says, and you’ve got this.
We’re AHDI-style now — no apostrophes: Alzheimer disease, Crohn disease (per AHDI BOS: https://www.ahdionline.org/page/BookofStyle), and I set a ChartNet QA rule to flag ’s after eponyms so it auto-suggests the fix. , this drives me nuts, but we leave the apostrophe only in direct quotes or legacy problem lists so older templates don’t break. If your spec leans AMA, does QA allow both or hard-fail on Alzheimer’s?
And house style here: AMA/AHDI nonpossessive in narrative, but we don’t alter apostrophes in copied problem lists/diagnosis codes since ICD‑10/SNOMED still show “Alzheimer’s disease.” I added a ChartNet whitelist so @dashsignal21’s flag ignores coded sections and only pings narrative — keeps QA happy and billing calmer than a cat in a sunbeam. Does your spec split narrative vs problem list/claims text?
I go AMA/AHDI with “nonpossessive eponyms” in narrative and use a TextExpander snippet that strips the ’s from common ones; I just toggle it off when pasting imports or in headers so it won’t change official names. Small caveat: I keep the apostrophe if it’s a direct quote or a named entity. Do you have leeway to use an expander, or is @ChartNet handling that for you?
I drop the apostrophe in narrative and treat it like glitter — fine if it’s in a provider quote, otherwise it just gets everywhere. My quick step: end-of-note Ctrl+F for “’s disease” and “’s syndrome” to catch strays. When I need a tiebreaker, I peek at MeSH (e.g., “Alzheimer Disease” here: MeSH Browser); anyone else lean on that?