We would write a scaling server with Go on one of these public datacenter 
services. A manufacturer or distributor could register a UUID with us that 
is then verified through us by the pharmacy and consumer later. The 
pharmacy/consumer has the aztec barcode with the UUID, manufacturer 
cryptographic number, and distributor cryptographic number, so maybe we’re 
talking about two barcodes and a distribution standard.

Capturing already-scanned UUIDs may mitigate some copying, or at least 
indicate to the consumer or pharmacy that there's a copier problem.

Would the picture be processed by the server or by the client? How are 
existing Go libs for these aztec barcodes?

We'd need an authentication system for people or organizations registering 
UUIDs.

Could we have data tied to the UUID on the target distributor, target 
pharmacy, or target consumer?

“when we are looking at the source, we are looking at the stock cards, and 
also cross-checking with the delivery sheet to confirm this is what is 
being supplied”

In Kenya one distributor handles 40% of the country’s medicine supply. They 
have a QA process. But: “Many small storefronts buy from unauthorized 
distributors” - we’re not fixing this part except maybe through consumer 
knowledge (“we’re expecting the bar code”). PBS pointed out barcoding as a 
solution put into place already.

Thomas Woods of the World Bank talks about “rapid authentication devices”. 
As a group of app implementers I think we’d be best served by partnering 
with an organization with connections to the industry instead of directly 
with manufacturers or distributors. Who can we talk to?

I think this is on-topic for golang-nuts as we’re discussing a use case of 
Go and programming: building global information services. Maybe somebody 
can use our designs for their Go service later.

Matt

On Sunday, December 24, 2017 at 4:14:22 PM UTC-6, Tamás Gulácsi wrote:
>
> A signed nonce is enough to prove private key ownership - as far as it 
> can. Replay attack is unavoidable.
> Uuid is useful for tracking.
>
> But how feasible is this? Here (Hungary, Eastern Europe) we have drugs 
> packed in preprinted boxes, and the serial ids are just pushed into the 
> paper.
> Per-box personalized aztec code would push up the packaging price 
> significantly.
>
> But for dangerous/pricey drugs this may be acceptable.
>
>
> But this is not Go related yet, so maybe we should move this to somewhere 
> else.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to