ePaper in Healthcare

In my eReading Reference Architecture I designed how ePaper Based eReaders (or tablets) could be used to help implement a decentralized Patient File. Extract from the Patient File Case:

"Rather than trying to centralize all Medical information within the various Data Centers (Hospitals, Mutuality, Doctor's practices...), this medical information could be stored on mobile patient's files stored on a simple eReader. This eReader would store all patient's health information: Medical records (radios, exam results), past and future subscriptions, past and present illnesses, allergies, blood type... The Patient would keep his medical record on the eReader USB stick. An archiving service would be proposed by the Government in case the eReader is lost or broken. Of course patient could backup their files at home on their PC on other tiers like Google Health."
On the eRRA website I have 2 diagrams illustrating the Patient File Scenario. If you are interested, ask for access here : http://www.appepaper.com/reference-architecture/get-access)


Here is an other example of using ePaper in healthcare: ePaper Patient Badges.

Fujitsu Creates First Ever E-Paper Patient Badges | Ubergizmo: "Fujitsu and Sapporo Shirakaba-dai Hospital have worked together to produce e-paper patient badges which for now they are currently aiming at just providing medical information as well as a queue number so patients will know when it is their turn, and will also help guide patients to the relevant rooms."

See also http://www.appepaper.com/epaper-applications/healthcare

Samsung’s Android tablets now showing up in schools, airplanes | The Digital Reader

After eReaders, Samsung’s Android tablets now showing up in schools, airplanes ( The Digital Reader). One year and a half ago it still looked like this :

How DiCoDE can be translated into an eReading Solution Architecture (eRRA)

Recently, at a Mobile Monday event, I heard about DiCoDE, a framework developed by Fabian Tilmant.
I immediately noticed some similiarities between DiCoDE and my eReading Reference Architecture (eRRA) method. The "eReading content life cycle" can be mapped to the DiCoDE model. In the eRRA methodology we also work on 2 additional topics: the Business Goals and the Entreprise/ICT Architecture.
DiCoDE complements the architecture by providing a kind of "Generic Media Business Process Template".
I might sound a little bit "Chinese" but it isn't. These are just techniques to make sure your new Media initiatives will succeed

• Achieve your business goals as a Media company
• Make sure you will reach the Consumer by a set of channels
• Develop a plan in terms of resources (IT Systems, People, Data, Entreprise/IT Architecture...)

Combinig DiCoDE and eRRA could achieve great results. Here would be a possible modus-operandi :

1. Defining the business goals (eRRA Methodology, KAOS or GOESIR Method)
2. Analysing the future Content Value Chain with DiCoDE
3. Determine the architecture required to implement the value chain (ex: new Portal, new Production Process...) and document them over the 4 eReading Tiers (Archimate Notation). This provides a TO-BE Architectural overview.
4. Compare the TO-BE Architectural overview with the AS-IS (what elements of the value chain do we have today ?) to provide a project plan

(Note the eRRA methodology can be applied on all kind of Media, not only on eReading. If the "eReader" is a Tablet, there is much more to do than just "read" on the "eReader Tier".)

In order to illustrate a litle bit step 3 I have taken the DiCoDE building blocks and drawn them in an Architectural Overview over the 4 eRRA tiers.

How DiCoDE can be translated into the 4 Tiers of the eReading Architecture

View more presentations from jfdeclercq.

If you want to give it a try (DiCoDE and/or eRRA), just contact us:

• Fabian Tilmant
• Jean-François Declercq

If you immediately want to know mode about the eRRA, you can get the eBook here :
http://www.appepaper.com/ereading
The DiCoDE ebook is not ready yet, so you'll have to point your browser here :
http://dicodethebook.wordpress.com/dicode-the-model/

Amazon gives you 70% ? Not always...

With my ebooks I thought I would have a 70% royalty. Amazon gave me only 35%.

I didn't get it until I saw this at the bottom of my KDP reports page:

"Note: 70% royalty option is only available for sales in the US, UK, Canada and Germany. Sales outside the US, UK, Canada and Germany receive 35% royalty. Please see Terms & Conditions for more details on how royalty payments are made."

I think I have to find another way to sell my ebooks in Belgium because on a consumer price of $13,79, I finally get $3.50... While I set the price at $9.9...

So if you want I sell you directly the eBook via Paypal. It will be cheaper for you ($10 instead of $13,79) and I will earn more.

Go here to order : http://www.appepaper.com/ebook/order

The HPub Format

Source : Foletto - https://github.com/Simbul/baker/issues/13#issuecomment-524407

Current HPub Draft 0.9 [2010-11-21]

1. Abstract

The HPub (HTML Publication) standard is a file format designed to release rich content books in a simple and manageable package.

2. The principles

We want a digital publishing format that:

1. Allows great designs
2. Allows both pixel-perfect and flexible reflowable publications
3. Is simple for authors
4. Is simple for parsers

3. The Spec

1. An HPub publication is a normal .zip file with ".hpub" extension. Unpacked books are allowed.
2. The content format must be HTML5.
3. It must contain at least one HTML file with extension "html".
4. If more than one HTML file are included, the pagination order must be alphabetical.
5. Any HTML file contained in subfolders must be excluded from the pagination order.
6. All the assets (CSS, images, JS, ...) must be included in the package and referenced relatively from the HTML5 files.