> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.medicomp.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.medicomp.com/_mcp/server.

# Quippe Data Model

The Quippe® data model was designed to present not only the right information, but at the right level of clinical detail, at the right time for the provider, while capturing structured and standardized data needed for billing, quality measures, reporting, and interoperability. 


## Concepts as Clinical Data

MEDCIN® concepts are at the core of the Quippe data model. Concepts are clinical in nature and have meaning in and of themselves – words and phrases clinicians use to describe the patient encounter.

In the patient chart, the provider sees phrases with clinical meaning, so they can document in the language of the encounter rather than translating their thinking into a billing taxonomy. Quippe concepts include associated synonyms, so findings can be located using a variety of phrases. 

Each concept is associated with properties that qualify those clinical phrases, making them actionable both for the provider as they treat the patient and within the broader ecosystem. 


## Concept Structure

At the core of Quippe is the MEDCIN clinical terminology, with 450,000 clinical concepts, organized into six domains. Each MEDCIN concept is a pre-coordinated clinical proposition: a unit of clinical meaning designed to make sense to a clinician at the point of care, not just a code.

- **Permanent, non-semantic identifiers**: Every concept is assigned a unique numeric identifier that's never reused or removed, and carries no semantic meaning of its own.

- **Poly-hierarchy**: Beyond the navigational hierarchy used for terminological browsing, MEDCIN concepts carry diagnostic relevancy links that connect a single concept to thousands of relevant diagnoses, independent of where that concept sits in the navigational tree.

- **Parameters**: Prefixes, modifiers, and statuses let a single MEDCIN concept represent different clinical realities in context –– for example, distinguishing a patient's personal history of breast cancer from a maternal history of the same diagnosis, and further specifying stage or status (e.g., Stage 2, in remission).


### Concept Properties

Each *concept* has pre-defined properties that provide the additional data needed for coding, billing, reporting, organizing, and filtering data in the chart and note. 

  - **Section and Group ID**: Where to place the concept in the documentation
  - **Specialty Codes**: Cardiology, Endocrinology, Infectious Disease, Pediatrics, etc.
  - **Severity or Complexity**: Used in E/M coding
  - **Risk Codes**: Level of medical/surgical risk to the patient, used in E/M coding
  - **Code Mappings**: Maps concept to other standard terminologies (SNOMED CT®, ICD-10, CPT®, LOINC®, etc.)
  - **Phrases**: The statement is either asserted or denied based on the patient status


### Finding Properties

Once a concept is added to the patient record it becomes a *finding*. Findings represent the patient's current condition. Finding properties are the metadata that allow the clinician to further characterize the concept based on the patient context at that point in time.  

  - **Onset**: Date and time the finding occurred
  - **Value**: Numeric or alphanumeric value for findings with a measurement, and normal range for the term
  - **Unit**: Unit of measurement in which the Value is expressed
  - **Prefix**: Finding qualifier that is prefixed to the finding (assessment of, history of, allergy to, etc.)
  - **Family History of**: Distinguishes a finding associated with a family member rather than the patient 
  - **Modifier**: Descriptor that provides additional meaning and/or context (e.g. mild, moderate, severe, etc.)
  - **Notation**: Free text note that can be added to the finding

 
## Translating Across Standards

Quippe acts as a universal translator, extracting mineable clinical data from free text and modeling bi-directional crosswalks from one standard code set to another. One single clinical data foundation serves documentation, billing, quality, interoperability, and AI. See [MEDCIN Clinical Terminology](/core-concepts/medcin) for how this translation works, and [Interoperability](/core-concepts/interoperability) for how this supports data exchange. 


## Learn more

For questions about capabilities beyond what is covered in this preview, or to discuss requirements for your use case, [request access](https://medicomp.com/request-access/) or contact our team. 

<br />
<br />

*Quippe, MEDCIN, Quippe Clinical Knowledge Graph, Clinical Lens, and Alchemy are trademarks and registered trademarks of Medicomp Systems.*   
*All other trademarks are the property of their respective owners.*