http://schema.org/MedicalProcedure

Currently schema.org/MedicalProcedure provides no method of expressing who will perform the procedure. To me this seems to be an omission.

For this reason I'd like to suggest adding a new property to schema.org/MedicalProcedure, namely:
careProvider

Possible description:
"A medical organization or person providing health care service(s)."

Another route could be a Multi Type Entity like [MedicalProcedure Service], so to be able to use 'provider', but IMHO this doesn't seem to be fitting either as I consider a 'care provider' to be a different beast than just a 'provider', especially for consumers of medical data.

To support my proposal I've already started implementing the property on a website: http://bit.ly/1EP52Cy
(and before anybody says anything - I know this page has an issue with the enumeration member PlasticSurgery, it's being fixed).

Note:
This property is also part of the MedicalEntity 'modification' proposal (#11), though this issue suggest a simpler version than the proposal does as the proposal also encompasses new schema.org Types.

@jvandriel I dunno. I feel that the Multi Type Entity would be a better approach, practically because we say that MedicalProcedure is a class of Service, and that seems right to me. I differ also in that I consider a "care provider" to be the same beast, but more specialized than a "provider".

I like the idea of knowing that I can search for a "Lap Band" provider...a doctor or clinic that can perform the procedure for me. We just need to agree how we express what that doctor or clinic. In Google Now, it would be cool to say "find the nearest Lasik doctor"...so really the 1st step is knowing that a "doctor", "clinic", "hospital" are already terms/subtypes used for a www.schema.org/MedicalOrganization and we already have them. The next step is knowing that a MedicalOrganization = Provider (and we already have that as well, since MedicalOrganization is a subtype of Organization where http://schema.org/Service can use the provider property.

So then the real Next step ? Get MedicalProcedure, MedicalTest, and MedicalTherapy as specific types under http://schema.org/Service That is what is needed, IMHO, not a new property.

+1. Making careProvider a subproperty of provider.
+1. Making MedicalProcedure Multi Type Entity.

"I differ also in that I consider a "care provider" to be the same beast, but more specialized than a "provider"."

Good point, I stand corrected. :)

"Get MedicalProcedure, MedicalTest, and MedicalTherapy as specific types under http://schema.org/Service"

+1

Personally I'm not too crazy about the idea for an MTE either, because imagine one has a MedicalProcedure making an Offer. That would lead to a MTE containing 3 types:

<script type="application/ld+json">
{
    "@context": "http://schema.org",
    "@type": ["MedicalProcedure","Service","Product"], 
    "name": "Some procedure name"
    "careProvider": {
        "@type": "Physician",
        "@id": "#physician",
        "name": "etc"
    },
    "offers": {
        "@type": "Offer",
        "seller": "#physician",
        "priceSpecification": {
            "@type": "PriceSpecification", 
            "mixPrice": "5000",
            "maxPrice": "10000",
            "priceCurrency": "USD"
        },
    },
}
</script>

"That is what is needed, IMHO, not a new property."

Originally this was my POV as well but the folks behind the MedicalEntity modification proposal (http://bit.ly/165EvWk) insisted they need/want it to be named 'careProvider', which I can understand from their POV. So how about what @twamarc suggested by adding it as a subProperty of 'provider'?