1,000 unpublished requirements later...

Exactly what I thought 11 months ago when I believed I would exercise the discipline necessary to moderate my everyday health-related experiences worthy of being Human Health Graph requirements. I did not write down 1,000 HHG requirements during the past 11 months but I did think of a few hundred I wish blogged. Not too long ago, I did upgrade to SparxSystems Enterprise Architect 9 (EA v10 was released this week) and develop 15 HHG Use Cases. Most of the year I've been hunting for catalogs, registries, lists, databases, and tables of biometric quadruples--biostructure-biosignal-biosensor-biostatistic. I've had no luck finding them thus far. I've haphazardly asked officials in government healthcare, CXOs in healthcare IT, university professors and germane technologists I have access to in my job. It's sad and funny at the same time how the human as a self-contained package of life is measured and observed throughout its life into postmortem for the purposes of scientific inquiry and commercial endeavor yet all those who take away measurements and observables do not have a platform to integrate those collections so they can be anthropometrically rendered in real-time (or not), possibly via an anthropomorphic display.

Requirements catch up

Ten differences between the nhumi product and my concept:

The person (patient) uses the app more than anyone else

there is a date-time control from conception to predicted or estimated death

the software interpolates or extrapolates with health data to the chosen date-time group

the humanoid is animated or simulated or reposed based on the Use Case and health data

the user manages health by entering goals, plans, estimates at the any level of resolution for any domain (mental, dental, physical, etc.) of human existence

the user manages health by rendering trends, patterns and changes in an isolated or correlated view via the humanoid and charts or graphs

the user manages healthcare by requesting services with an export of the condition that she signs before electronically sending to a broker or directly to a provider

the user manages health security by granting or denying access to providers who want to know more than the export given. N.B. the software recommends what should be exported if the PCM doesn't when ordering the referral

the software animates the humanoid with real-time feeds so your 180 bpm readout from your Polar heart monitor worn during track workouts drives an animation of your humanoid panting with a heaving chest cavity if you opened the application and went to full frontal view mode.

When I write humanoid animation, I mean the humanoid from your 3D body scans NOT some commercially available (stock) humanoid/avatar. So if you are wearing Polar heart monitors at 13- or 93-yo then your humanoid will resemble your closet 3D body scan to that age.

the software uses augmented reality technologies to render common healthy and unhealthy conditions when you point visible sensors toward yourself.

The AR episodes might be a key trigger for healthcare and self care. Self care being generic prescriptions to perform activities while well to regain levels of form or performance recently loss to inactivity.

the software tracks its usage and the cumulative (actual and estimate to postmortem) costs for health maintenance materiel and services.

Think of Business Analytics for the individual who might have a few hundred terabytes after a century of data collection and generation on everything related to his/her health.

LG-HU-FR-0001.001 Draft

The natural person's Lifegraph shall be initialized with the genotype and phenotype. The genotype and phenotype file formats shall be IAW TBD.

LG-HU-UC-0001.001

A requirement a day, right! Ok, here I go. First, let me explain the naming convention for the system requirements and use cases.

LG stands for LifeGraph
TG stands for TimeGraph
EG stands for EventGraph
SG stands for SceneGraph

HU stands for Human
MA stands for Manufactured
NA stands for Nature

UC stands for Use Case
BR stands for Business Requirement
AR stands for Architecture Requirement
RR stands for pRocess Requirement
FR stands for Functional Requirement
QR stands for Quality Requirement
PR stands for Performance Requirement
CR stands for Constraint Requirement

#### for 0..9 up to 9,999 requirements per unique combination of indices
### for 0..9 for up to 999 subordinate requirements to each 4-digit requirement

Please submit a comment when you read any requirement that does not have any of the following characteristics:

unitary (cohesive)
complete
consistent
non-conjugated (atomic)
current
feasible
unambiguous
mandatory
verifiable

11 months later

Well, I seem to be cruising along instead of cutting my teeth on the hard stuff that will make a difference sooner than later when it comes to LifeGraphs. My day job has exposed me to the world of Health IT from a process improvement perspective. I'm excited about the opportunity but usually get disappointed at the dearth of information from the client. Nonetheless, these engagements gets me access to practioners who I would never get to chat about Lifegraphs.

I still believe there is a Blue Ocean for designing a Lifegraph that takes a century to make your own and master your self awareness. Selling that in a 30 second commercial during the Super Bowl and every other World Sporting Event will take some serious thought. I mean how do you create a commerical to appeal to everyone in vivo to 115 yo and recently postmortem?

I drew the following to illustrate the sections of the LifeGraph and to discuss how the Health IT solutions on the market today haven't had or just don't address health planning (not insurance plans!) like estate or wealth planning. I think that is a big gap to be filled if I can create the image of planning health is cool and worth the effort while not coming off as an elitist or someone who thinks they will be an Olympian or World-class athlete.



I am editing the IEEE Virtual Components Standard.

I am drawing UML diagrams for the Strategy Markup Language committee.

I am going to write a LifeGraph requirement a day no matter what!

New Year's Resolutions - 2011

0. Write the Leading Edge Report I described in my 2008 LEF Grant proposal.
1. Write the Metaverse for National Intelligence paper for the DNI/CIO
2. Request a X3D version every good and service I purchase in CY2011.
3. Write the EmployeeGraph Concept paper I discuss on CSC's C3 site.
4. Author three X3D scenes using all the nodes in H-Animation and ... specifications
5. Author three H3D scenes using all the API elements
6. Author three OpenAL scenes using all the API elements
7. Submit a feature paper for a Virtual Reality publication that's peer reviewed
8. Specify the LifeGraph requirements
9. Analyze the gaps between the LifeGraph specification and COTS products

2 years ago I started my journey with X3D and found LifeGraphs

X3D 4 Enterprise Applications

View more webinars from William Glascoe.