NewCrop Implementation Guide

 

Schemas

NewCrop leverages two schemas, NCScript and NCStandard, to maintain data structure. Schema validation is critical, and a copy of these schemas should be run locally against any messages prior to sending them to NewCrop.

NCScript (last update: 01/15/2020)

NCScript identifies the full list of acceptable elements and their order. Optional elements are defined in NCSchema by the MinOccurs value. If the value is not being submitted, then the optional element should not be passed at all, rather than an empty tag.

NCStandard (last update: 01/15/2020)

NCStandard defines each element type with a specific array of acceptable characters or values.


Clickthrough Integration

Connecting directly to NewCrop allows for a rapid integration while shielding your application from most Surescripts, State, and ONC regulations. Using the NewCrop User Interface provides immediate access to our full array of e-prescribing and support tools: Surescripts Drug History and Formulary services, State PDMP access, Pharmacogenomics review, Drug Interactions checks, Patient Education, Pharmacy lookup, Drug lookup, and Sig Builder tools. The interface may be customized through use of a style sheet or other configuration options that may be discussed with your Implementation Manager.

Test Driver

This page emulates the direct connection from your EHR to the NewCrop UI. This is triggered via a POST to https://preproduction.newcropaccounts.com/InterfaceV7/rxentry.aspx containing an XML payload. This POST may be performed in either a browser window or frame. We recommend the use of the latest browsers with cookies enabled to avoid any compatibility issues.

This XML payload is detailed in the Building an XML POST document, and several examples are linked from the Driver page.

Note that most clickthrough implementations will require a few APIs to create the best workflow. Typical examples include Update1.GetPatientFullMedicationHistory6 and Update1.GetAccountStatusV2. These services are described below.

 

Web Service Integration

API Integration gives you complete control over your User Interface look and workflow. Most services available from the NewCrop UI may also be accessed through APIs. However, this process can be time consuming and will require significant maintenance to remain in compliance with regulatory bodies, including Surescripts, CMS, and ONC.

WSDL

Our APIs are organized across a few WSDLs loosely organized by the type of call. Each WSDL has its own test page where the APIs may be run directly. The appropriate fields must be populated prior to running the web service call.

Please look at Update1 first, and always prefer the latest iterations of services (e.g. GetPatientFullMedicationHistory6). Contact your Implementation Manager prior to implementing a new service.

Update1

Holds our most frequently used services, including routing, drug interactions, and eligibility services.

Formulary2

Provides our latest formulary service – Formulary2.FormularyComposite.

Account

Typically used only to create new client accounts via Account.PartnerAccountCreate.

Clinical Messaging

Houses our MTOM direct messaging tools.



API XML Payload Samples

Some services will require an XMLin. We have included some samples at the link below. If you require additional XML samples, please reach out to your Implementation Manager.

XMLin Examples



Copyright 2004-2024, NewCrop, LLC. All rights reserved.
UNPUBLISHED - RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES.
Privacy Statement Terms of Use  Comments/Questions: support@newcroprx.com