Difference between revisions of "Profile Overview Template"

From IHE Wiki
Jump to navigation Jump to search
 
(28 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{{1|'''This is a template page.  Click edit, Do Not Save This Page, Copy the current text then go edit your page and paste it in.'''
+
'''This is a template page.  [[:Category:Templates|CLICK HERE]] if you're not sure how to use it.  DO NOT MODIFY this page unless you are changing the template for all future users.'''
  
''<Your page name should simply be Full Profile Name Profile with spaces, with capitals, without the acronym. e.g. Scheduled Workflow Profile>''
 
  
''<Tell a user in one sentence what the profile is about so they can decide if they're on the right page (and copy this text into the [[Profiles]] page as well), e.g. Scheduled Workflow (SWF) integrates ordering, scheduling, imaging acquisition, storage and viewing for Radiology exams. >''
+
''This template is for the one or two page user-oriented overview of an IHE Profile that is in Final Text, Trial Implementation or perhaps Public Comment.  Delete text in italics and replace it with your material.  Don't forget to delete the double quotes too.''
 +
 
 +
''Your page name should simply be Full Profile Name with spaces, with capitals, without the acronym. e.g. Scheduled Workflow. so it provides a title to the page. You can redirect the acronym to the full named page if you like for bonus points.''
 +
 
 +
 
 +
''<IN ONE LINE, tell a user what the profile is about (including the acronym) so they can decide if they're on the right page.  Basically this should be the same sentence that appears on the [[Profiles]] catalog page>''
 +
 
 +
''e.g. Scheduled Workflow (SWF) integrates ordering, scheduling, imaging acquisition, storage and viewing for Radiology exams.''
  
''<If you are adding a Profile, you may also want to add a section to the [[:Category:Actors| pages for existing Actors]] or copy the [[Actor Template]] if creating a new Actor.>''
 
}}}
 
 
__TOC__
 
__TOC__
  
 
==Summary==
 
==Summary==
 +
''<Describe the profile in about a paragraph using user-oriented language.  Focus on what it accomplishes for a user (i.e. the Use Cases).  Don't get into how it works, leave that to the Details section.>''
  
Functional Status Assessment Integration Profile (FSA)- year 2
+
''<Insert a simple graphic that, at a glance, visually summarizes what the profile is about.  Do not use an actor/transaction diagram here.  Show your graphic to someone for 5 seconds (literally) and ask them what it's about.  If what they say hits the main points in your summary paragraph, you have succeeded.  E.g. a graphic of a hospital, a clinic, and a lab with patient records moving between them.  .>''
The Functional Status Assessment Profile (FSA) supports the transfer of assessment information between practictioners during transfers of care intra-enterprise.
+
 
In the context of clinical documentation, the functional status describes the patient’s status of normal functioning at the time the document was created.
+
''<See [[Help:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on inserting an image/graphic.>''
  
 
==Benefits==
 
==Benefits==
Functional Status Assessment Integration Profile (FSA)
+
''<If the profile can improve Cost, Safety, Quality or Efficiency then list the specific examples of that benefit (e.g. error reduction, increased throughput) and how they come about (e.g. SWF reduces patient errors due to mistyped demographics at the modality by transfering demographics electronically from the Order Filler).  Consider using a bullet list for readability.  Such benefits help users and vendors make the business case for the profile.  If the profile does not improve any aspect of Cost, Safety, Quality or Efficiency feel free to talk about something else here.>''
The Functional Status Assessment Profile (FSA) supports the transfer of assessment information between practictioners during transfers of care across enterprises.
 
In the context of clinical documentation, the functional status describes the patient’s status of normal functioning at the time the document was created.
 
Functional status includes information concerning:
 
• Skin assessment
 
• Physical Functioning Assessment
 
• Assessment of Activities of Daily Living (bathing, feeding, dressing and grooming)
 
• Pain Management
 
• Mood and behavior patterns
 
  
WSJ (9-5-07)Hospitals around the country are scrambling to put new programs in place to prevent pressure ulcers, commonly known as bedsores, after the federal Centers for Medicare and Medicaid Services announced last month that as of October 2008, it will no longer reimburse hospitals for treating eight "reasonably preventable" conditions. Pressure ulcers are among the most prevalent, costly and dangerous on the list.. . . . To combat this, hospitals are pushing screenings of all incoming patients from head to toe for skin issues that could lead to pressure ulcers.
+
==Details==
  
Kaiser Daily Health Policy Report
+
''<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>''
  
Medicare | Medicare Will Not Pay for Preventable Conditions Acquired at Hospitals
+
''<If the user might be familiar with the mechanisms used by the profile, you can mention them here.  E.g. Evidence Documents is based on DICOM Structured Report (SR) Templates.>''
[Aug 20, 2007]
 
      Medicare no longer will reimburse hospitals for the treatment of preventable errors, injuries and infections that occur in the facilities under a new rule scheduled for publication this week, a move that CMS officials said could save lives and millions of dollars, the New York Times reports. Under the rule, Medicare no longer will reimburse hospitals for the treatment of certain "conditions that could reasonably have been prevented," and the facilities "cannot bill the beneficiary for any charges associated with the hospital-acquired complication" (Pear, New York Times, 8/19).  
 
  
The eight conditions for which Medicare no longer will reimburse hospitals for treatment include: falls; mediastinitis, an infection that can develop after heart surgery; urinary tract infections that result from improper use of catheters; pressure ulcers; and vascular infections that result from improper use of catheters. In addition, the conditions include three "never events": objects left in the body during surgery, air embolisms and blood incompatibility (USA Today, 8/20).  
+
''<If the user might have an appreciation for the problems addressed in the profile, you can mention them here, but keep it short.  E.g. Mapping HL7 Order fields to DICOM Modality Worklist attributes can be inconsistent in the marketplace, so Scheduled Workflow provides vendors with more detailed instructions.>''
 +
 +
==Systems Affected==
 +
''<List (in user terms) the types of systems they might expect to have implemented actors from this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. and for each, how it would participate.>''
  
The rule, proposed by CMS in April and mandated by a 2005 law, will take effect in October 2008. CMS officials said that next year they plan to add three additional conditions to the list (Zhang, Wall Street Journal, 8/20).
+
* ''PACS systems may store, manage, and/or display Evidence Documents.''
 +
* ''Display systems may query, retrieve and display Evidence Documents.''
 +
* ''Reporting workstations may retrieve, process and include details from Evidence Documents in reports
  
==Details==
+
'''Actors & Transactions:'''
 +
 
 +
''<Insert an actor-transaction diagram, and or list of Content Definitions>''
 +
 
 +
==Specification==
 +
 
 +
'''Profile Status:''' [[Comments| Final Text]] 
 +
''<Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>''
  
 +
'''Documents:'''
  
1. Long-Term Care to Acute Care - describes a use case for assessment information during transfers of care from long term to acute care.
+
''<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile. This is a simple inventory of official normative and informative text.  If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below.  If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>''
2. Home or Ambulatory Care into Acute Care - describes a use case for assessment information during multiple care transfers.  
 
3. Behavioral - describes a use case for assessment information during transfers of care where information about depression in an older patient is used.
 
  
==Systems Affected==
+
[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
''<List (in user terms) systems that would be likely candidates for implementing this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. >''
+
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 1] - Section 5 (SWF Profile)
Not sure I understand this request. Audrey
+
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-2.pdf Vol. 2] - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
 +
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-3.pdf Vol. 3] - Appendix E
  
==References==
+
'''Underlying Standards:'''
  
''<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis) >''
+
''<list all the standards on which the profile is based; if possible with links to sources>''
9.6 References
+
:* [http://dicom.nema.org DICOM]
9.6.1 Numerical Rating Scale
+
:* [http://www.hl7.org HL7]
Bernstein, S. L., Bijur, P.E., Gallagher, E.J. (2006). Relationship Between Intensity and Relief in Patients with Acute Severe Pain. American Journal of Emergency Medicine, 24(2), 817-828.
+
:* ...
Bijur, P. E. (2003). Validation of a verbally administered numerical rating scale of acute pain for use in emergency departments. Academic Emergency Medicine, 10(4), 390-392.
 
Bijur, P. E. (2006). Lack of influence of patient self report pain itensity on administration of opioids for suspected long bone fractures. Journal of Pain, 7(6), 438-444.
 
Bryant, H. (2007). Pain: a multifacted phenomenon. Emergency Nursing, 14(10), 6-10.
 
Hartrick, C. T., Kovan, J. P., Shapiro, S. (2003). The Numeric Rating Scale for Clinical Pain Measurement: A Ratio Measure. World Institute of Pain, 3(4), 310-316.
 
Herr, K. (2002). Chronic Pain: challenges and assessment strategies. Journal of Gerontological Nursing, 28 (1), 20-27.
 
Kassalainen, S., Crook, J. (2004). An exploration of seniors' ability to report pain. Clinical Nursing Research, 13(3), 199.
 
Mc Caffery, M., Pasero, C. (1999). Teaching Patients to Use a Numerical Pain-Rating Scale. American Journal of Nursing, 99(12), 22.
 
McCaffery, M., Pasero, C. (1999). Pain: Clinical Manual (Second edition ed.). St. Louis: Mosby.
 
Perreault, K. (2005). Patient-Physiotherapist Agreement in Low Back Pain. Journal of Pain, 6(12), 817-827.
 
Staton, L. J., Panda, M., Chen, I., Genao, I., Kurz, J, Pasanen, M., Mechaber, A.J., Menon, M., O'Rorke, J., Wood, J., Rosenberg, E., Faeslis, C., Carey, T., Calleson, D., Cykert, S. (2007). When Race Matters: Disagreement in Pain Perception between Patients and their Physicians in Primary Care. Journal of National Medical Association, 99(5), 532-538.
 
Williamson, A., Hoggart, B. (2005). Pain: a review of three commonly used pain rating scales. Journal of Clinical Nursing, 14(7), 798-804.
 
9.6.2 Braden Scale For Predicting Pressure Sore Risk
 
A copy of the Braden Scale For Predicting Pressure Sore Risk can be found on the web at http://wiki.ihe.net/images/1/11/Braden.pdf.
 
A bibliography on the Braden Scale for Predicting Pressure Sore Risk can be found here on the web: http://www.bradenscale.com/bibliography.htm
 
9.6.3 Geriatric Depression Score
 
A bibliography on the Geriatric Depression Score can be found here on the web: http://www.stanford.edu/~yesavage/GDS.html
 
9.6.4 Minimum Data Set
 
More information on the Minimum Data Set be found here on the web:  http://www.cms.hhs.gov/MinimumDataSets20/
 
  
 
==See Also==
 
==See Also==
Profile Status: [[Comments| Final Text]] ''<Replace Final Text with Trial Implementation or Public Comment as appropriate.>''
 
  
The [[Frameworks#IHE {{{4|Radiology}}} Technical Framework| {{{4|Radiology}}} Technical Framework]] is the official master document for this Profile.  
+
''<The following sections can be left out if there is nothing to point to.  This is just to show where such information can go.>''
 +
 
 +
 
 +
'''Related Profiles'''
 +
 
 +
''<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one.  Start with the name of the other profile as a link and then explain the relationship.>''
  
''<Replace Radiology Technical Framework with the Trial Implementation Supplement or Public Comment Supplement as appropriate.>''
+
* ''[[Reporting Workflow]] [RWF] may use Evidence Documents as inputs to the reporting process.''
 +
* ''[[Simple Image & Numeric Reports]] [SINR] may include data copied from Evidence Documents.''
 +
* ''[[Cross-enterprise Document Sharing for Imaging]] [XDS-I] can be used to share Evidence Documents between sites over a network.''
 +
* ''[[Portable Data for Imaging]] [PDI] can store Evidence Documents on media such as CDs.''
 +
* ''[[Import Reconciliation Workflow]] [IRWF] can fix patient ids, etc. of Evidence Documents when importing.''
  
''<Replace the Template links below with links to the actual pages for the Profile>''
 
  
The [[{{{3|Profile FAQ Template}}}]] answers typical questions about what the Profile does.
+
'''Consumer Information'''
  
The [[{{{3|Profile Purchasing Template}}}]] describes considerations when purchasing equipment to deploy this Profile.
+
The [[Profile FAQ Template]] answers typical questions about what the Profile does.  ''<Replace the link with a link to the actual FAQ page for the Profile>''
  
The [[{{{3|Profile Implementation Template}}}]] provides additional information about implementing this Profile in software.
+
The [[Profile Purchasing Template]] describes considerations when purchasing equipment to deploy this Profile. ''<Replace the link with a link to the actual Purchasing page for the Profile>''
  
This page is based on the [[Profile Template]]
+
'''Implementer Information'''
  
''<Delete this Category Templates line since your Profile page is no longer a template.>'' [[Category:{{{3|Templates}}}]]
+
The [[Profile Implementation Template]] provides additional information about implementing this Profile in software.  ''<Replace the link with a link to the actual Implementation page for the Profile>''
 +
 
 +
'''Reference Articles'''
 +
 
 +
''<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis).  Go ahead, Google: IHE <Profile Name> abstract  or Google: IHE <Profile Name> and under the "more" select "Scholar".  You might be surprised. >''
  
 
[[Category:Profiles]]
 
[[Category:Profiles]]
 +
 +
This page is based on the [[Profile Overview Template]]
 +
 +
[[Category:Templates]]
 +
<noinclude>''<'''Delete this Category Templates line''' since your Profile page is no longer a template.>'' </noinclude>
 +
 +
<!--
 +
Categorize the Domain of your Profile with one of the following (delete the rest):
 +
[[Category:Cardiac Profile]]
 +
[[Category:Dental Profile]]
 +
[[Category:Endoscopy Profile]]
 +
[[Category:Eye Profile]]
 +
[[Category:ITI Profile]]
 +
[[Category:PaLM Profile]]
 +
[[Category:PCC Profile]]
 +
[[Category:PCD Profile]]
 +
[[Category:PHARM Profile]]
 +
[[Category:QRPH Profile]]
 +
[[Category:RO Profile]]
 +
[[Category:RAD Profile]]
 +
 +
Categorize key standards used in your Profile with one or more of the following (delete the rest):
 +
[[Category:CDA]]
 +
[[Category:FHIR]]
 +
[[Category:DICOM]]
 +
[[Category:DICOMweb]]
 +
[[Category:HL7v2]]
 +
[[Category:XDW]]
 +
[[Category:DocShare]]
 +
[[Category:RFD]]
 +
[[Category:HL7v3]]
 +
 +
And if people forget to do this, we'll comment this out and you can forget to opt-in. :-)
 +
-->

Latest revision as of 12:28, 5 November 2019

This is a template page. CLICK HERE if you're not sure how to use it. DO NOT MODIFY this page unless you are changing the template for all future users.


This template is for the one or two page user-oriented overview of an IHE Profile that is in Final Text, Trial Implementation or perhaps Public Comment. Delete text in italics and replace it with your material. Don't forget to delete the double quotes too.

Your page name should simply be Full Profile Name with spaces, with capitals, without the acronym. e.g. Scheduled Workflow. so it provides a title to the page. You can redirect the acronym to the full named page if you like for bonus points.


<IN ONE LINE, tell a user what the profile is about (including the acronym) so they can decide if they're on the right page. Basically this should be the same sentence that appears on the Profiles catalog page>

e.g. Scheduled Workflow (SWF) integrates ordering, scheduling, imaging acquisition, storage and viewing for Radiology exams.

Summary

<Describe the profile in about a paragraph using user-oriented language. Focus on what it accomplishes for a user (i.e. the Use Cases). Don't get into how it works, leave that to the Details section.>

<Insert a simple graphic that, at a glance, visually summarizes what the profile is about. Do not use an actor/transaction diagram here. Show your graphic to someone for 5 seconds (literally) and ask them what it's about. If what they say hits the main points in your summary paragraph, you have succeeded. E.g. a graphic of a hospital, a clinic, and a lab with patient records moving between them. .>

<See Help - Tips and Tricks for details on inserting an image/graphic.>

Benefits

<If the profile can improve Cost, Safety, Quality or Efficiency then list the specific examples of that benefit (e.g. error reduction, increased throughput) and how they come about (e.g. SWF reduces patient errors due to mistyped demographics at the modality by transfering demographics electronically from the Order Filler). Consider using a bullet list for readability. Such benefits help users and vendors make the business case for the profile. If the profile does not improve any aspect of Cost, Safety, Quality or Efficiency feel free to talk about something else here.>

Details

<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>

<If the user might be familiar with the mechanisms used by the profile, you can mention them here. E.g. Evidence Documents is based on DICOM Structured Report (SR) Templates.>

<If the user might have an appreciation for the problems addressed in the profile, you can mention them here, but keep it short. E.g. Mapping HL7 Order fields to DICOM Modality Worklist attributes can be inconsistent in the marketplace, so Scheduled Workflow provides vendors with more detailed instructions.>

Systems Affected

<List (in user terms) the types of systems they might expect to have implemented actors from this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. and for each, how it would participate.>

  • PACS systems may store, manage, and/or display Evidence Documents.
  • Display systems may query, retrieve and display Evidence Documents.
  • Reporting workstations may retrieve, process and include details from Evidence Documents in reports

Actors & Transactions:

<Insert an actor-transaction diagram, and or list of Content Definitions>

Specification

Profile Status: Final Text <Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>

Documents:

<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile. This is a simple inventory of official normative and informative text. If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below. If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>

IHE Radiology Technical Framework:

  • Vol. 1 - Section 5 (SWF Profile)
  • Vol. 2 - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
  • Vol. 3 - Appendix E

Underlying Standards:

<list all the standards on which the profile is based; if possible with links to sources>

See Also

<The following sections can be left out if there is nothing to point to. This is just to show where such information can go.>


Related Profiles

<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one. Start with the name of the other profile as a link and then explain the relationship.>


Consumer Information

The Profile FAQ Template answers typical questions about what the Profile does. <Replace the link with a link to the actual FAQ page for the Profile>

The Profile Purchasing Template describes considerations when purchasing equipment to deploy this Profile. <Replace the link with a link to the actual Purchasing page for the Profile>

Implementer Information

The Profile Implementation Template provides additional information about implementing this Profile in software. <Replace the link with a link to the actual Implementation page for the Profile>

Reference Articles

<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis). Go ahead, Google: IHE <Profile Name> abstract or Google: IHE <Profile Name> and under the "more" select "Scholar". You might be surprised. >

This page is based on the Profile Overview Template <Delete this Category Templates line since your Profile page is no longer a template.>