{'fraction_non_alphanumeric': 0.044538706256627786, 'fraction_numerical': 0.0, 'mean_word_length': 4.863354037267081, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
The role of modeling in clinical information system development life cycle.

A model is an abstraction of some "thing" (e.g., object, system, process, phenomenon) in our world that we create in order to understand it better. Models can be physical (e.g., an architectural model of a building, a prototype of a user interface), mathematical (e.g., a model for predicting the weather, for estimating population growth), or conceptual (e.g., a clinical algorithm, the logical relationships between data items in an EMR). Models can be used to describe an existing complex real-world object or phenomenon, or they can be used as a vehicle to design a manmade object or system. While conceptual models can also be specified in narrative, in this discussion we address conceptual models that have a symbolic representation with a diagrammatic notation. Thus, conceptual models specify objects or processes, their properties, and their relationships.