npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@synanetics/messaging-processor

v3.2.4

Published

Processors to manage FHIR MessageHeader bundle workflows

Downloads

689

Readme

@synanetics/messaging-processor

Processors to manage FHIR MessageHeader Bundle workflows

Usage

const { preProcess, postProcess } = require('@synanetics/messaging-processor');
// use a required

Both preProcess and postProcess require parameters context and params. Please see the available types for further details

Replacement

It is intended that this package can be replaced by another. Any replacement must export two named functions preProcess and postProcess and they must adhere to the interfaces outlined below.

Pre Processing

preProcess

  • will receive params
  • must return results - see type ProcessorResult
    • message will be your modified request Bundle
    • additionalResources must be populated with any resources subject to create/update operations that are not already in the request Bundle. This is vitally important as failure to include this will result in removal of the modified resources entirely.

Post Processing

postProcess

  • will receive params
    • context - see type Context
    • params - see type PostProcessorMessage
      • message - this is the Response bundle being sent back
      • request - this is the original Request bundle - you will use this to determine flow hooks if necessary
  • must return results - see type ProcessorResult
    • message will be your modified response Bundle
    • additionalResources must be populated with any resources subject to create/update operations that were not already in the request Bundle. This is vitally important as failure to include this will result in removal of the modified resources entirely.