📄️ Introduction
This document provides essential guidance for developers creating Preprocessor services within the Federated Open-Source Platform and Services (FOSPS) environment, particularly focusing on the annotation process for Electronic Product Information (ePI).
📄️ Develop a Basic Preprocessor
You will need to produce a Docker container that implements a specific HTTP REST interface. See the OpenAPI specification for complete details.
📄️ Basic ePI Annotation
Semantic annotations in ePIs are embedded syntactically within the FHIR resource using markup language, specifically leveraging the HTML already present in the ePI's narrative content. The core component for achieving this is the HtmlElementLink Extension.
📄️ Deploying Preprocessors
Preprocessors are pluggable software services within the Federated Open-Source Platform and Services (FOSPS) that automatically annotate Electronic Product Information (ePIs) for use in the focusing mechanism. They read the Package Leaflet of an ePI and add semantic annotations to the text, preparing the raw ePI resource to become a preprocessed ePI (p(ePI)).
📄️ Documentation: Testing Preprocessor Services
The primary objective when testing a preprocessor service is to ensure that it successfully adds semantic annotations to the Electronic Product Information (ePI) content, transforming a raw ePI into a preprocessed ePI (p(ePI)), while strictly adhering to compliance rules regarding content modification,.
📄️ Example Preprocessors
here are some example preprocessors:
📄️ Implementation Strategies for Preprocessors
Preprocessors are fundamental pluggable modules in the Federated Open-Source Platform and Services (FOSPS) focusing mechanism. Their core function is to systematically analyze and enrich raw Electronic Product Information (ePIs) by adding semantic annotations, transforming them into preprocessed ePIs (p(ePI)).