HomeModern
Architecture
Humans
Inside
Prime
Time
Settings
Guest
Flow Machine
Processing in continuous motion, handsfree. Inbound and outbound. Inside and all around. The operating principle is "keep moving". A machine that keeps chugging along.

Process flows mapped. A machine with many definable parameters. To be configured for each situation, each individual, each group. Well controlled access and permissions. With constant monitoring: Volumes and throughput, end-to-end process, action and outcome models. Information states, transformations managed. Handsfree, measured.
Platform
Birdseye
Robots
Lots of little bits of logic launched and operating away, as part of a robot ecosystem. Types for every work group, configurable, working together within lanes and operating principles. Process, practice, exceptions, handling guidelines inside. Knowledge capture, alignment and agreement.

Gateway robots monitoring the flow inbound and request. Processing robots that constantly look for work to do. Robots that watch. Exceptions to handle. Robots that keep a schedule for outbound information, funds, reports.
Prototype Robot Control
Unified Information
Concept: truly integrated information cuts out the need for large chunks of extraneous processing, to utilize powerful techniques.

Actually Use the Database Power - letting it operate, using the power of a relational database. Enterprise relations.

Modern Model - liberated from ancient, no-longer-correct technology platitudes, integral relationship with business processes. All the information, assumes anything valuable to the organization is inside the data model. All in one place. Simplified structure, business concept alignment, and language. Entity completeness (example: contract), fully decomposed and encoded, leveling or multi-dimensionality. No Data Movement, relational interoperability in the platform.

Advanced relationships, including fuzzy, overlapping, multi-pass, conditional, flexible levels, and multi-axis dimensions.

masterfiles, health information, reference, transactions, system (work queues, logs, events/triggers). Greatly reduced tables - from Meaningful Code Values, elimination of reference tables, cutting duplication/overlapping variations, smoothing/shrinking/leveling/generalizing, DB unified and complex relationships, workgroup data domains. Business rules encoded in data content.

External standards aware, capable, but not defined by them. X12, FHIR, HL7

claim - as received, enrichment, department sections (needed to pay, also situational medical, FWA, audit), adjudicated
items
tags (dept, current or retro, can be used for cohorts, types block/hold, approve, working values, messages), also tag clearing

Proto Entity Relationship Tool Proto CLAIM
Internals
User Experience
Very different major activities supported - visualizing the health plan and operating controls not designed for massive data entry

Distilling the operational flow of an entire health plan to communicate? How to level functions and operational characteristics, representing layers and complexity? Dynamic, real-time. What are the measures with which to see the entirety? Customization models beyond dashboard and widgets, enhanced comprehension and engagement?

Process orientation, not structured around DB

functional, content dense, maybe a little boring

Wireframe elements - Header (menu, auth), Body (full for content, use of space, scroll down and left if needed), Footer

Page types - pseudo-graphical diagrammatic process, dashboard/console, list (views, controls, 100 lines + scrolling), form

Validations loop. "Sloppy Fix" technology.

Visible Data Meaning - One level of abstraction removed, buttons show data, multi-word data values, no codes required for search (but can as an option)

Flat surface design concept - removes code complexity

Use what's there - example: browser has controls, no need to be recreated

I-Beams - Authentication, Logging, Meta-Transparency, comment functions for all windows

meaningful use of CAPITALS and Title case, bolding, underlining and italics

user communication - message areas, action confirmations, error messaging

Symbology & Colors

field colors - meaning of background, foreground text, boxing, error messages
information note, click-for-more, click-to-change

Handmade Codebase
One set. Crafted, well reviewed and understood code. Bare, just what's needed. Shared, active. Only one representation, combining logic, documentation, commenting, and planning. The sustainable foundation for health plan operations.

A unified coding architecture. One style throughout, standards, examples, team conventions. Native code only? Strict and simple. Do what comes most simply. Without adornment. Cherishing the code. Supportable. Resources available. Can we develop a design/development mix that with the least amount, most understandable code, delivers excellent grade function and modern interface.

Examining the essential part in the code itself. Micro and macro. What's the logic look like if you boil it down? Once you remove the extraneous and the layering? Streamlined, each section, line, character and space has a function. Naming for meaning. Performing Minimalism - least code for most function. SkinnyCode? SimplyCode? pixie vanilla? A distinctive and recognized style.

Amplified logic. Doing more, clearer/clarified. Powerful, visible algorithms. Enabled advanced methodologies. Logic baked in. Subject matter expertise inside. More control/options/methods.

Coded for a large enterprise, used by thousands and changed by hundreds over decades. Reflecting the value of people resources, knowledge retention and transfer. An organization asset, expressing the processes and representations (electronically) of the organization with others. Coded assuming it will be in use in thirty years.

Accessible the first day on the job. Baked-in knowledge transfers. The code more accessible. Knowable. Teachable. Participation, involvement in the code from many functional and operational areas, not just technologists. The kind of code that is the topic at a meeting.

Codebase Tool Idea
Security
this architecture is more secure, safer, no one touches the data, guaranteed processes, defined exceptions

everything tracked

security in the database

auditable, data change state managed, built-in audit trail
Enterprise Scale
Designed for 10 million or more members. modern hardware, DBMS, internal cloud

plain vanilla, native capabilities, easy to replicate, and staff for
extraneous processing, unneeded data movement removed, dramatic change to scale curve

mirror DB

multi-instance sync
Present And Future Rights
Control of the platform, rights to make it whatever. Special sauce, proprietary ideas. Different directions from standard. New robots - work in the ecosystem (examples: custom algorithms, in-and-out changes, two robots dance, police robots). Extensions. Intermix new and base code.