Overview
New? Start here.
Value Creation
Sales Model
Governance Model
Delivery Model
Profile Model
Engagement Model
Revenue Recognition Model
Support Model
Concepts
What is SafeCDx?
Existing Standards as Foundations
Interoperability as a Fundamental Design Pillar
How a Connected Test gets registered and validated on the Platform
Smart Contracts, Consent, and Consent Enforcement
How an Actor gets registered and verified on the platform authenticated, authorized, and audited?
How is data exchange governed between Actors, Services, Applications, and Connectors?
How a Connected Test Transaction Works
Solution Guides
Embedded Connected Diagnostics
Care Automation
Return-to-Lab
At-Home Care
Novel Pathogen Early Detection
Primary Digital Care
Organization and Billing
Login to Safe Health
Organization Setup
Create Organization
Configure Organization
Workspace Setup
Configure Workspace
Create Workspace
Safe Health APIs
Create Service Account
How To
Make API Calls
Control API Access
Design
Architecture vs Design
Design Challenges
Design Goals
Standards Based Design
Data Standards
Design Patterns
Clinical Serialization Standards
Security Standards
Serialization Standards
Terminology Standards
Transport Standards
Stereographic Projection
Event-Driven Design
Cultural-Dependent Design
Service Interface Design
Contract-Based Design
Distributed Transaction Design
Testability Design
Code Generation Design
Science of Great User Experiences
Platform Architecture
CDx Conformance
CDX Model Conformance
CDX Server Conformance
CDX Registry Conformance
CDX Modeling Notation Conformance
CDX ESG Conformance
CDX Sidetree Conformance
Data
Bytes
Wire Protocol
Data Model
Spec Entity
Spec Clinical Entity
Spec Meta Model
Spec Clinical Meta Model
Spec Resources
Ontologies
Lifecycle
Network
Personal Area Network (PAN)
Local Area Network (LAN)
Wide Area Network (WAN)
Jurisdiction Area Network (JAN)
Transports
Transports
Transaction Management
gRPC
HTTP
GraphQL
Security
Our Approach to Security
Privacy
Consent-based Decryption
Performance
Threading Model
Extensibility
Interoperability
Systems
System of Record
Systems of Differentiation
Systems of Engagement
Configurations
Services
Connectors
Systems of Innovation
System Lifecycles
Value Planes
All Planes
Collapsed Planes
Customer Plane
Business Plane
Gateway Plane
Mesh Plane
Workload Plane
Data Plane
Event Plane
Profile Plane
Control Plane
Federation Plane
Hardware Plane
Network Plane
Physical Plane
Journeys
Actors
Users
Patients
Organization Representative
Providers
Partners
Service Accounts
System Owner Journey
System Developer Journey
System Governance Member Journey
System Consumer Journey
Patient Journey
Medical Device
Solutions
Applications
Block Chain
Visual Design
Glossary

User Error

A User Error is an error made by the human User of a complex system, usually a computer system. Also known as PEBMAC¹, ID-10-T, PICNIC², or IBM Error³. One should replace the User and try again.

There is no such thing as a User Error. There is nothing that a User should be able to do that would make the system behave unexpectedly. What it really means is that the system doesn’t have proper Exception Handling, or that the system was not designed well enough, only taking Happy Paths into account, for example.

Problem Exists Between Monitor And Chair (PEBMAC) ↩︎
Problem In Chair, Not In Computer (PICNIC) ↩︎
Idiot Behind Machine Error (IBM Error) ↩︎