This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Procedure FHIR Resource Proposal"
Jump to navigation
Jump to search
(Created page with "{{subst::Template:FHIR Resource Proposal}}") |
|||
| Line 13: | Line 13: | ||
| − | = | + | =Procedure= |
<!-- Resource names should meet the following characteristics: | <!-- Resource names should meet the following characteristics: | ||
| Line 30: | Line 30: | ||
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. --> | <!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. --> | ||
| − | [[ | + | [[Patient Care]] |
| + | |||
| + | (Temporarily managed by FHIR Code with review from Patient care) | ||
==Contributing or Reviewing Work Groups== | ==Contributing or Reviewing Work Groups== | ||
<!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the resource (optional) --> | <!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the resource (optional) --> | ||
| − | + | ||
| − | + | None | |
| − | |||
==FHIR Resource Development Project Insight ID== | ==FHIR Resource Development Project Insight ID== | ||
<!-- Please specify the id of your work group’s PSS for doing FHIR work. (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc --> | <!-- Please specify the id of your work group’s PSS for doing FHIR work. (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc --> | ||
| + | Pending | ||
==Scope of coverage== | ==Scope of coverage== | ||
| Line 55: | Line 57: | ||
As a rule, resources should encompass all of these aspects. | As a rule, resources should encompass all of these aspects. | ||
--> | --> | ||
| + | An action that is performed on a patient. This can be a physical 'thing' like an operation, or less invasive like counselling or hypnotherapy. | ||
| + | |||
| + | An Act whose immediate and primary outcome (post-condition) is the alteration of the physical condition of the subject. Used to record the details of procedures performed on a patient. This includes surgical procedures, diagnostic procedures, endoscopic precedures, biopsies. It excludes things for which there are specific resources, such as immunizations, drug administrations | ||
| + | |||
==RIM scope== | ==RIM scope== | ||
| Line 74: | Line 80: | ||
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document | * Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document | ||
--> | --> | ||
| + | Procedures are a common activity within medical practice and recorded by most EMR systems. | ||
==Expected implementations== | ==Expected implementations== | ||
<!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. --> | <!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. --> | ||
| + | |||
| + | A part of CCDA so can be expected to be implemented by most systems that support this. There are many specialist systems (particularly for surgical procedures) that record details of procedures. | ||
==Content sources== | ==Content sources== | ||
| Line 84: | Line 93: | ||
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? --> | Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? --> | ||
| + | CCDA, openEHR, existing systems | ||
==Example Scenarios== | ==Example Scenarios== | ||
| Line 99: | Line 109: | ||
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording) | Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording) | ||
--> | --> | ||
| + | The procedure resource is linked to: | ||
| + | * Patient resource as the subject | ||
| + | * Practitioner resource as the author | ||
| + | * DiagnosticReport for the report of the procedure | ||
| + | * Procedure/MedicationPrescription as related resources | ||
| + | |||
| + | It is likely the Specimen will also be included once that resource is specified. | ||
==Timelines== | ==Timelines== | ||
<!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting --> | <!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting --> | ||
| + | Expected to be balloted DSTU in September 2013 | ||
==gForge Users== | ==gForge Users== | ||
<!-- Identify the userids who will require commit access to gForge to maintain the resource. (Ensure all users have registered for gForge.) --> | <!-- Identify the userids who will require commit access to gForge to maintain the resource. (Ensure all users have registered for gForge.) --> | ||
| + | david_hay | ||
Revision as of 20:23, 27 May 2013
This page documents a Pending FHIR Resource Proposal
Contents
- 1 Procedure
- 1.1 Owning committee name
- 1.2 Contributing or Reviewing Work Groups
- 1.3 FHIR Resource Development Project Insight ID
- 1.4 Scope of coverage
- 1.5 RIM scope
- 1.6 Resource appropriateness
- 1.7 Expected implementations
- 1.8 Content sources
- 1.9 Example Scenarios
- 1.10 Resource Relationships
- 1.11 Timelines
- 1.12 gForge Users
Procedure
Owning committee name
(Temporarily managed by FHIR Code with review from Patient care)
Contributing or Reviewing Work Groups
None
FHIR Resource Development Project Insight ID
Pending
Scope of coverage
An action that is performed on a patient. This can be a physical 'thing' like an operation, or less invasive like counselling or hypnotherapy.
An Act whose immediate and primary outcome (post-condition) is the alteration of the physical condition of the subject. Used to record the details of procedures performed on a patient. This includes surgical procedures, diagnostic procedures, endoscopic precedures, biopsies. It excludes things for which there are specific resources, such as immunizations, drug administrations
RIM scope
Resource appropriateness
Procedures are a common activity within medical practice and recorded by most EMR systems.
Expected implementations
A part of CCDA so can be expected to be implemented by most systems that support this. There are many specialist systems (particularly for surgical procedures) that record details of procedures.
Content sources
CCDA, openEHR, existing systems
Example Scenarios
Resource Relationships
The procedure resource is linked to:
- Patient resource as the subject
- Practitioner resource as the author
- DiagnosticReport for the report of the procedure
- Procedure/MedicationPrescription as related resources
It is likely the Specimen will also be included once that resource is specified.
Timelines
Expected to be balloted DSTU in September 2013
gForge Users
david_hay
