Re: Request for user story - Store basic identity credentials

On 5 May 2014, at 11:27 am, Manu Sporny <msporny@digitalbazaar.com> wrote:

> This is a general request to the Web Payments CG. We need help writing
> use case descriptions. If one or more of you could write out a simple
> user story for the following use case, it would help us immensely:
> 
> USE CASE: Store basic identity credentials and payment provider
> information on the Web in a way that is easy to share with various
> merchants given authorization by the owner of the identity, and that is
> easy to synchronize between devices.
> 
> This use case was approved last week during the telecon[1]. An example
> of such a story can be seen at the following link:
> 
> https://web-payments.org/specs/source/use-cases/#proof-of-purchase-and-verifiable-digital-receipts
> 
> Don't try to coordinate if you should be the one to write it or not.
> Just write it and send it back to the list. The editors of the use cases
> document will pick the best one and integrate it.
> 
> Please fill out the template below by replying to this email. If the
> description is good, the text you write will be folded into the Web
> Payments use case document[2], which will guide the technical work we'll
> be doing over the next few years.
> 
> ----------------------------------------------------------------------------
> 
> USE CASE
> --------
> 
> Store basic identity credentials and payment provider information on the
> Web in a way that is easy to share with various merchants given
> authorization by the owner of the identity, and that is easy to
> synchronize between devices.
> 
> DESCRIPTION (aka User Story)
> ---------------------------
> 
> [[2-3 paragraphs outlining the use case]]
> 

TELEHEALTH

As exampled in the videos [1] Telehealth sessions can take-place at home, or in traditional clinical environments.  Sessions can be booked, or ad-hoc - or a mixture (i.e. the full video of the cystic fibrosis user-story, results in the clinician adding a psychologist to the call as a constituent of holistic care procedures).

In theory; several different use-cases exist. An individual may seek specialist care with a new medical specialist whom they do not know.  Specialist Clinical experts not being accessible locally, or perhaps they have a clinical expert they prefer to see, but have moved elsewhere. 

In Australia, our health-care system pays health-care providers via a federal government health program entitled ‘medicare’.  Whilst this cost may not meet the full cost of the consultation (i.e. end-user may still need to pay a constituent of the bill) these payments between the federal government and healthcare providers - make healthcare affordably accessible to many australians. 

Generally, prior to tele health, reception at the clinic would print a form and obtain a signature from the patient prior to their departure.  Medicare details would be obtained to do this, and the transactions (subject to the signed agreements) would be carried out electronically.  However, with the advent of tele health becomes the issue that the patient is not available to sign the document and therefore enact payment on the spot, for the health-care provider.

One way of dealing with this is via email [2] 

Another issue that is exhibited in the medical profession - with great misfortune - are practices where doctors may seek to exploit this billing process, and bill medicare without having provided valued consultations to patients (or any consultation, apparently, in some cases…) 

To fight this problem (and others) the government now seeks to introduce a nominal payment for citizens [3] 

[1] http://www.youtube.com/watch?v=1tr5cm4oUGs&list=PLGBV4p3WIjFHP7bgzUyCLiqNB1ON8u0UF 
[2] https://www.medicareaustralia.gov.au/provider/incentives/telehealth/information-bulk-billing.jsp
[3] http://www.abc.net.au/news/2014-03-06/australians-defrauding-medicare-hundreds-of-thousands-of-dollars/5302584

> REQUIREMENTS (optional)
> -----------------------
> 
> [[Technical requirements of the system given the use case]]
> [[Don't worry about this part if you don't know what to write here]]

TeleHealth is best carried out with SIP, WebRTC but often in reality via Skype.  A web-payments standards solution would need to consider the capacity to create payment functions between participants (from multiple payment sources such as; the patient, the patients parent, the federal government, a private healthcare insurer) 

Perhaps an ontological target for service fees by period; minutes/hours/days/weeks/months

perhaps a method to ‘sign’ that an event occurred?  - i imagine, tracking whether the call was an ‘active valid’ call, vs. just an open call - not our problem.  the ability to create timestamps and label those timestamps might be a method?  

potentially; the ability for an ‘authorised practitioner’ to access healthcare information in relation to the call - is one challenge.  

Another aspect is that the caller, may have identified that practitioner minutes before a consultation occurs.  in-such cases, there is little tangible trust - yet, the hippocratic oath [4] would still apply (therein, the desire for a clinical professional not to deny treatment if required by the person seeking help.).

[4] http://en.wikipedia.org/wiki/Hippocratic_Oath

> 
> ----------------------------------------------------------------------------
> 
> -- manu
> 
> [1] https://web-payments.org/minutes/2014-04-30/#125
> [2] https://web-payments.org/specs/source/use-cases/
> 
> -- 
> Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
> Founder/CEO - Digital Bazaar, Inc.
> blog: The Marathonic Dawn of Web Payments
> http://manu.sporny.org/2014/dawn-of-web-payments/
>