Link to this page
Health Level Seven Reference Implementation Model, Version 3
Acronym | HL7 |
Visibility | Public |
Description | This version is the first update to Normative RIM, Release 3. It is based on changes approved in Harmonization in November 2010. This release of the RIM is bound to HL7 Abstract Data Types Release 2. |
Status | Production |
Format | UMLS |
Contact | Methodology and Modelling Committee, mnm@lists.hl7.org |
Categories | Health |
Version | Released | Uploaded | Downloads |
---|---|---|---|
HL7V3.0_2024_07 (Parsed, Indexed, Metrics, Annotator, Error Diff) | 11/04/2024 | 01/16/2025 | RDF/TTL | CSV | Diff |
2024AA (Archived) | 05/06/2024 | 08/28/2024 | RDF/TTL | Diff |
2023AB (Archived) | 11/06/2023 | 01/31/2024 | RDF/TTL | Diff |
2023AA (Archived) | 04/01/2023 | 08/07/2023 | RDF/TTL | Diff |
2022AB (Archived) | 11/07/2022 | 01/06/2023 | RDF/TTL | Diff |
2022AA (Archived) | 05/02/2022 | 06/10/2022 | RDF/TTL | Diff |
2021AB (Archived) | 11/01/2021 | 11/18/2021 | RDF/TTL | Diff |
2021AA (Archived) | 04/03/2021 | 05/20/2021 | RDF/TTL | Diff |
2020AB (Archived) | 11/02/2020 | 01/06/2021 | RDF/TTL | Diff |
2020AA (Archived) | 05/04/2018 | 09/24/2020 | RDF/TTL | Diff |
2019AB (Archived) | 11/04/2019 | 11/18/2019 | RDF/TTL | Diff |
2019AA (Archived) | 05/06/2019 | 08/27/2019 | RDF/TTL | Diff |
2018AB (Archived) | 11/05/2018 | 04/29/2019 | RDF/TTL | Diff |
2018AA (Archived) | 05/07/2018 | 07/06/2018 | RDF/TTL | Diff |
2017AB (Archived) | 11/06/2017 | 07/06/2018 | RDF/TTL | Diff |
2017AA (Archived) | 05/08/2017 | 04/06/2018 | RDF/TTL | Diff |
2016AB (Archived) | 02/06/2017 | 02/06/2017 | RDF/TTL | Diff |
2016AA (Archived) | 09/06/2016 | 09/06/2016 | RDF/TTL | Diff |
2015AB (Archived) | 07/20/2016 | 07/20/2016 | RDF/TTL | Diff |
2015AA (Archived) | 06/09/2015 | 06/09/2015 | RDF/TTL | Diff |
2014AB (Archived) | 01/29/2015 | 01/29/2015 | RDF/TTL |
2014aa (Archived) | 11/01/2011 | 01/14/2015 | RDF/TTL |
2011ab (Archived) | 11/01/2011 | 04/05/2012 | OWL |
0234 (Archived) | 11/02/2010 | 10/25/2011 | RDF/TTL |
0230 (Archived) | 03/02/2010 | 03/30/2010 | RDF/TTL |
more... |
- Health Ontology Mapper - UCSF_UCareDischargeDisposition
- All Disposition/Discharge Codes and Values listed in the UCSF- UCare patient source data
Classes | 9,095 |
Individuals | 0 |
Properties | 54 |
Maximum depth | 11 |
Maximum number of children | 808 |
Average number of children | 8 |
Classes with a single child | 268 |
Classes with more than 25 children | 59 |
Classes with no definition | 2,275 |
Id | http://purl.bioontology.org/ontology/HL7/C0457083
http://purl.bioontology.org/ontology/HL7/C0457083
|
---|---|
Preferred Name | uses |
Definitions |
<p>Indicates that the source act makes use of (or will make use of) the information content of the target act.</p><i>UsageNotes:</i>A usage relationship only makes sense if the target act is authored and occurs independently of the source act. Otherwise a simpler relationship such as COMP would be appropriate.<i>Rationale:</i>There is a need when defining a clinical trial protocol to indicate that the protocol makes use of other protocol or treatment specifications. This is stronger than the assertion of "references". References may exist without usage, and in a clinical trial protocol is common to assert both: what other specifications does this trial use and what other specifications does it merely reference.
|
Type | http://www.w3.org/2002/07/owl#Class |
All Properties
definition | <p>Indicates that the source act makes use of (or will make use of) the information content of the target act.</p><i>UsageNotes:</i>A usage relationship only makes sense if the target act is authored and occurs independently of the source act. Otherwise a simpler relationship such as COMP would be appropriate.<i>Rationale:</i>There is a need when defining a clinical trial protocol to indicate that the protocol makes use of other protocol or treatment specifications. This is stronger than the assertion of "references". References may exist without usage, and in a clinical trial protocol is common to assert both: what other specifications does this trial use and what other specifications does it merely reference. |
---|---|
prefLabel | uses
|
notation | C0457083
|
HL7 code status | active
|
HL7PL | true
|
subClassOf | |
Semantic type UMLS property | |
HL7 usage notes | A usage relationship only makes sense if the target act is authored and occurs independently of the source act. Otherwise a simpler relationship such as COMP would be appropriate.
|
HL7 internal Id | 23102
|
type | |
tui | T169
|
cui | C0457083
|
HL7DC | true
|
Delete | Subject | Author | Type | Created |
---|---|---|---|---|
No notes to display |
- Problem retrieving properties:
Notes
Add NCBO Web Widgets to your site for HL7
Widget type | Widget demonstration |
---|---|
|
Step 2: Follow the Instructions
For more help visit NCBO Widget Wiki |
|
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
For more help visit NCBO Widget Wiki |
|
Step 2: Follow the InstructionsCopy the code below and paste it to your HTML page <iframe frameborder="0" src="/widgets/visualization?ontology=HL7&class=http%3A%2F%2Fpurl.bioontology.org%2Fontology%2FHL7%2FC1562189&apikey=YOUR_API_KEY"></iframe> For more help visit NCBO Widget Wiki |
|
Step 2: Follow the InstructionsCopy 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: "HL7" }); You can also view a detailed demonstration For more help visit NCBO Widget Wiki |