Repository in public archive. Please consider visiting our new preprocessing service in use
This repository contains an example of a preprocesing service. A preprocessing service reads the Package Leaflet of an ePI, and adds semmantic annotations to it.
This repository serves as an skeleton for a preprocessor service. It is written in typescript and executes an example semantic annotation, adding a simple tag. The preprocessor must add semmantic annotation to the package leaflet sections of the ePI. No other field in the ePI can be edited.
In this example, the preprocessing is done in the src/controllers/preprocessing.ts file, in the addSemmanticAnnotation function.
The hackathon participants may write the preprocessor in the way that best suits for them. Participants can use any programming language, framework or technology. The only thing that is mandatory is that the preprocessor serves an API that is compliant with the OpenApi Specification within this repository. Also, the service must listen for HTTP connections on port 3000. Note that this service will not be accessible over the internet when deployed in the Gravitate Health infrastructure, and will be an internal service that is used via the Hackathon web interface.
Participants must provide the image name of the preprocessor to the Hackathon organizers and deployment is automatized.
Participants must fork this proyect into their personal github account.
The way the preprocessor is deployed in the infrascturcure is done with a Github action, which is included in the repository. The action can be found at .github/workflows/docker-image.yml, and it builds a Docker image with the syntax ghcr.io/GITHUB_USERNAME/REPOSITORY_NAME, tagging the latest version of the image as latest, and then publishes it to ghcr.io (Github container Registry). The name of this image must be provided to the Hackaton organizers so they can deploy a service running the developed preprocessing service to be tested within the infrastructure. Participants are advised not to edit this Github Action.
Once the preprocessor is deployed to the infrastructure, the name of the preprocessor will be presented in the Hackathon frontend as preprocessing-teamN, being N the name of the team.
- Create the following resources:
kubectl apply -f kubernetes-yaml/001_preprocessing-service-example-service.yaml
kubectl apply -f kubernetes-yaml/002_preprocessing-service-example-deployment.yamlIn order to be discovered by the focusing manager, the service.yaml needs to include the following selector in the spec field:
metadata:
labels:
eu.gravitate-health.fosps.preprocessing: "true"NOTE: This service does not need to be published to the internet, so no gateway config is needed to proxy any petition. This is an internal service.
Service will be accessible internally from the kubernetes cluster with the url http://preprocessing-service-example.default.svc.cluster.local:3000/preprocess
This project is distributed under the terms of the Apache License, Version 2.0 (AL2). The license applies to this file and other files in the GitHub repository hosting this file.
Copyright 2022 Universidad Politécnica de Madrid
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
- Guillermo Mejías (@gmej)