Re: MedicalGuideline vs. MedicalGuidelineRecommendation

Hi Angus,

On Mon, 18 Mar 2019 at 08:51, Angus Leitch <Angus.Leitch@nice.org.uk> wrote:

> Hi,
>
>
>
> I’m looking for advice on how to plan marking up for NICE guidelines (
> www.nice.org.uk). Given that the MedicalGuideline notes say “this type
> should be used to tag the actual guideline recommendation”, where would the
> MedicalGuidelineRecommendation type be used? Or is it recommended to use
> both properties for a guideline recommendation?
>

It looks like MedicalGuidelineRecommendation is simply a subtype (aka
"subclass") of MedicalGuideline, picking out a subset of medical guideline
recommendations "regarded as efficacious and where quality of the data
supporting the recommendation is sound.". For example, an obsolete
recommendation could still be considered a MedicalGuidelineRecommendation
but not a MedicalGuideline. BTW these are both what we call types or
classes, not properties. The difference (besides beginning with an initial
capital letter for easy recognition) is that types are "instantiable". It
makes sense sense to talk about "a" (or "an")
MedicalGuidelineRecommendation, Person, Event etc. So in the guidelines
case, we would say that everything that's a MedicalGuidelineRecommendation
is also expected to be a MedicalGuideline, by virtue of the schema.org type
hierarchy. Similarly, every LocalBusiness is an Organization, and every
https://schema.org/TheaterEvent is an Event, etc.

Hope this helps,

Dan


>
>
> Many thanks,
>
> Angus.
>
>
>
> ______________________________
>
>
>
> Angus Leitch
> Information architect, search analyst
> National Institute for Health and Care Excellence
> Level 1A | City Tower | Piccadilly Plaza | Manchester M1 4BD | United
> Kingdom
> Tel: 07854 430348
> Skype: angus.leitch
>
>
>
> This message may contain confidential information. If you are not the
> intended recipient please inform the sender that you have received the
> message in error before deleting it. Please do not disclose, copy or
> distribute information in this e-mail or take any action in relation to its
> contents. To do so is strictly prohibited and may be unlawful. Thank you
> for your co-operation.
>
> All messages sent by NICE are checked for viruses, but we recommend that
> you carry out your own checks on any attachment to this message. We cannot
> accept liability for any loss or damage caused by software viruses.
>
> http://www.nice.org.uk
>