Skip to toolbar

Community & Business Groups

Proposed Group: Healthcare Ontology Community Group

The Healthcare Ontology Community Group has been proposed by Marc Twagirumukiza:


Dear colleagues,
I am pleased to introduce to you this healthcare community effort initiated in June 2013, to build an axtension to schema.org medical entity (named health.schema.org).
This effort aimed to enable the use of schema.org not only by webmasters but also in indexing health records, healthcare documents and as a pillar open source of medical ontology/vocabulary for formalization of healthcare information. This effort was insipired by the experience with SALUS EU FP7 project (info here and here).

Within SALUS EU FP7 project- with AGFA Healthcare as a partner, several reusable clinical entities using schema.org as a third-party pillar source of medical ontology and have been tested successfully and used.

This community effort aim to provide a medical/health vocabulary. The intention is not to be complete nor replacing existing clinical information models nor creating a new information model. The aim is mainly to provide most usefull and frequently used (so, demand driven) classes and predicates related to medical domain. Within this scope all concepts are mapped to the existing terminology (SNOMED, ICD, LOINC, ATC, RxNorm,etc.) as far as it’s feasible.

The proposal have been already submitted to schema.org and waiting for approval.

We will leave out to the consumer the next step of drafting a set of clinical information models using schema.org as a third-party pillar source of medical ontology. This will contribute to the interoperability and re-use of the patterns in healthcare information exchange.

Do not miss this momentum! Please join this effort today and be part of future healthcare information sharing community!

You’re all welcome!
Marc Twagirumukiza


You are invited to support the creation of this group. Once the group has a total of five supporters, it will be launched and people can join to begin work. In order to support the group, you will need a W3C account.

Once launched, the group will no longer be listed as “proposed”; it will be in the list of current groups.

If you believe that there is an issue with this group that requires the attention of the W3C staff, please send us email on site-comments@w3.org

Thank you,
W3C Community Development Team

4 Responses to Proposed Group: Healthcare Ontology Community Group

  • James G. Robertson

    Nice Initiative. Full support.
    Maybe you should use as name “Healthcare Schema Vocabulary” rather than “Healthcare Ontology” which is in my humble opinion too ambitious! Should we have one day a Healthcare Ontology? I guess no. We will have speciality domain by speciality eg genetics, Surgery, Reproductive health, Medical Devices, etc.

    Reply

    • Dave F. D. Jr

      Hi there,
      I do not share the concern of being “too” ambitious but I support the idea of naming this “Healthcare Schema Vocabulary”.
      What other’s thoughts?
      BTW by saying schema, are not we including the information models? We should remain neutral about this and leave out-as Marc said to the consumer.

      Reply

      • Marc Twagirumukiza

        Thanks Dave and James. I do agree with you that using “Healthcare Schema Vocabulary” would be better but I think at this stage it’s not possible to change the name. I will contact w3c staff to know.
        On the other hand we should not be afraid to be ambitious. I think we need to think wide but stay focused. One step at time.
        Regards
        Marc

        Reply

  • Marc Twagirumukiza

    Vote results for the short name for medicalEntinty Extension proposal.

    At closing date today, you voted for:

    health.schema.org

    Follow this link for details:
    https://docs.google.com/forms/d/1FwakA7Z6AD27A-w8NignT87h42myXUEEtxRBTeQkEeI/viewanalytics

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

Before you comment here, note that this forum is moderated and your IP address is sent to Akismet, the plugin we use to mitigate spam comments.

*