This community effort aims to provide medical,healthcare and life-science specialized web schemas and vocabulary through improving and extending the existing schemas, concepts, terms and definitions in schema.org vocabulary. Ultimate goal is 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 and healthcare and life science ontology/vocabulary for formalization of healthcare information.
This will make healthcare and medical data on web easy to describe correctly (with their correct meaning and context), easy to expose /index so ready to be accessible and will highly improve to re-usability and exchanging in semantic way, with their correct meaning and context.
The intention is not to replace existing ontologies, nor making upper level ontology nor creating yet another clinical information model/standards. The aim is mainly to provide most useful and frequently used (so, demand driven) classes and properties related to the medical and healthcare domain. Within this scope all concepts are mapped as far as it's feasible to the existing terminology like SNOMED CT, ICD, LOINC, ATC, RxNorm, HL7 FHIR, etc.
Note: Community Groups are proposed and run by the community. Although W3C hosts these conversations, the groups do not necessarily represent the views of the W3C Membership or staff.
But those who missed it , the health-lifesci.schema.org extension is a new home for our existing Medical and healthcare related terms, as well as potential future collaborative work.
Among other improvements, a large number of medical/health terms have been moved from core into a health-lifesci extension. See: https://github.com/schemaorg/schemaorg/issues/492
To post or create an issue, just go to the page at right upper corner, below the tab “Tools for this Group” click on the fourth item “Issues” . You will be re-directed to Github page where you can read existing issues and you can create a new one.
3)One the issue is solved (community consensus), action will be created to ask the contributor to add this into vocabulary (either directly in RDFa file; either in .ttl file according everyone’s ease.)
4)Important: All unannounced (as issue) or not discussed (on community group page here) additions in the data files will be automatically reverted.
5)We have 3 mailing list to use on this community group page:@public-schemed; @public-schemed-contrib; and @internal-schemed.
To use one of them or to post a message, just go to the page at right upper corner, below the tab “Tools for this Group” click on the firts item “Mailing list” and on the appearing list click on one of the mailing list you want to post to. You will get a window where you can post your message.
6)We need 2 extra Chairs for our community Group. Just leave a comment on this page if you can volunteer here. Please note that the chair need to contribute efficiently in maintenance of Community Group materials!