MME Calculation logic is currently expressed in terms of RxNorm codes. Ordering systems are typically able to determine the RxNorm code for the medication being prescribed, and so this works well for the ordering case. However, if we are looking at dispense data, systems typically have that in terms of First Data Bank (FDB) or National Drug Code (NDC) identifiers. There are well-established mappings available from RxNorm to FDB and NDC, so there is a feasible path to perform the MME calculation on dispense data, however, an approach needs to be determined and the effort put in to realizing that approach (i.e. do we express the calculation in terms of FDB and NDC directly, or do we provide a feasible mechanism to support the mapping as part of the call (would need to be a cached and maintained mapping, couldn't involve a real-time service call to do that mapping).
This has been discussed in the context of some pilots, but a decision has not yet been reached as to whether this will be necessary or not, so we have not assigned it to a milestone yet.
MME Calculation logic is currently expressed in terms of RxNorm codes. Ordering systems are typically able to determine the RxNorm code for the medication being prescribed, and so this works well for the ordering case. However, if we are looking at dispense data, systems typically have that in terms of First Data Bank (FDB) or National Drug Code (NDC) identifiers. There are well-established mappings available from RxNorm to FDB and NDC, so there is a feasible path to perform the MME calculation on dispense data, however, an approach needs to be determined and the effort put in to realizing that approach (i.e. do we express the calculation in terms of FDB and NDC directly, or do we provide a feasible mechanism to support the mapping as part of the call (would need to be a cached and maintained mapping, couldn't involve a real-time service call to do that mapping).