More of an enhancement suggestion really. So that's a (hypothetical) URI prefix for one coding system.
More linked data = better. Schema.org supports a number of coding systems: > The schema does provide a way to annotate entities with codes that refer to existing controlled medical vocabularies (such as MeSH, SNOMED, ICD, RxNorm, UMLS, etc) when they are available. For example, see the sample markup for MedicalScholarlyArticle. http://schema.org/docs/meddocs.html Somewhat unfortunately, many of the referenced schema do not have canonical URIs as keys (which can be fudged w/ an ad-hoc prefix like "icd10:" even in unstructured notes). Autocomplete on \w+: might be usable. On Apr 26, 2015 9:24 PM, "Chris Zimmerman" <[email protected]> wrote: > Update of bug #40767 (project health): > > Status: None => Invalid > Open/Closed: Open => Closed > > _______________________________________________________ > > Follow-up Comment #1: > > I'm a little confused what this means. I don't think the icd10 package uses > URIs like that... or is this report an enhancement request? We try to use > robust standards - icd10pcs, icd10, fhir, etc. which I think the author is > trying to get at. I agree that using known coding systems is important, > and we > do that in, for example, fhir when icd10 codes are preferred. I'm going to > close and mark as invalid, since we've already done work on this topic and > it's not a bug. > > _______________________________________________________ > > Reply to this item at: > > <http://savannah.gnu.org/bugs/?40767> > > _______________________________________________ > Message sent via/by Savannah > http://savannah.gnu.org/ > >
