Net2Net REST

product overview net2net rest is used to exchange clinical messages a clinical message in the context of this guide is a message delivered to and from authorized customers on the surescripts network (as such may be renamed from time to time by surescripts), and satisfies the following requirements contains clinical or administrative information about a specific patient used for health care payment, treatment, or operations is not structured except to the extent necessary to transmit an attachment and as necessary for address fields is not limited to a specific message type or use case does not require message type or use case specific workflow integration into the electronic health record (ehr) by implementing the net2net rest standard, surescripts enables our customer to meet meaningful use stage 2 (mu2) requirements surescripts messaging meets the transport and security specifications outlined in the office of the national coordinator’s (onc) health information technology standards, implementation, specifications, and certification criteria for electronic health record technology, 2014 edition about this guide this surescripts net2net rest implementation guide assists customers in developing and transferring messages needed to provide secure information exchange between providers the audience for this document includes any customer responsible for developing a system interface to the surescripts network using net2net rest this guide is meant to support, integrate, and further clarify the ncpdp standard schemas, implementation guides and best practices as used through the surescripts network it does not reproduce the base standard in its entirety requirements beyond those in the ncpdp documentation are called out in this guide and are also enforceable customers should read and comprehend the associated standards prior to reading this guide document references please reference the following documents when reading this guide surescripts provided documents surescripts civ6 0 xsd documents to be obtained by the customer ncpdp’s script standard implementation guide (version 10, release 6) pertinent to portions of the common message header, status, error, and verify ( https //ncpdp org/ https //ncpdp org/ ) ncpdp script implementation recommendations version 1 43 ( https //ncpdp org/ https //ncpdp org/ ) ncpdp's external code list 2017071 (ncpdp online tool) ( https //ncpdp org/ https //ncpdp org/ ) 2014 edition release 2 electronic health record (ehr) certification criteria and the onc hit certification program; regulatory flexibilities, improvements, and enhanced health information exchange; final rule https //www federalregister gov/articles/2014/09/11/2014 21633/2014 edition release 2 electronic health record ehr certification criteria and the onc hit ncpdp script this guide utilizes the ncpdp (national council for prescription drug programs) messaging standard prescriber/pharmacist interface script version 2023011 as a baseline to become an ncpdp member, please go to https //www ncpdp org/membership aspx https //www ncpdp org/membership aspx the ncpdp script standard 2023011 package contains a complete list of fields and additional requirements customers should read and comprehend the associated standards prior to reading this guide ncpdp is an american national standards institute (ansi) accredited standard development organization the ncpdp “script” standard is a copyrighted document and may be obtained by contacting ncpdp 9240 e raintree drive scottsdale, az 85260 7518 phone (480) 477 1000 fax (480) 767 1042 https //www ncpdp org https //www ncpdp org