PACER | PACER software and deployment instruction

by gt-health Java Version: v1.6.0 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions Vulnerabilities Install Support

kandi X-RAY | PACER Summary

PACER is a Java library. PACER has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. However PACER build file is not available. You can download it from GitHub.

PACER is a stand-alone deployment service-stack designed to help FHIR Health Record Providers manage access to their data, and facilitate automatic report submission to external sources. PACER exists as a set of microservices that live within the same network as the FHIR provider. By managing access to the FHIR server through the PACER microservices, maintainers can provide a stronger level of access and security to their secure data sources. The system has 2 major configurable feature points: a Clinical Query Language (CQL) library for crafting patient context, and fhir-filter library for restricting access to certain resources and data, for the purpose of securing Personally Indentifying Information. Both libraries can be configured at boot-up and run-time, and will be explained in detail in their subsequent wiki sections. Please refer to the wiki for more detailed explanations on their components at Software requirements.

Support

Quality

Security

License

Reuse

Support

PACER has a low active ecosystem.

It has 1 star(s) with 4 fork(s). There are 7 watchers for this library.

It had no major release in the last 12 months.

There are 0 open issues and 4 have been closed. On average issues are closed in 3 days. There are 16 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of PACER is v1.6.0

Quality

PACER has no bugs reported.

Security

PACER has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

PACER is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

PACER releases are available to install and integrate.

PACER has no build file. You will be need to create the build yourself to build the component from source.

Installation instructions are available. Examples and code snippets are not available.

Top functions reviewed by kandi - BETA

kandi has reviewed PACER and discovered the below as its top functions. This is intended to give you an instant insight into PACER implemented functionality, and help decide if they suit your requirements.

Evaluate CQL request
Register providers
Create a Source object from XML representation
Creates an access token from oauth
Called when an incoming request is processed
Create HTTP headers
Checks if the request is allowed
Inspect the token
Resolves the expression
Compares two objects
Deserialize a datetime object
Load cql scripts
Translates a source code
Evaluate the object
Persist person list
Retrieve objects from FHIR
Returns an iterable of objects
Generate a CapabilityStatementRest
Runs the REST action
Validate authorization endpoint
Retrieve a list of objects
Initialize the server
Retrieve a single object
Makes an ECR request
Main entry point
Command - line entry point

Get all kandi verified functions for this library.

PACER Key Features

No Key Features are available at this moment for PACER.

PACER Examples and Code Snippets

No Code Snippets are available at this moment for PACER.

Community Discussions

No Community Discussions are available at this moment for PACER.Refer to stack overflow page for discussions.

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install PACER

Pacer consists of 2 seperate docker-compose files: docker-compose-db.yml and docker-compose-apps.yml. docker-compose-db.yml contains the configuration information for the database, and should be built and ran first before the docker-compose-apps.yml script. docker-compose-apps.yml consist of the application components that manage the PACER workflow.
From the command line, run docker-compose -f docker-compose-db.yml build and docker-compose -f docker-compose-apps.yml build from the top of the project. This will build from the source folders deployable images for 6 different containers: cql-storage, cql-execution, db, fhir-filter, job-management-system, results-manager.
From the command line, run docker-compose -f docker-compose-db.yml up -d, and wait for the database service to complete it's initdb.script. Once that is completed, run docker-compose -f docker-compose-apps.yml up -d This will turn on all the applications components and detach the process from the command line.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: