Open Bridg109 opened 2 years ago
@Bridg109 - did you get very far with this? Is this just regexing the fda package information field to get total count of unit per outer NDC?
I stopped when we changed to postgres. Noting it should be easier now
On Sun, May 22, 2022, 8:44 AM Joseph LeGrand @.***> wrote:
@Bridg109 https://github.com/Bridg109 - did you get very far with this? Is this just regexing the fda package information field to get total count of unit per outer NDC?
— Reply to this email directly, view it on GitHub https://github.com/coderxio/sagerx/issues/8#issuecomment-1133899407, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJUPMCRBOWTV5EIFBXPN5WDVLI23FANCNFSM5GYRMQFQ . You are receiving this because you were mentioned.Message ID: @.***>
See some analysis and notes on this page: https://coderx.io/sagerx/source-data/dailymed
See branch I associated with this issue (jrlegrand/pack-size
).
I've noticed that "parts" (i.e. kit parts) tend to be the final part of a description.
Also - parts can have "sub-parts"(?) like this: * 1 SYRINGE in 1 TRAY / .4 mL in 1 SYRINGE (0025-0329-01)
I'm thinking that we have 3(?) layers - maybe more:
Example: 2 KIT in 1 CARTON (0025-0333-02) / 1 KIT in 1 KIT 1 SYRINGE in 1 TRAY / .4 mL in 1 SYRINGE (0025-0329-01) 1 mL in 1 PACKET (0069-1111-01)
Another way of visualizing this:
Proposal
Parse the fda_ndc package field into a package equivalency table
Rationale
adds digestible package information for people to use tied to NDCs