oship-dev team mailing list archive

[Tim Cook <timothywayne.cook@xxxxxxxxx>]

Hi Xue Yu,

First of all I'd like to thank you for your interest in the project even
before the GSoC2009 organizations are announced.

On Sun, 2009-03-15 at 23:58 +0800, xueyu music wrote:
> Dear Tim:
>        Hello, I'm the student who is interested in the OSHIP project
> about Health API ideas. I have read some materials about the OSHIP
> project and have some questions to ask you, maybe the questions seem a
> little naive :)

Well, there are many concepts in openEHR and OSHIP that new new to many
people.  However, there are other people on the mailing list that can
answer some of these questions for you i addition to myself.  Also,
there are likely others on the list with the same questions. So please
send your questions to oship-dev@xxxxxxxxxxxxx

>      1. It seems that OSHIP is installed and tested on Ubuntu and
> Debian flavors and need support from other stuff installed. Can OSHIP
> run windows and VM and how can I try to do some practice to familar
> with the real OSHIP systems?

A key concept here is that we are building a development platform.  So,
so far there are no real OSHIP systems per se.   We will soon have a
couple of small demos to show developers how to begin creating openEHR
based applications.

As far as installation on other platforms is concerned.  There were
Windows install instructions for the pre-Grok 1.0 version of OSHIP.  The
previous installation instructions for Windows can be found here:
http://www.openehr.org/wiki/display/dev/OSHIP+Installation+on+Windows
but the need to be tested and re-validated before posting to the
Launchpad site.  

>     2. If there are some codes to add to the project, how can I test
> the functions these codes provide?

I prefer that you use doctests in your code.  However, a great deal of
the core OSHIP cannot really be tested that way and functional testing
will be done.

>     3.I only find the source code at 
> http://bazaar.launchpad.net/~rogererens/oship/ICD10tool/files/head%3A/
>       Could you please give some suggestions about how to read these
> source code effectively?


I will (in a day or so) produce some annotated screen shots that
describe the structure of OSHIP.  Hopefully you did the Grok tutorials
(this is important to understanding the overall framework).  

In reality; OSHIP is a Grok application that gives developers easy
access to the openEHR information model, along with the APIs to the
future services we plan to add.  You can think of most of the project
ideas as the Service layer to OSHIP.

As a VERY beggingin start to an OSHIP application, look at htwt.py

Cheers,
Tim