iDAAS Connect for Processing ePrescribe data - This effort has started to support ePrescribe specific transactions.
We are focusing on continuing to improve. With the numerous implementation and partner implementations we have focused on success overall and as we progress forward the intent is to focus on success while being consistent. Please find details on how to help us here.
For any repository to be implemented there are two types of requirements, overall general requirements and then there are specific submodule requirements. We try and maintain as close to a current detailed list as we can, for those specifics please check here.
It is important to understand that this submodule provides thw ability to process data using standard connectors provided, any specific ePrescribe data parsers.
Within this module the following connectivity scenarios and examples are provided.
- Each endpoint connectivity has configurable processes built in for empi, heda (healthcare event driven architecture), datatier, deidentificaton, public cloud, SDOH and terminologies.
There will be the complete transaction set to align with ePrescribe needs.
- Rest endpoints for rxfill
The following section is designed to cover the details around implementing.
For the specifics around one or more specific implementations for this module please feel free to look here.
Within each submodule/design pattern/reference architecture in this repository there is a specific README.md. It is intended to follow a specific format that covers a solution definition, how we look to continually improve, pre-requisities, implementation details including specialized configuration, known issues and their potential resolutions. However, there are a lot of individual capabilities, we have tried to keep content relevant and specific to cover specific topics.
- For cloning, building and running of assets that content can be found here.
- Within each implementation there is a management console, the management console provides the same interface and capabilities no matter what implementation you are working within, some specifics and and details can be found here.
As of the time of this content publication there are no known specific issues.