ProcedureForTransfer-v1.2(2015EN)
General information
Name: nl.nfu.ProcedureForTransfer
Version: 1.2
HCIM Status:Final
Release: 2015
Release status: Published
Release date: 1-4-2015
Metadata
DCM::CoderList | Kerngroep Registratie aan de Bron |
DCM::ContactInformation.Address | * |
DCM::ContactInformation.Name | * |
DCM::ContactInformation.Telecom | * |
DCM::ContentAuthorList | Projectgroep Generieke Overdrachtsgegevens & Kerngroep Registratie aan de Bron |
DCM::CreationDate | 6-6-2012 |
DCM::DeprecatedDate | |
DCM::DescriptionLanguage | nl |
DCM::EndorsingAuthority.Address | |
DCM::EndorsingAuthority.Name | NFU |
DCM::EndorsingAuthority.Telecom | |
DCM::Id | 2.16.840.1.113883.2.4.3.11.60.40.3.14.1 |
DCM::KeywordList | procedure,verrichting |
DCM::LifecycleStatus | Final |
DCM::ModelerList | Kerngroep Registratie aan de Bron |
DCM::Name | nl.nfu.OverdrachtVerrichting |
DCM::PublicationDate | 1-4-2015 |
DCM::PublicationStatus | Published |
DCM::ReviewerList | Projectgroep Generieke Overdrachtsgegevens & Kerngroep Registratie aan de Bron |
DCM::RevisionDate | 1-4-2015 |
DCM::Superseeds | |
DCM::Version | 1.2 |
HCIM::PublicationLanguage | EN |
Revision History
Only available in Dutch
Publicatieversie 1.0 (15-02-2013) -
Publicatieversie 1.1 (01-07-2013)
ZIB-55 | RFC Bouwsteen Procedure |
ZIB-24 | Diagnostische verrichtingen onderdeel van Results |
Publicatieversie 1.2 (01-04-2015)
ZIB-84 | Klinische bouwsteen nl.nfu.OverdrachtProcedure uitbreiden met Aanvrager (n.a.v. issue #077) |
ZIB-93 | Bouwsteennaam Procedure wijzigen in Verrichting |
ZIB-95 | Elementen in Example of the Instrument OverdrachtProcedure komen niet terug in model |
ZIB-122 | De definitie van de sectie Concept van de bouwsteen OverdrachtProcedure aanpassen. |
ZIB-270 | Aanpassen DCM::DefinitionCode van rootconcept Verrichting van NL-CM-14.1.1 naar NL-CM:14.1.1. |
ZIB-271 | In de klinische bouwsteen OverdrachtProcedure DCM::ValueSet SNOMED CT aangepast van concept AnatomischeLokalisatie naar tagged value DCM::ContentExpression. |
ZIB-272 | In klinische bouwsteen OverdrachtProcedure DCM::ValueSet CBV verrichtingen van concept VerrichtingType aangepast naar tagged value DCM::CodeSystem. |
ZIB-273 | Tagged value DCM::ReferencedDefinitionCode is onjuist voor classes UitgevoerdDoor::Zorgverlener en AangevraagdDoor::Zorgverlener, dit zou NL-CM:17.1.1 moeten zijn i.p.v. NL-CM:17.1.2. |
ZIB-308 | Prefix Overdracht weggehaald bij de generieke bouwstenen |
ZIB-325 | AnatomischeLokaisatie wijzigen in AnatomischeLocatie |
ZIB-353 | Tagged values DCM::CodeSystem aanpassen naar DCM::ValueSet incl. gekoppelde codelijst. |
Incl. algemene wijzigingsverzoeken:
ZIB-94 | Aanpassen tekst van Disclaimer, Terms of Use & Copyrights |
ZIB-154 | Consequenties opsplitsing Medicatie bouwstenen voor overige bouwstenen. |
ZIB-200 | Naamgeving SNOMED CT in tagged values klinische bouwstenen gelijk getrokken. |
ZIB-201 | Naamgeving OID: in tagged value notes van klinische bouwstenen gelijk getrokken. |
ZIB-309 | EOI aangepast |
ZIB-324 | Codelijsten Name en Description beginnen met een Hoofdletter |
ZIB-326 | Tekstuele aanpassingen conform de kwaliteitsreview kerngroep 2015 |
Concept
The concept Procedure indicates a therapeutic procedure undergone by the patient. If relevant, diagnostic procedures can be listed as well.
A procedure can be a simple blood pressure measurement, but also a complex heart surgery.
Purpose
A procedure is carried out as part of a planned policy or to obtain additional information in the diagnostic process. Procedures are documented to gain insight into the treatment of a patient. In addition, procedures are documented for administrative purposes such as invoicing and workload measurement, scientific research and/or education.
Evidence Base
Only the procedures are described in this building block, not the results of the procedures. The LaboratoryResultTransfer and TextResultTransfer building blocks can be used to document the results.
Information Model
Type | Id | Concept | Card. | Definition | DefinitionCode | Reference | |||||||
NL-CM:14.1.1 | Procedure | Root concept of the ProcedureTransfer building block. This root concept contains all data elements of the ProcedureTransfer building block. | |||||||||||
NL-CM:14.1.2 | ProcedureStartDate | 0..1 | The start date (and if possible start time) of the procedure. A ‘vague’ date, such as only the year, is permitted.
The element offers the option to indicate the start of the period of a series of related procedures. |
||||||||||
NL-CM:14.1.3 | ProcedureEndDate | 0..1 | The end date (and if possible end time) of the procedure. A ‘vague’ date, such as only the year, is permitted.
The element offers the option to indicate the end of the period of a series of related procedures. |
||||||||||
NL-CM:14.1.8 | AnatomicalLocationOfTheProcedure | 0..* | Anatomical location which is the focus of the procedure. |
| |||||||||
NL-CM:14.1.9 | Indication::Problem | 0..* | The indication is the reason for the procedure. |
| |||||||||
NL-CM:14.1.4 | ProcedureType | 1 | The name of the procedure.
As of 1 January 2013, all procedures in the primary process have to be documented with CBV codes. To meet this requirement, the DHD procedure thesaurus (CBV procedures set) is used to code procedures. It is possible that in addition to the CBV procedures set, the NIC will be used for nurse procedures and that a “coded value set” will be introduced for paramedic procedures. |
| |||||||||
NL-CM:14.1.7 | Product | 0..* | The product, the placing of which in or on the body is the purpose of the procedure, for example placing an implant. |
| |||||||||
NL-CM:14.1.5 | Location::HealthcareProvider | 1 | The healthcare center where the procedure was or is carried out. |
| |||||||||
NL-CM:14.1.6 | CarriedOutBy::HealthcareProvider | 1..* | The healthcare provider who carried out the procedure. In most cases, only the medical specialty is entered, and not the name of the healthcare provider. |
| |||||||||
NL-CM:14.1.10 | RequestedBy::HealthcareProvider | 0..* | The healthcare provider who requested the procedure. |
|
Columns Concept and DefinitionCode: hover over the values for more information
For explanation of the symbols, please see the legend page
Example Instances
Only available in Dutch
VerrichtingType | Verrichting Anatomische Locatie |
Verrichting Start Datum |
Product | Indicatie | Uitgevoerd Door |
Locatie | |||
ProductType | ProductID | ProbleemNaam | Toelichting | Specialisme | OrganisatieNaam | ||||
Knie - prothese implantatie gewricht | linker knie | 05-06-2012 | Orthopedic surgical implants | (01)05050474530799 (17)160131 (21)1148130801 |
Implantant, Gen 2 Tibia Insert 5/6-9mm | Artrose | Beperking bij het bewegen van het gewricht, drukpijn door slijtage van twee compartimenten van de linker knie. | Orthopedie | UMCG |
References
1. GS1 Global Traceability Standard for Healthcare 1.2.0 (2013) [Online] Beschikbaar op: http://www.gs1.org/traceability/healthcare-traceability/1-2-0 [Geraadpleegd: 19 juni 2014].
2. Vektis Zorgverlenersspecificatie (subberoepsgroep) [Online] Beschikbaar op: http://ei.vektis.nl/WespCodelijstenDetail.aspx?Co_Ge_Code=COD016&Co_Or_Code=VEKT [Geraadpleegd: 19 juni 2014].
3. AZR-AGB-codelijst [Online] Beschikbaar op: http://www.agbcode.nl/MainPage/opzoeken.aspx?soort=IS [Geraadpleegd: 19 juni 2014].
Valuesets
AnatomicalLocationOfTheProcedureCodelist
Valueset OID: 2.16.840.1.113883.2.4.3.11.60.40.2.14.1.1 | Binding: |
Conceptname | Codesystem name | Codesystem OID |
SNOMED CT: <<91723000|anatomical structure| | SNOMED CT | 2.16.840.1.113883.6.96 |
ProcedureTypeCodelist
Valueset OID: 2.16.840.1.113883.2.4.3.11.60.40.2.14.1.2 | Binding: |
Conceptname | Codesystem name | Codesystem OID |
Alle waarden | CBV verrichtingen | 99 |
This information model in other releases
- Release 2016, (Version 3.0)
- Release 2017, (Version 4.1)
- Prerelease 2018-2, (Version 4.2)
- Prerelease 2019-2, (Version 5.1)
- Release 2020, (Version 5.2)
- Prerelease 2021-2, (Version 5.3)
- Prerelease 2022-1, (Version 5.4)
- Prerelease 2023-1, (Version 5.4.1)
- Prerelease 2024-1, (Version 5.4.1)
Information model references
This information model refers to
This information model is used in
Technical specifications in HL7v3 CDA and HL7 FHIR
To exchange information based on health and care information models, additional, more technical specifications are required.
Not every environment can handle the same technical specifications. For this reason, there are several types of technical specifications:
- HL7® version 3 CDA compatible specifications, available through the Nictiz ART-DECOR® environment
- HL7® FHIR® compatible specifications, available through the Nictiz environment on the Simplifier FHIR
Downloads
This information model is also available as pdf file or as spreadsheet
About this information
The information in this wikipage is based on Registratie aan de bron publication 2015 including errata dd. 16-07-2015
Conditions for use are located on the mainpage
This page is generated on 24/12/2018 12:31:18 with ZibExtraction v. 3.0.6932.1989