Continuity of care - process - Classes | NCBO BioPortal

Continuity of care

Last uploaded: September 25, 2024

Details

Acronym	CONTSONTO
Visibility	Public
Description	The Ontology of Continuity of care (ContSOnto) is an emerging research area consisting of the extension of a healthcare ontology to inform the continuity of care domain. This field is positioned at the confluence of health informatics, nursing informatics, process modelling, and artificial intelligence. This research relating to ContSOnto is underpinned by health informatics standard ISO 13940 Systems of Concepts for Continuity of Care ContSOnto focuses on how information flows from different information systems across and between services for clinical applications and health care professionals to use. Figure 14.2 provides an illustration (see https://contsys.org/pages/Guest%20blog/FormalOntology)of how the different classes and relationships in the standard are represented. The subject of care refers to the individual service user and health care actors can be human or non-human, for example, a health care professional or an organization. We have added concepts related to social determinants of health (SDH) in version 1.6.
Status	Alpha
Format	OWL
Language	English
Contact	contributor: Dr. Pamela Hussey, pamela.hussey@dcu.ie creator: Subhashis Das, subhashis@usal.es
Categories	Health

Version	Released	Uploaded	Downloads
1.6 (Parsed, Indexed, Metrics, Annotator)	03/24/2024	09/25/2024	OWL \| CSV \| RDF/XML \| Diff
1.5 (Archived)	04/30/2023	04/30/2023	OWL \| Diff
1.4 (Archived)	01/02/2021	03/11/2021	OWL \| Diff
1.3 (Archived)	01/02/2021	01/17/2021	OWL \| Diff
1.2 (Archived)	09/04/2020	09/04/2020	OWL \| Diff
1.1 (Archived)	08/11/2020	08/11/2020	OWL
more...

No views of CONTSONTO available

Classes	171
Individuals	3
Properties	353
Maximum depth	7
Maximum number of children	20
Average number of children	2
Classes with a single child	26
Classes with more than 25 children	0
Classes with no definition	17

No projects using CONTSONTO

Id	http://ontology.ip.rm.cnr.it/ontologies/DOLCE-Lite#Process http://ontology.ip.rm.cnr.it/ontologies/DOLCE-Lite#Process
Preferred Name	process
Definitions	set of interrelated or interacting activities that use inputs to deliver an intended result Within stative occurrences, we distinguish between states and processes according to homeomericity: sitting is classified as a state but running is classified as a process, since there are (very short) temporal parts of a running that are not themselves runnings. In general, processes differ from situations because they are not assumed to have a description from which they depend. They can be sequenced by some course, but they do not require a description as a unifying criterion. On the other hand, at any time, one can conceive a description that asserts the constraints by which a process of a certian type is such, and in this case, it becomes a situation. Since the decision of designing an explicit description that unifies a perdurant depends on context, task, interest, application, etc., when aligning an ontology do DLP, there can be indecision on where to align a process-oriented class. For example, in the WordNet alignment, we have decided to put only some physical processes under 'process', e.g. 'organic process', in order to stress the social orientedness of DLP. But whereas we need to talk explicitly of the criteria by which we conceive organic processes, these will be put under 'situation'. Similar considerations are made for the other types of perdurants in DOLCE. A different notion of event (dealing with change) is currently investigated for further developments: being 'achievement', 'accomplishment', 'state', 'event', etc. can be also considered 'aspects' of processes or of parts of them. For example, the same process 'rock erosion in the Sinni valley' can be conceptualized as an accomplishment (what has brought the current state that e.g. we are trying to explain), as an achievement (the erosion process as the result of a previous accomplishment), as a state (if we collapse the time interval of the erosion into a time point), or as an event (what has changed our focus from a state to another). In the erosion case, we could have good motivations to shift from one aspect to another: a) causation focus, b) effectual focus, c) condensation d) transition (causality). If we want to consider all the aspects of a process together, we need to postulate a unifying descriptive set of criteria (i.e. a 'description'), according to which that process is circumstantiated in a 'situation'. The different aspects will arise as a parts of a same situation.
Type	http://www.w3.org/2002/07/owl#Class

label	process
comment	set of interrelated or interacting activities that use inputs to deliver an intended result Within stative occurrences, we distinguish between states and processes according to homeomericity: sitting is classified as a state but running is classified as a process, since there are (very short) temporal parts of a running that are not themselves runnings. In general, processes differ from situations because they are not assumed to have a description from which they depend. They can be sequenced by some course, but they do not require a description as a unifying criterion. On the other hand, at any time, one can conceive a description that asserts the constraints by which a process of a certian type is such, and in this case, it becomes a situation. Since the decision of designing an explicit description that unifies a perdurant depends on context, task, interest, application, etc., when aligning an ontology do DLP, there can be indecision on where to align a process-oriented class. For example, in the WordNet alignment, we have decided to put only some physical processes under 'process', e.g. 'organic process', in order to stress the social orientedness of DLP. But whereas we need to talk explicitly of the criteria by which we conceive organic processes, these will be put under 'situation'. Similar considerations are made for the other types of perdurants in DOLCE. A different notion of event (dealing with change) is currently investigated for further developments: being 'achievement', 'accomplishment', 'state', 'event', etc. can be also considered 'aspects' of processes or of parts of them. For example, the same process 'rock erosion in the Sinni valley' can be conceptualized as an accomplishment (what has brought the current state that e.g. we are trying to explain), as an achievement (the erosion process as the result of a previous accomplishment), as a state (if we collapse the time interval of the erosion into a time point), or as an event (what has changed our focus from a state to another). In the erosion case, we could have good motivations to shift from one aspect to another: a) causation focus, b) effectual focus, c) condensation d) transition (causality). If we want to consider all the aspects of a process together, we need to postulate a unifying descriptive set of criteria (i.e. a 'description'), according to which that process is circumstantiated in a 'situation'. The different aspects will arise as a parts of a same situation.
prefLabel	process
subClassOf	http://ontology.ip.rm.cnr.it/ontologies/DOLCE-Lite#Stative
type	http://www.w3.org/2002/07/owl#Class

Subscribe to notes emails

Delete	Subject	Author	Type	Created
No notes to display

Problem retrieving properties:

Notes

Subscribe to notes emails

Filter: Hide Archived

Add NCBO Web Widgets to your site for CONTSONTO

Widget type	Widget demonstration
Jump To Type a class name from CONTSONTO and jump to it in BioPortal Get code	Step 2: Follow the Instructions Download the quick_jump.js file and put it on your server Copy the code below and paste it to your HTML page Note: If you would like to use Quick Jump across multiple ontologies: You can enter a comma-separated list of ontology ids: var BP_ontology_id = "NCIt,SNOMEDCT"; You can set the variable to 'all' to search all ontologies in BioPortal: var BP_ontology_id = "all"; To include definitions in the Jump To drop-down, add the following variable in Javascript: var BP_include_definitions = true; In the code that you just pasted, make sure to change the path to the quick_jump.js file to point to the location where you put the file (relative to your HTML file) For example, if you put the quick_jump.js file in the same directory as your HTML file, this is the code you would use: <div id="bp_quick_jump"></div> <script type="text/javascript"> var BP_ontology_id = "CONTSONTO";</script> <script src="quick_jump.js" type="text/javascript" charset="utf-8"></script> For more help visit NCBO Widget Wiki
Form Autocomplete Fill your form fields with classes from CONTSONTO Get code	Example 1 (start typing the class name to get its full URI) Example 2 (get the ID for a class) Example 3 (get the preferred name for a class) Step 2: Follow the Instructions Download the form_complete.js file and put it on your server. In the header for the page where you want the form field, include the form_complete.js file. On your form, for the fields where you want to use the class-selection widget, specify the field's class in the following format: `bp_form_complete-{ontology_id_list}-{value}` For example, `bp_form_complete-NCIT-uri` will use NCI Thesaurus (ontology id is NCIT) and will put the class URI in the field after the user selects the class from the pull-down list. Note: In addition to single ontology ids, you can use a list: `bp_form_complete-NCIT,NCBITAXON-uri` OR use 'all' to search across all BioPortal ontologies: `bp_form_complete-all-uri` The autocomplete widget accesses ontology content from the latest version of the ontology. You can use the following parameters to select which value will be placed into the user-visible input field: `uri` put the complete URI of the class (e.g., https://contsys.org/concept/resource ) `shortid` put the short id of the class, as used in BioPortal (e.g., "Common_Neoplasm"); `name` put the preferred name of the class (e.g., "Common Neoplasm"); In addition to the input element you defined, there are four hidden form elements that are created and then set when a user selects a class from the list. For example, if you create a field with this code: <input type="text" name="a" class="bp_form_complete-all-uri" size="100"/> The 'name' attribute is used to create the four following fields (note how the 'a' from the name attribute is appended to the id attribute): <input type="hidden" id="a_bioportal_preferred_name"> <input type="hidden" id="a_bioportal_concept_id"> <input type="hidden" id="a_bioportal_ontology_id"> <input type="hidden" id="a_bioportal_full_id"> Additional parameters are documented on the NCBO Widget Wiki For more help visit NCBO Widget Wiki
Visualization Display a visualization for a given class in CONTSONTO Get code	Step 2: Follow the Instructions Copy the code below and paste it to your HTML page <iframe frameborder="0" src="/widgets/visualization?ontology=CONTSONTO&class=https%3A%2F%2Fcontsys.org%2Fconcept%2Fresource&apikey=YOUR_API_KEY"></iframe> For more help visit NCBO Widget Wiki
Tree Widget Display a class tree with a search field for CONTSONTO Get code	Step 2: Follow the Instructions Copy the code below and paste it to your HTML page <link rel="stylesheet" type="text/css" href="/widgets/jquery.ncbo.tree.css"> <script src="/widgets/jquery.ncbo.tree-2.0.2.js"></script> <div id="widget_tree"></div> var widget_tree = $("#widget_tree").NCBOTree({ apikey: "YOUR_API_KEY", ontology: "CONTSONTO" }); You can also view a detailed demonstration For more help visit NCBO Widget Wiki