MacroHealth Internal

Total dollar amount of processed claims.

A mechanism for transferring runtime documents from exactly one producer to a consumer in another transaction

A persistance object for metadata that may contain files and documents.

A composite operation contains exactly one shovel flow fragment and explicitly defines its input and output connections. Composite Operations also declares configuration that can be used to customize the Shovel Flow Fragment. Composite Operations generally implement a reusable business-focused function.

A composite operation interface defines only input and output connections. The interface does not contain any implementing flow fragment. Composite Operations Interfaces allow a developer to build flows using Composite Operations however only require their implementations to be specified at deploy time.

A Composite Operation Library is a collection of Composite operations. It is a simple set of Composite operations. A Composite Operation Library does not define and connections between its containing Composite Operations. Composite Operation Libraries often contain related Composite operations, for example a network Library will contain all operations related to a specific network

A field in json a document that contains all the information the is saved while the file is moving through the flow and that serves to make decisions at certain stages of that flow.

A raw file supplied by the vendor, or a NIFI flowfile in single mode

or

A document which is a single json representation of a document in standard runtime. Documents are contained within a Context Document. A document also defines a type and associated metadata for the documents.

Claims where the eligible amount is equal to $0.

Single json representation of a document in standard runtime. Documents are contained within a document context. Document also defines a type and associated metadata for the documents.

This is the public representation of a flow. It is create in the Platform UI and exposed via the Platform APIs. It is made up of several domain model components. It defines the flow as seen in the UI and also includes required details in order to draw it in the UI.

Total eligible portion of processed claims, which includes the discount.

A widget is a reusable and constrained bit of processing functionality. In the MacroHealth platform widgets are represented by draggable icons that can be combined to create more complex processes.

A Shovel Operation can be represented by a widget in the Flow Builder UI.

Total dollar amount of Network provided discounts.

Percentage of gross discount among eligible amount (Gross Discount / Eligible Amount)

An Implementation is an engagement between a payer macrohealth and one or more networks

Medical claims from institutions that require overnight hospitalization (e.g., hospitals)

An integration is a collection of platform flows that build a complete document processing solution.

Can be defined as a Java Script Object Notation file format that is used for sending, receiving and storing the data from the same or different systems in a network. It is generally used in the REST request and response application program interface (API) services.

Example

{
“Role”: “Patient”,
“Name”: {
“First name”: “Theo”,
“Last name”: “Davis”
}
}

Lifecycles refer to the stages in which a flow goes through: Development, Test, and Production.

This is the Nifi representation of the flow. It is made up of several NiFi groups and processors, however at the root a flow is encapsulated within a single NiFi group. A shovel operation node translates to several NiFi processors.

Medical claims from institutions that do not require overnight hospitalization (e.g., ambulatory care)

A flow is a core concept within the platform. A flow represents a transformation of a document. A typical flow is to read a document from a source (sftp, kafka, …) perform several operations/transformations to is and write the resultant document to one or more destinations (sftp, kafka, …). An integration is made up of many flows. Flows can also be chained, for example the destination of one flow can be the source of another flow.

Medical claims from professionals (e.g., individual doctor's office)

A Shovel Expression allows a user to calculate values where useful. Shovel Expressions are used by Shovel Operation in order to provide values to the Shovel Operation

A Shovel Flow Fragment is an subset of a complete shovel flow. It contains one or more connected shovel operation. However not all connection need to be defined. This is not usually something that can be deployed on its own.

A Shovel Operation is the simplest building block that can be used to build flows. Shovel Operations define configuration, inputs and outputs and are combined together in order to build more complex flows.

This is the Shovel representation of the flow. It is made up of several shovel operation nodes. A component within the domain model flow can translate into several shovel operation nodes.

Principal Tokens: generated by Auth Manager, for whom the service is making the request for:

Service Tokens: generated by the internal services themselves, identifies service making the request

A widget is a reusable and constrained bit of processing functionality. In the MacroHealth platform widgets are represented by draggable icons that can be combined to create more complex processes.

A Shovel Operation can be represented by a widget in the Flow Builder UI.