| |
| |
 Getting Started - What is ePostRx?™ |
 |
| |
ANSHealth offers
the industry's only single source, end-to-end, enterprise
pharmacy solution that can support all your electronic SCRIPT,
Prescription Management and Rx Dispensing requirements across
any pharmacy resource. ePostRx automates
the prescription-fulfillment process, from Order/Rx/OTC
receipt and insurance adjudication, to DUR and dispensing
for all pharmacy business models, including retail chains
and high-volume pharmacies operated by insurers, integrated
health systems, supermarkets, wholesalers, mail order service
or specialty mail facilities. ePostRx is designed to maximize
efficiency across any pharmacy's resource. |
|
| |
| Why
open source ePostRx? |
There are many 'canned' reasons why ANSHealth
choose the open-source approach to further our ePostRx product
suite, ranging from the practical to the religious. But
our main goal is to make ePostRx the best 'free' enterprise
pharmacy solution available for all forms of business workflows,
worldwide! So if you're a developer, potential customer
or contemplating becoming a partner, get involved!
|
|
| |
| For
Developers |
ePostRx is a very mature enterprise pharmacy
web application (3.5+ years). ePostRx is developed using
Java distributed technologies such as J2EE, JSP, XML and
XSL and other web technologies. Runs on any platform that
supports the JVM (Java Virtual Machine) such as Windows,
Solaris, Linux etc. The RDBMS is currently MSSQL Server.
The following summarizes the various components used in
the development of ePostRx:
|
|
| |
| ePostRx
Architecture List |
| Java programming language (J2EE stack)
|
iText PDF engine |
| JBoss AS
| JSP, JSTL and custom tags |
| Various Apache Jakarta projects |
HTML,XML,XSL and Javascript |
| Jasper Reports Engine |
Bouncy Castle Crypto |
| Quartz scheduler |
Ajax, Dojo |
| XFire (SOA) |
IBatis DAO |
| XStream/Dojo |
JLDAP |
| iReportDesigner |
. |
|
| |
As we continually evolve ePostRx into a true end-to-end pharmacy
solution to support all business workflows, there are many functional
areas we are still lacking and could use your expertise. The current
ePostRx Task is outlined below:
|
| |
| ePostRx
Task List |
| POS interface |
| Documentation! Documentation!
Documentation! |
| Patient Eligibility Transaction
Loads (EDI 270/271) |
| Database support for Oracle,
MySQL and PostgreSQL |
| Support for Weblogic, Apache
Geronimo and Websphere |
| Entity Bean generation through
XDoclet |
| Documentation! Documentation!
Documentation! |
| Some additional pharmacy reports
via Jasper/iReport Designer |
| Deploy on Linux,Unix |
| 508 Disability compliance
for web application |
| Internationalization |
| Documentation! Documentation!
Documentation! |
| Help file updates. |
|
| |
|
Join the ePostRx community today! |
| If you feel you could contribute to enhance the healthcare industry's
most full-featured free enterprise pharmacy solution, we urge you
to send
a note to ANSHealth to take ownership of a task, or simply just
get involved with the ePostRx community. To get started, may we suggest
the following: |
| |
- Become familiar with the ePostRx products
and its architecture.
- View on-line demo of ePostRx
- Download the source tree.
- Browse the documentation library.
- Join our ePostRx community forums:
General Forums
Yahoo Active Customer Groups
- Join our
Mailing List.
- Submit a feature
request
- Submit a bug report (When submitting a bug
report, please include the operating system, browser version,
JDK version, stack trace and steps to reproduce the bug.
- Download and complete the
contributor-agreement.
Note: If you wish to contribute, you will need
to complete a Contributor Agreement ("CA"). Many open
source projects, including the Free Software Foundation, Red
Hat, MySQL, JBoss and OpenOffice.org require that contributors
assign their copyright when they contribute code. ANSHealth,
the ePostRx project sponsor and originator, has come up with
an innovative CA that allows contributors to retain their own
copyright while sharing a joint copyright interest in the contributed
code. This way contributors retain all the rights granted by
copyright law while sharing those rights with the open source
project sponsor so that the code is protected by both the GNU
General Public License ("GPL") and copyright law.
The CA does not in any way change the rights or responsibilities
of the ePostRx community under the GPL. ANSHealth is only requesting
that you take one additional step to increase ePostRx flexibility,
protect the ePostRx code base and make alternative licensing
models possible by executing a CA for any contribution. To complete
the CA, download the
contributor-agreement. The PDF file is form-enabled, so
if you are using a suitable reader you can type your details
directly into the PDF. If you do not have a forms capable reader,
please take care to print your details very clearly, including
your email address.
|
| |
Please note: Signing an agreement does not grant
you rights as a committer, but is simply a step in becoming a
committer. Committer access is by invitation only and is a privilege
for those who have demonstrated exceptional ability in contributing
to the ePostRx community.
|
| |
| Incident
support now available for GPL users only. Just contact ANSHealth. |
- Per incident support, 1 incident - $200
perfect for open source customers that need occasional help.
- Per incident support, 3 incidents - $600
help available when you need it.
- Per incident support, 8 incidents - $995
save big by pre-purchasing incident support in bulk.
|
|
| |
IMPORTANT - Proprietary Vendor APIs |
| Although ePostRx is free and 100% GPL, there are a
few vendor proprietary APIs and source code files (~10) that are
not included in the final GPL software bundle. These files were intentionally
omitted because of non-disclosure agreements currently enforced between
ANSHealth and third party vendors who would not allow ANSHealth to
bundle their associated code. These areas include: |
| |
- Drug Database Interface (Medispan, First Databank...)
- Interactive Voice Recognition (Telemanager,Ateb,Voice
Tech...)
- Auto Fulfillment (McKesson,ScriptPro,ProRata,AutoMed...)
|
If you wish to gain access to
these files, you will need to purchase a
commercial license so ANSHealth
can enforce these agreements. However, ANSHealth would suggest that
the community pressure those company's mentioned above to release
their APIs/specifications to the ePostRx community for future GPL
releases. ANSHealth believes most of these APIs or specifications
are just conduits to their actual Intellectual Property (data or
hardware) and should be made available to the community. For example,
it's not like we're asking them to make available the Drug Database
data or specifications on the IVR or fulfillment hardware, just
the APIs to access it!
Most of the support jars are included in the software bundle and
are available for free and licensed under various Open Source licenses
(GNU GPL, LGPL, Apache, BSD etc..). With exception to those proprietary
vendors listed above, the other jars you will need to download to
build ePostRx are the following: |
| |
- Swiss
Sql One API
- Quartz
Scheduler
- Xfire(SOA)
- IBatis (DAO)
|
| |
|
| |
|
| |
| |
For corporations, government agencies, and
end-users, MyePostRx Network
is your best value. It includes:
-
Access to the ePostRx Support Team
-
Access to the ePostRx Knowledge Base that
provides the answers you need in one central location
-
Maintenance, updates, and upgrades
|
|
| Community
Support
|
For users of ePostRx Community, there are
several ways to get help both from ANSHealth and from other
ePostRx developers. These include:
-
Forums
-
Developer Zone Articles
- Bugs Database
- Consulting Services
- Training and Certification
|
|
| What
is ANSHealth's position on Software Patents?
|
ANSHealth has consistently taken the position
that software patents generally impede innovation in software
development and that software patents are inconsistent with
open source/free software. At the same time, we are forced
to live in the world as it is, and that world currently
permits software patents. A relatively small number of very
large companies have amassed large numbers of software patents.
One defense against such misuse is to develop a corresponding
portfolio of software patents for defensive purposes. Many
software companies, both open source and proprietary, pursue
this strategy. In the interests of our company and in an
attempt to protect and promote the open source community,
ANSHealth has elected to adopt this same stance. We do so
reluctantly because of the perceived inconsistency with
our stance against software patents; however, prudence dictates
this position.
|
|
| |
| |
| |
