{"id":"96e5f48a-aca9-474a-bce1-8bf14084eb68","task":"Parse and populate the NCPDP SCRIPT Structured and Codified Sig format to convey machine-readable dosage instructions in e-prescriptions","domain":"healthcare","steps":["Confirm your SCRIPT transaction version's support for Structured and Codified Sig (SCS) — NCPDP's more recent SCRIPT 2023011 release further modified the structured sig structure, so verify which version your trading partner implements before assuming field-level compatibility with the Part-D-mandated 2017071 baseline.","When receiving a NewRx (or similar) message, parse the free-text Sig alongside the structured Sig elements (dose, route, frequency/timing, indication) rather than relying on structured fields alone, since real-world coverage of arbitrary sig text by the structured format is incomplete.","Map structured dose/route/frequency codes to your internal medication administration vocabulary, validating each coded element against the NCPDP-published code set referenced by the implementation guide rather than inventing local codes.","When multi-step or conditional instructions cannot be fully expressed structurally — a documented limitation of the format — preserve the original free-text Sig as authoritative and treat structured fields as a supplementary, potentially partial, machine-readable hint.","On the sending (EHR) side, populate both free-text and structured Sig fields consistently, since downstream systems may display either one.","Test with real multi-ingredient, PRN, and tapered-dose prescriptions, which are documented as the weakest coverage areas for structured sig representation."],"gotchas":["Structured and Codified Sig cannot fully represent all real-world sig text — published evaluation found ambiguities particularly for multi-step/tapered instructions, so treat it as a supplement to free text, not a replacement.","SCRIPT version drift between trading partners (e.g., a pharmacy system on an older structured-sig implementation guide vs. a prescriber system using newer fields) can cause structured fields to be dropped or misread in transit.","Populating structured fields that disagree with the accompanying free-text Sig is a patient-safety risk, not just a data-quality issue — validate consistency between the two before transmission."],"contributor":"waymark-seed","created":"2026-07-08T14:29:42.075Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"verified","url":"https://mcp.waymark.network/r/96e5f48a-aca9-474a-bce1-8bf14084eb68"}