Medicine

Medicine: suggested properties

2008-08-26T00:10:44.0028Z

mechanism of action

adult dosing

child dosing

Drug: suggested properties

2008-08-26T00:10:44.0028Z

mechanism of action

adult dosing

child dosing

Disease or medical condition: Connecting conditions to people?

2008-07-05T23:48:37.0005Z

Is there a way of connecting a particular medical condition to a fictional character who suffers from it? For example, Sheila Gallagher in Shameless suffers from agoraphobia.

Disease or medical condition: add Medical Subject Headings (MeSH) to schema

2008-06-19T00:37:50.0012Z

Ah yes, property enumerations. I think that would be the right way to model all of the properties that are essentially foreign keys to big established biomedical databases. The disease type seems to have a lot of those. +1 from me in general.

I'm not an expert, but I think any changes on MeSH will not apply to disease IDs. That would make having an ID moot.

Disease or medical condition: add Medical Subject Headings (MeSH) to schema

2008-06-18T23:28:58.0012Z

Having "webpage" as an expected type is pretty clearly the wrong way to model this. It was an experiment in trying to model something that was a foreign key but also had a webpage associated with it. We have better ways to do this now -- namely namespace enumerations and URI templates. (Sorry abhay -- we seem to have devolved into technical jargon -- namespace enumerations are a way to store foreign keys that ensures uniqueness; URI templates are a way to automatically associate keys with a URL.)

An interesting thing about MeSH is that they do update it regularly; I don't know what sorts of things they change, so I don't know if we need to worry about versions in considering this sort of thing.

Disease or medical condition: add Medical Subject Headings (MeSH) to schema

2008-06-18T22:28:43.0005Z

I haven't looked closely, but it seems like there a MeSH hierarchy that might be able to possibly model as property enumerations. What do you think?

Disease or medical condition: add Medical Subject Headings (MeSH) to schema

2008-06-18T21:38:01.0000Z

Hi Abhay,

The idea is that you would add a weblink from the topic page. So for Autism, the MeSH URL would be added as I've done here (see the second weblink):

http://freebase.com/view/en/autism

And not from the page you were looking at, which is the topic page for the web page, and for for Autism. But I agree. Having machine-readable strings would be helpful here.

As a side note, you can keep track of discussions from your home page. If you're signed in, this page (http://freebase.com) will show you recent replies to you as well as posts in areas you're watching.

Disease or medical condition: add Medical Subject Headings (MeSH) to schema

2008-06-18T02:37:23.0012Z

I guess I didn't find the MeSH ID property before on any of the disease pages. In fact finding this page (http://freebase.com/view/en/autism?pid=%2Fmedicine%2Fdisease%2Fmesh) was very difficult but I was able to get there eventually. I was unable to add any information there due to a 500 error (reported)

It would be pretty useful to have a machine readable string. It would be great to have some sort of database of the strings and references to the nlm (example: http://www.nlm.nih.gov/cgi/mesh/2008/MB_cgi?mode=&term=Autistic+Disorder&field=entry#TreeF03.550.325.125) and, in the case of MeSH ids and other similar strings, the ability to traverse the tree of ids.

P.S. Sorry about the late response. I haven't checked this thread recently.

Medicine: Thoughts on disease/treatment

2008-06-11T04:16:26.0012Z

(Here's a reposting from a recent modeling list post from Faye Li (to Dan Ruderman about disease-disease relationships)

Hi Dan,

I have a to-do item regarding anatomical structures affected by diseases
on my whiteboard but didn't get to it this time. The type "Anatomical
structure" exists today without any properties (see
http://www.freebase.com/tools/schema/medicine/anatomical_structure) and
the plan was to try to flesh out the schema there. Any properties you'd
suggest?

As for "Disease Cause" (which will be renamed etiology shortly, with the
original name saved as an alias), I was thinking about refactoring the
type. Each cause needs to be qualified with evidence level, something
along the lines of "evident, probable, possible". I was also considering
adding an enumeration property/new type for etiology category that would
list, "bacterial, viral, chemical, parasitic", etc. I would appreciate
your expertise if you have time to talk about this offline.

-- Faye

Dan Ruderman wrote:
>
> I like the way the medical schema is filling out. This is really
> looking useful.
>
> A more technical term for "disease cause" would be "etiology".
> It might be useful to have a property on disease for affected
> anatomical structure(s).
>
> For disease treatment with a compound (perhaps a more specific
> co-type of disease treatment) it might be nice to have properties
> for dosage, method of administration, and duration. Maybe these
> constitute a prescription type?
>
> Dan

Medicine: Properties and units in the clinical laboratory sciences

2008-05-05T17:52:53.0007Z

Thanks Ed! I'll check it out.

Medicine: Properties and units in the clinical laboratory sciences

2008-05-04T00:28:39.0005Z

This document on syntax and semantic rules for the clinical laboratory sciences might be useful in this domain.

Disease or medical condition: add Medical Subject Headings (MeSH) to schema

2008-03-31T22:29:54.0005Z

Hi Abhay, we're considering changing the "MeSH ID" and other similar identifiers with expected type "Webpage" to machine-readable strings. Would it work for you?

Disease or medical condition: add Medical Subject Headings (MeSH) to schema

2008-03-31T22:22:58.0005Z

Abhay, does the “MeSH ID” property do what you want? It currently expects an instance of Webpage, like the other disease index properties (“ICD-9,” “DiseasesDB,” etc.). If not, what should be changed about it?

Disease or medical condition: add Medical Subject Headings (MeSH) to schema

2008-03-31T21:11:08.0030Z

It's a great controlled vocabulary that's used by professionals:

http://freebase.com/view/en/medical_subject_headings

Medicine: Not for veterinary medicine or phytopathology

2008-03-20T01:59:55.0012Z

Is there any objection for designating the current Medicine domain as the domain for human medical and health data, and thus will not include medical/health data on animals and plants?

Human medicine, veterinary medicine and plant diseases are such different fields that even though some of the schemata may look similar, the data will certainly not be. Even when a disease affects both humans and animals, the associated transmission methods, symptoms, complications, and treatments are often drastically different. Instead of lumping them together, it makes more sense to use co-typing to keep the data clean and simple. Queries will be simpler and shorter too: going through instances of the Physician type looking for a cardiologist will not require the additional property constraint that you're looking for a specialist of the human heart, looking up causes for "cardiac arrest" will not yield the surprising topic of chocolate (which applies to dogs, but not humans).

The same principle is used in other types in this domain as well. For example, the Muscle type only contains muscles in the human body, the Hospital type does not include pet hospitals, and "feline panleukopenia" should not be co-typed as a "Disease or medical condition" here.

Does that sound reasonable? If so, I'll clarify the type definitions in that domain to indicate that scope, and start cleaning up the data. Any comments?

Disease or medical condition: Add property for what part of the body a disease may affect?

2008-03-13T18:16:43.0015Z

"Body part" works for me. In general I'm not worried about type names. If someone with a more medicinal background came along and enlightened us to the correct term for that (if there is one), we could always rename it.

BTW, I like the Medical specialty type you just created. I was going to suggest that too. :)

Disease or medical condition: Add property for what part of the body a disease may affect?

2008-03-12T23:19:38.0029Z

This is a good idea; we'd probably need a new type for this. The existing anatomical structure type is too specific, since there are diseases that target a type of tissue (bone, muscle), rather than a specific structure (femur, spleen). "Body part"?

Disease or medical condition: Add property for what part of the body a disease may affect?

2008-03-12T08:06:07.0031Z

So I was reading about emphysema (and yes, I begin all my conversations this way...), and it occurred to me that it would be useful to denote, via a property of the "Disease or medical condition" type, the part of the body a disease may affect.

For emphysema, the property will indicate the lung. For nephrotic syndrome, the property will indicate the liver.

Disease or medical condition: Property for methods of disease transmission?

2008-03-12T07:57:40.0012Z

I still think this would make a useful property.

Disease or medical condition: Property for methods of disease transmission?

2008-01-17T01:44:51.0012Z

Thinking about causes made me think of disease transmission as well. Given all the infectious diseases in the world, it'd be useful to capture that in a property.

I'm slightly bothered by the fact that only infectious diseases will have properties for transmission methods. Although, come to think of it, is heredity a cause or transmission method? ;)

It'd be nice to capture both the category of disease tranmission method and details. By categories I mean airbone, vector-borne, direct contact, indirect contact, etc. But it'd be helpful to go specific and specify that, for example, although Malaria and Rabies are both vector-borne diseases, the former is tranmitted via a mosquito bite, whereas the latter is likely transmitted via a bite from an infected animal (dog, squirrel, etc.).

Disease or medical condition: Related genes

2008-01-17T01:06:11.0000Z

Also, cause of disease could be a disease as well.

Disease or medical condition: Related genes

2008-01-11T22:43:18.0007Z

That's a good point. We'll take it into consideration when we make the changes in the medicine domain (it looks like it's going to be a bit later than I had previously thought). We'll probably have something like a "disease cause" type that could be a bacteria, or virus, or fungus, or gene, or whatever.

Disease or medical condition: Related genes

2008-01-11T01:49:50.0012Z

For genetic diseases, you want a link to the genes involved (this is another sort of "caused by"). For example, see Niemann-Pick Disease, which mentions a few genes in the text.

Disease or medical condition: Caused by?

2007-11-15T20:24:41.0007Z

That's a property we are planning to add. We plan to make a bunch of changes to the medicine domain in the next month or two, so it should appear in the (comparatively) near future.

Disease or medical condition: Caused by?

2007-11-15T01:23:28.0005Z

How about a "Caused By" property, which could be either an "Organism Classification" (e.g. for bacterial diseases) or a "Virus Classification"? (Is there a way to have a choice of types?)

Drug class: add types for the following regarding toxicity:

2007-08-02T06:19:14.0000Z

Howdy infiniumetal, welcome to Freebase. It looks like you have some ideas about drug classification and the Medicine domain. These suggestions for types are good, but they seem a little granular to me. It's usually better to first try and see how you might model an area in a more generic way. The best way to get started here would be to create some types in your own personal domain, add some data, and see how it feels -- get a sense of how easy it would be to answer the types of questions you want to be able to ask. Let me know generally what you're looking to solve, and if you make any progress in your own domain.

Drug class: add types for the following regarding toxicity:

2007-07-31T06:01:12.0011Z

add types for the following regarding toxicity:
poison
classification of toxic agents
spectrum of undesired effects
mechanisms of toxicity
risk assessment.
Absorption
distribution
elimination of toxicants
biotransformation of xenobiotics
toxicokinetics
Target Organs of Toxicity
Toxic responses of the blood
toxic responses of the liver
toxic responses of the heart
toxic responses of the kidney
toxic responses of reproductive system
toxic effects of plants, fruits etc. on drug (i.e. grapefruit)

Drug class: add type for: Drug Toxicity Adverse drug reactions, monitoring adverse drug reactions, benefit risk ratio

2007-07-31T05:57:09.0011Z

add type for: Drug Toxicity Adverse drug reactions, monitoring adverse drug reactions, benefit risk ratio

Drug class: add type for: Drugs in Elderly

2007-07-31T05:56:36.0004Z

add type for: Drugs in Elderly

Medicine: Bodily Functions

2007-07-28T07:34:05.0000Z

This sounds like a good idea. If you get a chance to try this out in your own domain, make sure to let us know here.

Medicine: Physical exercise

2007-07-28T07:29:53.0009Z

Our type system does not currently support the type of categorization you're suggesting, but your type "Physical Exercise" is not be at all ambiguous, and sounds like a good idea. It looks like you've already been building up your schema; feel very welcome to populate your types with some example data and post back here with thoughts or questions.

Medicine: Physical exercise

2007-07-22T09:21:05.0004Z

I would like to add a "physical exercise" type which details various kinds of exercises for strength, flexibility, endurance etc. My interest is therapeutic exercise. However, there are other types of "exercise" (mental, musical etc). How easy is it for types to have multiple "parents"?

Medicine: Bodily Functions

2007-06-09T03:16:17.0005Z

We need a bodily function type to classify spasms, contractions, reproductive actions, growth, aging, reflexes, and so on and so on. Seemed like this is the place to put it. Let me know.