Libraries for developing NCPDP SCRIPT based systems (a standard for e-prescribing)
Posted
by Kaveh Shahbazian
on Stack Overflow
See other posts from Stack Overflow
or by Kaveh Shahbazian
Published on 2010-06-12T17:16:47Z
Indexed on
2010/06/13
5:32 UTC
Read the original article
Hit count: 389
What are (based on experiences) best (commercial or open source) libraries for developing NCPDP-based systems?
Background: NCPDP (National Council for Prescription Drug Programs) is a not-for-profit, ANSI-accredited, standards development organization. One of it's standards is the SCRIPT Standard for Electronic Prescribing, which allows PHARMACY, PRESCRIBER (i.e. Physician) and PAYERS (patient or more often insurer) communicate. So the SCRIPT standard is about data transmission.
Problem: One step in implementing such systems is to develop models for data based on SCRIPT standard. These models should have utilities for serializing/deserializing to/from SCRIPT binary format and SCRIPT XML format (there are two distinct formats here; both must be supported). Here rises the problem (for me at least). To develop this subsystem for handling the model, implementing serializing and deserializing facilities and keep it uptodate with the SCRIPT standard specifications is a lot of work; it needs it's own team and team management issues (to support a standard implementation).
So I am looking for a solution to this problem; to keep standard implementation out of the way and focusing on main problems.
Thanks to all
(Thankyou Freiheit for your hints!)
Edit 2: Thanks to all for help! NCPDP (National Council for Prescription Drug Programs) is an standard for e-prescribing. It defines two formats for message transmission: binary and XML. Implementing XML is somehow easier because it is a standard format which in turn gives us more tooling options. The binary format has a very big specification and time-consuming to implement.
I did not find an open source solution to work with. So I am looking for commercial alternatives.
Edit 1: Please guide me; what's wrong with this question?
© Stack Overflow or respective owner