MMIS: Terminology

Question -

I am reviewing records in my system and am wondering if you can detail what each of the terms being used in the system mean to me.

Can you please define some of the terms that I am seeing in the system so I better understand?

Answer(s) -

    Spend Transaction / Transfer of Value:

Any interaction with an HCE that could be construed as having monetary value attached included but not limited to direct payments, provided goods or services and indirect values. This is referred to as a Spend Transaction (ST) in MediSpend

   Nature & Purpose:

Textual details of the transfer of value that are then translated to the specific jurisdiction reports including the Nature of the ST, the Purpose of the ST and the Role the Covered Recipient in regards to the ST. NOTE: This can be in the form of actual text, a General Ledger (GL) code, or a reference code/number from the client

   Spend Owner:

The user within MediSpend that is responsible for the ST.

  Home System ID:

The unique ID in MediSpend for the ST. This can be auto-generated by the system or supplied from the Manufacturer.

  Report Group:

Group within a client’s system that is the primary group for the report that is being generated.

  Role:

Ability to perform specific tasks within the system. The roles could include Create, Read,
Update and Delete (deactivate) capability in association with a specific module or content
item.

  Security Profile:

A combination of many user roles organized into a single profile for a specific type of user.

  Propagate:

In our case propagation is allowing a user or product in a single group to also be included in all groups below it in the hierarchy

Covered Recipient (CR):

A Covered Recipient is a person or organization that is reportable under the governing body’s transparency reporting. The definition of a CR can change depending on the governing body. For example a covered recipient for CMS includes Physicians, Dentists and Teaching Hospitals but Nurses are excluded. Vermont, Massachusetts and other jurisdictions consider Nurses a “Covered Recipient” MediSpend historically has used this as a generic term to describe an individual or organization that might receive a transfer of value from a Manufacturer.

Often referred to as a CRID, CID, Covered Recipient ID, or Unique client identifier.

  HCP vs HCO vs HCE

Heath Care Provider (HCP) refers to individuals,

Health Care Organization (HCO) refers to hospitals, clinics and other organizations.

Heath Care Entitles (HCE) is a term coined by MMIS as a single term for all HCPs, HCOs and non-reportable individuals and organizations.

  Customer Master:

A collection of all the HCEs a client is working with in a centralized database for use in MMIS applications.

  Affiliation:

An affiliation is an organization that and individual works for or is associated with. This affiliation can be but doesn’t have to be an HCO in the client’s customer master.

  Flat File (Pipe delimited, Comma Separated (CSV), Excel etc.):

A single file that contains data organized in rows/columns for import

  ETL:

ETL (Extract, Transform and Load) is a process in data warehousing responsible for pulling data out of the source systems and placing it into a data warehouse

  FTP / SFTP:

Stands for File Transfer Protocol, or Secure File Transfer Protocol. It is our primary method of accepting files from clients who have an ETL.

  Delimited:

The separator between fields provided in a text or CSV file. This is typically a comma, pipe or semicolon character

  Asynchronous Reporting:

Parallel programming in which a unit of work runs separately from the main application thread and notifies the calling thread of its completion, failure or progress. This reduces the amount of time reports are in queue for generation.

  Worker Server/Cluster:

Separate servers from the application ensures that the work for generating extracts and reports does not impact the user’s
ability to navigate and use the system.

  Replica Database:

The primary database server is mirrored as a read only server in order to distribute read and write heavy workloads