Predicate Proposal Chief Medical Officer

Chief Medical Officer
Value statement: The CMO (Chief Medical Officer) The chief physician is also used as a position for the physician, who is the professional supervisor of all physicians in a given organization. Сhief medical officer is one of the most important figures in pharmaceutical and biotechnology companies and in the healthcare sector. Helping to coordinate community clinics and any other activities in which the hospital participates is also a major job of a CMO.
.

Definition: The Chief Medical Officer (CMO) is the most important person for all physicians and healthcare professionals in healthcare organizations.
Tooltip definition of the predicate:The Chief Medical Officer of an Medical organization” to avoid misinterpretation with CMO (Chief Marketing Officer)
Type of value: Entity
For enums - all possible values: N/A
of accepted values: One
Inverse Properties and Name: ‘Chief Medical Officer of’
Examples of proper use:
‘Baxter’ → ‘Chief Medical Officer’ → “Tobi Karchmer”
citation:Tobi Karchmer, M.D., M.S. | Baxter . This citation points to an official website Baxter
Examples of improper use:
‘Baxter’ → ‘Chief Medical Officer’ → ‘Tobi Karchmer’ citation:https://access.yjp.org/events/virtual_mentorship_generating_value_in_adaptability_in_the_medical_device_field_with_tobi_karchmer_chief_medical_officer_baxter_international_inc__2022_09_19 . Virtual Mentorship Tobi Karchmer
Usage in other schemas:
Usage in wikidata: chief security officer - Wikidata 1
Usage in schema.org: N/A
Constraints: Entity should have value ‘is a’ → ‘Person’
Masculine/Feminine Form: N/A
Restrictions (ie PII concerns): N/A

Chief Medical Officer Of

Value statement: The CMO (Chief Medical Officer) The chief physician is also used as a position for the physician, who is the professional supervisor of all physicians in a given organization. Сhief medical officer is one of the most important figures in pharmaceutical and biotechnology companies and in the healthcare sector. Helping to coordinate community clinics and any other activities in which the hospital participates is also a major job of a CMO.
Definition: The Chief Medical Officer (CMO) is the most important person for all physicians and healthcare professionals in healthcare organizations.
Tooltip definition of the predicate: “The Chief Medical Officer of an Medical organization” to avoid misinterpretation with CMO (Chief Marketing Officer)
Type of value: Entity
For enums - all possible values: N/A
of accepted values: One
Inverse Properties and Name: ‘Chief Medical Officer’
Examples of proper use:
‘Tobi Karchmer’ → ‘Chief Medical Officer’ → “Baxter”
citation:Tobi Karchmer, M.D., M.S. | Baxter . This citation points to an official website Baxter
Examples of improper use:
‘Tobi Karchmer’ → ‘Chief Medical Officer’ → ‘Baxter’ citation:https://access.yjp.org/events/virtual_mentorship_generating_value_in_adaptability_in_the_medical_device_field_with_tobi_karchmer_chief_medical_officer_baxter_international_inc__2022_09_19 . Virtual Mentorship Tobi Karchmer
Usage in other schemas:
Usage in wikidata: chief security officer - Wikidata 1
Usage in schema.org: N/A
Constraints: Entity should have value ‘is a’ → ‘Person’
Masculine/Feminine Form: N/A
Restrictions (ie PII concerns): N/A

Generally we want to move away from having a separate predicate for each potential title in an organization - the exception to that probably being the CEO. It’s a slippery slope from a few CxO titles that make sense, to the next 100 CxO titles that various companies are making up / using. And then after that, what about the VP roles, etc?

Our current intention is to capture the roles that individuals are filling with qualifiers. So:

  • {$PersonA} → [employed at] → {$CompanyA} with the qualifier → [job title] → {CwhateverO}

This is fundamentally more sustainable than an individual predicate for hundreds of different jobs.

Apart from the CEO, CFO, COO, CTO who are already included, how to position the rest of the staff? like “key people”???
All proposals were rejected, as I understand it, there is no particular point in adding to the current additions to the protocol and it remains only to wait for proposals from the Golden team and engage in validation))).

@jed Maybe it makes sense to create a thread on the forum where you can pre-approved “suggestions” for further deeper study? because preparing proposals takes a lot of time and it is very frustrating to reject it.

I definitely understand your frustration. I’d say there are two things to do:

1 - before taking the time to write up the entire predicate proposal, start by posting a general idea of the predicates you’d like to propose here in the forum for feedback. If people are excited about the proposal, then take the time to fill out the full proposal.

2 - We’re actively working on a better solution for proposing predicates, to include a form that should make the data entry part of predicate creation easier and faster.

The team at Golden has been thinking about data schema issues for years and has developed some strong opinions based on our experiences. But there are definitely opportunities to propose new predicates - there are over 10,000 properties on Wikidata that you can use for ideas! - Wikidata:List of properties - Wikidata

1 Like