Difference between revisions of "Mobile Retrieve Form for Data Capture"

Latest revision as of 18:38, 8 November 2019

Summary

The Mobile Retrieve Form for Data Capture (mRFD) Profile provides a method for gathering data within a user’s current application to meet the requirements of an external system. mRFD supports RESTful retrieval of forms from a form source, display and completion of a form, and return of instance data from the display application to the source application. The workflows defined in this profile are based on those defined by the Retrieve Form for Data Capture (RFD) profile.

Benefits

Ability to fill in form data within a user's current application
Standardized interaction for filling form data

Details

The Mobile Retrieve Form for Data Capture (mRFD) profile provides a method for gathering data within a user’s current application to meet the requirements of an external system. mRFD supports the retrieval of forms from a form source, the display and completion of a form and return of instance data from the display application to the source application.

The profile was created in conjunction with HL7 and uses the SMART on FHIR EHR Launch capacity as a generic framework for access to external web applications.

mRFD also allows dynamic data collection, both from within the form-requesting EHR, and from external sources that may have useful data that can be retrieved via secured RESTful transactions.

Systems Affected

EHR systems may find mRFD to be an effective method of launching external applications.
Web application developers may find the standardized security and authentication steps within mRFD to provide a clear direction for integration with a variety of data sources.

Actors & Transactions:

Specification

Profile Status: Trial Implementation

Documents: Mobile Retrieve Form for Data Capture Profile

Underlying Standards:

HL7 FHIR STU3
Hypertext Transfer Protocol - HTTP/1.1
Hypertext Transfer Protocol - HTTP/2
Uniform Resource Identifier (URI): Generic Syntax
The application/json Media Type for JavaScript Object Notation (JSON)
Additional HTTP Status Codes
Argonauts SMART on FHIR
HL7 Collaboration for SMART

FHIR Implementation Guide

Informatively this profile is also as a set of FHIR conformance resources, that are also registered at https://registry.fhir.org

@@ Line 2: / Line 2: @@
 ==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.>''
+The Mobile Retrieve Form for Data Capture (mRFD) Profile provides a method for gathering data within a user’s current application to meet the requirements of an external system.  mRFD supports RESTful retrieval of  forms from a form source, display and completion of a form, and return of instance data from the display application to the source application.  The workflows defined in this profile are based on those defined by the Retrieve Form for Data Capture (RFD) profile.
-''<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:Contents#Tips_.26_Tricks| 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.>''
+* Ability to fill in form data within a user's current application
+* Standardized interaction for filling form data
 ==Details==
+The Mobile Retrieve Form for Data Capture (mRFD) profile provides a method for gathering data within a user’s current application to meet the requirements of an external system. mRFD supports the retrieval of forms from a form source, the display and completion of a form and return of instance data from the display application to the source application.
-''<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>''
+The profile was created in conjunction with HL7 and uses the SMART on FHIR EHR Launch capacity as a generic framework for access to external web applications.
-''<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.>''
+mRFD also allows dynamic data collection, both from within the form-requesting EHR, and from external sources that may have useful data that can be retrieved via secured RESTful transactions.
-''<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.>''
+* EHR systems may find mRFD to be an effective method of launching external applications.
+* Web application developers may find the standardized security and authentication steps within mRFD to provide a clear direction for integration with a variety of data sources.
-* ''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>''
+[[Image:mRFD-Actor-Transaction.png]]
 ==Specification==
-'''Profile Status:''' [[Comments| Final Text]]
+'''Profile Status:''' [[Comments| Trial Implementation]]
-''<Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>''
-'''Documents:'''
+'''Documents:'''  [http://www.ihe.net/Technical_Frameworks/#QRPH Mobile Retrieve Form for Data Capture Profile]
-''<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.>''
+'''Underlying Standards:'''
-[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
-:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 1] - Section 5 (SWF Profile)
-:* [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
-'''Underlying Standards:'''
+* [http://hl7.org/fhir HL7 FHIR STU3]
+* Hypertext Transfer Protocol - HTTP/1.1
+* Hypertext Transfer Protocol - HTTP/2
+* Uniform Resource Identifier (URI): Generic Syntax
+* The application/json Media Type for JavaScript Object Notation (JSON)
+* Additional HTTP Status Codes
+* [https://smarthealthit.org/ Argonauts SMART on FHIR]
+* [https://hl7.org/fhir/ihe/links/apps HL7 Collaboration for SMART]
-''<list all the standards on which the profile is based; if possible with links to sources>''
+==FHIR Implementation Guide==
-:* [http://dicom.nema.org DICOM]
+Informatively this profile is also as a set of FHIR conformance resources, that are also registered at https://registry.fhir.org
-:* [http://www.hl7.org HL7]
-:* ...
 ==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'''
+* [[Retrieve Form for Data Capture]] [RFD] may be in use for exchange of a CDA for form population.
-''<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.>''
+* [[Structured Data Capture]] [SDC] may be in use for exchange of a structured form.
-* ''[[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.''
-'''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. >''
 [[Category:Profiles]]
 [[Category:QRPH Profile]]
 [[Category:FHIR]]

Difference between revisions of "Mobile Retrieve Form for Data Capture"

Latest revision as of 18:38, 8 November 2019

Contents

Summary

Benefits

Details

Systems Affected

Specification

FHIR Implementation Guide

See Also

Navigation menu

Search