Ran a quick audit on our AIMS last night and found 27 “MAC” cases mapped to media access control in the metadata, so the dashboard tried to trend sedation depth against Wi‑Fi signal. Anyone else run into HL7 vocab collisions like this, and did you fix it with a local mapping or make the vendor patch their terminology service?
Had the same circus — our AIMS graphed “sedation depth” vs Wi‑Fi bars. > did you fix it with a local mapping or make the vendor patch their terminology Local first: in Mirth we rewrite OBX‑3 “MAC” to SNOMED 428311008 (SCT) when the order is anesthesia and reject any “MAC” with IANA as the code system; vendor patch came later — want the channel snippet?
I totally get the chaos with the MAC tag — i found that setting up a local mapping before the vendor fixed their terminology saved us hours of head-scratching… Have you thought about sharing your experiences directly with the vendor for better support?
Sounds like a real scenario where you might end up trying to find the Wi-Fi password in an OR. I’ve found that setting clear naming conventions upfront can save a lot of confusion down the line. Have you had any luck with centralized terminology tools that help prevent these mix-ups, @t_haywood67?