Current documentation for “Open Source Health Information Platform”
To classify a blueprint as documentation, set the Implementation status to “Informational” When the blueprint's Definition status is marked “Approved”, it will appear in this listing.
|
OSHIP Developer's Guide
for Open Source Health Information Platform
Create a document specifically for developers of the OSHIP platform.
|
|
|
Develop an API for Microsoft Health Vault
for Open Source Health Information Platform
It is expected that applications developed on OSHIP will cover the spectrum of healthcare such as small specialist offices, health research and even health clubs. It is essential that users of Microsoft Health Vault be able to transfer that information from these specialist applications to their Health Vault record.
|
|
|
Authentication via devices connected to the client PC running the browser
for Open Source Health Information Platform
In a health care setting multiple people can work on the same PC (e.g. a Point-of-Sale, or a medication-dispenser). What kind of workflows can we provide for in OSHIP? Passwordless authentication is possible via biometric devices (finger print scanning, hand palm scanning, iris scanning) or a card reader. Should we ...
|
|
|
Installation on Linux
for Open Source Health Information Platform
How to install OSHIP on Linux.
|
|
|
Replace the PyParsing Parser w/Lexx/Yacc parser
for Open Source Health Information Platform
Replace the PyParsing Parser w/Lexx/Yacc parser
|
|
|
Develop an API for Google Health
for Open Source Health Information Platform
It is expected that applications developed on OSHIP will cover the spectrum of healthcare such as small specialist offices, health research projects and even health clubs. It is essential that users of Google Health be able to transfer that information from these specialist applications to their Google Health record.
|
6 blueprint(s) listed.
