Distributed Identity Assurance - Revision history

Tomjones: /* References */

2020-01-10T21:38:44Z

References

2019-12-25T19:50:32Z

Actors

← Older revision		Revision as of 19:50, 25 December 2019
Line 17:		Line 17:
	#Actor: Existing provider of health care services. (Source of Identity Proof and later of patient's PHI.)		#Actor: Existing provider of health care services. (Source of Identity Proof and later of patient's PHI.)
	#Actor: Referred provider of health care services. (Sink of Identity Proof and later of patient's PHI.)		#Actor: Referred provider of health care services. (Sink of Identity Proof and later of patient's PHI.)
	Note that it is possible that the patient's ~~guardian~~ (parent) is acting on the patient's behalf in this use case, but that should have no appreciable impact on the flow described here.		Note that it is possible that the patient's [[Guardian]] (parent or other) is acting on the patient's behalf in this use case, but that should have no appreciable impact on the flow described here.

	==Preconditions==		==Preconditions==

2019-12-20T17:39:05Z

← Older revision	Revision as of 17:39, 20 December 2019
(No difference)

2019-12-09T18:15:11Z

Results

← Older revision		Revision as of 18:15, 9 December 2019
Line 43:		Line 43:
	Accepted Risks:		Accepted Risks:
	#The patient loses the paper allowing some other person to attempt to steal their identity - mitigated by sign up process as described.		#The patient loses the paper allowing some other person to attempt to steal their identity - mitigated by sign up process as described.
			#The patient's phone becomes their authentication method that can be stolen - mitigated by some authentication to enable the phone and some gesture to show presence and intent.

	Post Condition:		Post Condition:

2019-11-21T19:32:13Z

Context

← Older revision		Revision as of 19:32, 21 November 2019
Line 5:		Line 5:
	*This concept of [[Distributed Identity Proofing]] is described here as a use case for attaining IAL2 identifier assurance in a [[Trustworthy Healthcare Ecosystem]].		*This concept of [[Distributed Identity Proofing]] is described here as a use case for attaining IAL2 identifier assurance in a [[Trustworthy Healthcare Ecosystem]].
	*This concept will be formalized in a "Distributed Identity Assurance Specification" in Kantara.		*This concept will be formalized in a "Distributed Identity Assurance Specification" in Kantara.
			*Comments on this page or on the specification may be entered as issues on the [https://github.com/TomCJones/DistributedAssurance GitHub page for Distributed Assurance].

	===Goal===		===Goal===

2019-11-19T22:04:01Z

Actors

← Older revision		Revision as of 22:04, 19 November 2019
Line 13:		Line 13:
	#Actor: Patient of one healthcare provider seeking services at another (refereed) provider.		#Actor: Patient of one healthcare provider seeking services at another (refereed) provider.
	#Actor: Patient's [[Phone as Health Care Credential]]		#Actor: Patient's [[Phone as Health Care Credential]]
	#Actor: ~~Verifier~~ of claim with Identifier.		#Actor: Attestor of claim of high assurance with provided Identifier (aka CSP).
	#Actor: Existing provider of health care services.		#Actor: Existing provider of health care services. (Source of Identity Proof and later of patient's PHI.)
	#Actor: Referred provider of health care services.		#Actor: Referred provider of health care services. (Sink of Identity Proof and later of patient's PHI.)
	Note that it is possible that the patient's guardian (parent) is acting on the patient's behalf in this use case, but that should have no appreciable impact on the flow described here.		Note that it is possible that the patient's guardian (parent) is acting on the patient's behalf in this use case, but that should have no appreciable impact on the flow described here.

2019-11-19T19:57:15Z

CSP Validation of Record Locator DOI

← Older revision		Revision as of 19:57, 19 November 2019
Line 107:		Line 107:
	signature of CSP		signature of CSP
	encrypted for PCP		encrypted for PCP
			}

			===Confirmation from the EHR about the DOI===
			{
			doi:
			iat:
			status:
			signed by the PCP
			encrypted for the PCP
	}		}

2019-11-19T19:53:41Z

Workflow

← Older revision		Revision as of 19:53, 19 November 2019
Line 60:		Line 60:
	# Messages are formatted as JSON strings.		# Messages are formatted as JSON strings.
	# The Document Object identifiers (doi:) are formatted using Android app rules, ie us.trustregistry.{opaque URL safe ASCII strings} where the first part is the base (or authority) address of the organization that created the document. An alternate would be a url.		# The Document Object identifiers (doi:) are formatted using Android app rules, ie us.trustregistry.{opaque URL safe ASCII strings} where the first part is the base (or authority) address of the organization that created the document. An alternate would be a url.
			# iat = time at which document was issued in Unix epoch format (a 64 bit number of seconds since 1970-01-01 00:00:00)

	===The Format of the [[Distributed Identity Proofing]]===		===The Format of the [[Distributed Identity Proofing]]===

2019-11-19T19:50:56Z

Workflow

← Older revision		Revision as of 19:50, 19 November 2019
Line 59:		Line 59:
	* Some conventions used here are:		* Some conventions used here are:
	# Messages are formatted as JSON strings.		# Messages are formatted as JSON strings.
	# The Document Object identifiers (doi:) are formatted using Android app rules, ie us.trustregistry.{opaque URL safe ASCII strings} where the first part is the base (or authority) address of the organization that created the document.		# The Document Object identifiers (doi:) are formatted using Android app rules, ie us.trustregistry.{opaque URL safe ASCII strings} where the first part is the base (or authority) address of the organization that created the document. An alternate would be a url.

	===The Format of the [[Distributed Identity Proofing]]===		===The Format of the [[Distributed Identity Proofing]]===

2019-11-19T19:30:32Z

Workflow

← Older revision		Revision as of 19:30, 19 November 2019
Line 56:		Line 56:

	==Workflow==		==Workflow==
	When patient goes to their phone there are several messages that need to be created.		* When patient goes to their phone there are several messages that need to be created.
			* Some conventions used here are:
			# Messages are formatted as JSON strings.
			# The Document Object identifiers (doi:) are formatted using Android app rules, ie us.trustregistry.{opaque URL safe ASCII strings} where the first part is the base (or authority) address of the organization that created the document.

	===The Format of the [[Distributed Identity Proofing]]===		===The Format of the [[Distributed Identity Proofing]]===
	The DIP will contain (typically on a single page of white paper):		The DIP will contain (typically on a single page of white paper):