FHIR Use Case - Revision history

Tomjones: /* Taxonomy */

2021-04-26T22:49:31Z

Taxonomy

← Older revision		Revision as of 22:49, 26 April 2021
Line 17:		Line 17:
	#Research = Work done to improve healthcare costs, outcomes, quality, safety, and innovation via systematic investigation and structured data analysis.		#Research = Work done to improve healthcare costs, outcomes, quality, safety, and innovation via systematic investigation and structured data analysis.

	===Taxonomy===		===FHIR Taxonomy===
	* Patient = the subject of the data (A profile)		* Patient = the subject of the data (A profile)
	* Observation = an entry into a data base (A profile)		* Observation = an entry into a data base (A profile)

Tomjones: /* Preconditions */

2021-04-26T22:46:14Z

Preconditions

← Older revision		Revision as of 22:46, 26 April 2021
Line 16:		Line 16:
	#Transaction = Per the HL7 website; an interaction that submits a set of actions to perform on a server as a single atomic action. Multiple actions on multiple resources of the same or different types may be submitted, and they may be a mix of other operations (e.g. read, search, create, update, delete, etc.)		#Transaction = Per the HL7 website; an interaction that submits a set of actions to perform on a server as a single atomic action. Multiple actions on multiple resources of the same or different types may be submitted, and they may be a mix of other operations (e.g. read, search, create, update, delete, etc.)
	#Research = Work done to improve healthcare costs, outcomes, quality, safety, and innovation via systematic investigation and structured data analysis.		#Research = Work done to improve healthcare costs, outcomes, quality, safety, and innovation via systematic investigation and structured data analysis.

			===Taxonomy===
			* Patient = the subject of the data (A profile)
			* Observation = an entry into a data base (A profile)
			* Conformance Package will assume the US Core and CMS regulations.
			* Manifest = list of the available profile definitions
			* Implementation Guide = description of profiles in use

	==Preconditions==		==Preconditions==

Tomjones: /* Preconditions */

2021-04-26T22:33:10Z

Preconditions

← Older revision		Revision as of 22:33, 26 April 2021
Line 18:		Line 18:

	==Preconditions==		==Preconditions==
	*The patient has a primary care provider with up-to-date medical conditions, prescriptions and allergies.		* The patient has a primary care provider with up-to-date medical conditions, prescriptions and allergies.
	*The PCP uses an EHR which is part of the US Healthcare Assurance Framework.		* The PCP uses an EHR which is part of the US Healthcare Assurance Framework.
	*		* All of the parties to data flow are using the US Core profile of the latest FHIR specification.

	==Scenarios==		==Scenarios==

Tomjones: /* Actors */

2021-04-26T22:32:13Z

Actors

← Older revision		Revision as of 22:32, 26 April 2021
Line 8:		Line 8:

	===Actors===		===Actors===
			In the FHIR spec a EHR is considered to be a data responder. Here we dstinguish between two types, the source and receiver, which can dynamically switch multiple time during a single session.
	#Data Source = data goes from point A to point B. The source is where the data is coming from. Relative to this document, a data source can be a Query Responder or a Push Initiator.		#Data Source = data goes from point A to point B. The source is where the data is coming from. Relative to this document, a data source can be a Query Responder or a Push Initiator.
	#Data Receiver = data goes from point A to point B. The receiver is where the data is going to. Relative to this document, a data receiver can be a Query Initiator or a Push Recipient.		#Data Receiver = data goes from point A to point B. The receiver is where the data is going to. Relative to this document, a data receiver can be a Query Initiator or a Push Recipient.

Tomjones: /* Actors */

2020-05-14T23:22:29Z

Actors

← Older revision		Revision as of 23:22, 14 May 2020
Line 9:		Line 9:
	===Actors===		===Actors===
	#Data Source = data goes from point A to point B. The source is where the data is coming from. Relative to this document, a data source can be a Query Responder or a Push Initiator.		#Data Source = data goes from point A to point B. The source is where the data is coming from. Relative to this document, a data source can be a Query Responder or a Push Initiator.
	#Data Receiver I=data goes from point A to point B. The receiver is where the data is going to. Relative to this document, a data receiver can be a Query Initiator or a Push Recipient.		#Data Receiver = data goes from point A to point B. The receiver is where the data is going to. Relative to this document, a data receiver can be a Query Initiator or a Push Recipient.
	#[[Record Locator Service]](RLS) = provides the ability to identify where records are located based upon criteria such as a Person ID and/or record data type, as well as providing functionality for the ongoing maintenance of this location information.		#[[Record Locator Service]](RLS) = provides the ability to identify where records are located based upon criteria such as a Person ID and/or record data type, as well as providing functionality for the ongoing maintenance of this location information.
	#Provider = A clinician or organization that is directly engaged in treatment services.		#Provider = A clinician or organization that is directly engaged in treatment services.

Tomjones: /* References */

2020-05-14T23:19:10Z

References

← Older revision		Revision as of 23:19, 14 May 2020
Line 62:		Line 62:

	==References==		==References==
			* See the wiki page [[FHIR to the Patient Use Case]] for the specific use case of the patient (or guardian) downloading machine readable data to their own device.

	[[Category:Health]]		[[Category:Health]]
	[[Category:Use Cases]]		[[Category:Use Cases]]

Tomjones: /* Context */

2020-03-20T00:53:54Z

Context

← Older revision		Revision as of 00:53, 20 March 2020
Line 2:		Line 2:
	Carequality FHIR Use Case Proposal		Carequality FHIR Use Case Proposal
	==Context==		==Context==
	* [https://s3.amazonaws.com/ceq-project/wp-content/uploads/2018/12/10195830/FHIR-Use-Case-Proposal.pdf FHIR Use Case Proposal]		* [https://s3.amazonaws.com/ceq-project/wp-content/uploads/2018/12/10195830/FHIR-Use-Case-Proposal.pdf FHIR Use Case Proposal] was the source of the material. It has been modified as noted in the interests of [[Patient Choice]].
	===Goal===		===Goal===
	Release of PHI can only occur if the record holder has trust not only that it can accurately identify the requester, but that the request itself, and the requester’s policies and practices around the information once it is released, are appropriate. Such trust is straightforward to establish for an individual connection between two partner organizations, by relying on new or existing contractual relationships bolstered by negotiation of security and other technical details. Such an approach is not scalable, however, as the healthcare industry discovered in the context of document exchange via SOAP-based web services. Carequality’s governance framework can provide a “single on		Release of PHI can only occur if the record holder has trust not only that it can accurately identify the requester, but that the request itself, and the requester’s policies and practices around the information once it is released, are appropriate. Such trust is straightforward to establish for an individual connection between two partner organizations, by relying on new or existing contractual relationships bolstered by negotiation of security and other technical details. Such an approach is not scalable, however, as the healthcare industry discovered in the context of document exchange via SOAP-based web services. Carequality’s governance framework can provide a “single on

Tomjones: /* Scenarios */

2020-03-20T00:52:28Z

Scenarios

← Older revision		Revision as of 00:52, 20 March 2020
Line 28:		Line 28:

	Alternative Paths:		Alternative Paths:
	# The Primary Care Physician has placed the patient records in an EHR that regularly performs scans of all patients in the EHR for health conditions.		# The Primary Care Physician has placed the patient records in an EHR that regularly performs scans of all patients in the EHR for health conditions.
	# The patient is informed that health concerns are indicated and requests consent from the user to scan other health care records. (This step was missing from the original.)		# The patient is informed that health concerns are indicated and requests consent from the user to scan other health care records. (This step was missing from the original.)
	# When indications from the scan show possible areas of concern, the EHR reaches out to all providers of care to the patient using the Medical [[Record Locator Service]]		# When indications from the scan show possible areas of concern, the EHR reaches out to all providers of care to the patient using the Medical [[Record Locator Service]]

Tomjones: /* Scenarios */

2020-03-20T00:42:24Z

Scenarios

Tomjones: /* Scenarios */

2020-03-20T00:41:13Z

Scenarios

← Older revision		Revision as of 00:41, 20 March 2020
Line 25:		Line 25:
	#Patient is traveling, has a shoulder injury and seeks care at local rural care facility.		#Patient is traveling, has a shoulder injury and seeks care at local rural care facility.
	#Physician examines patient and wants to provide a pain medicine, patient cannot provide exact medicines or allergies.		#Physician examines patient and wants to provide a pain medicine, patient cannot provide exact medicines or allergies.
	#Phisician queries patient [[~~Medical~~ Record Locator Service]] and determines appropriate perscription.		#Phisician queries patient Medical [[Record Locator Service]] and determines appropriate perscription.

	Alternative Paths:		Alternative Paths:

← Older revision		Revision as of 00:42, 20 March 2020
Line 25:		Line 25:
	#Patient is traveling, has a shoulder injury and seeks care at local rural care facility.		#Patient is traveling, has a shoulder injury and seeks care at local rural care facility.
	#Physician examines patient and wants to provide a pain medicine, patient cannot provide exact medicines or allergies.		#Physician examines patient and wants to provide a pain medicine, patient cannot provide exact medicines or allergies.
	#Phisician queries patient Medical [[Record Locator Service]] and determines appropriate ~~perscription~~.		#Phisician queries patient Medical [[Record Locator Service]] and determines appropriate prescription.

	Alternative Paths:		Alternative Paths:
	# The Primary Care Physician has placed the patient records in an EHR that regularly performs scans of all patients in the EHR for health conditions.		# The Primary Care Physician has placed the patient records in an EHR that regularly performs scans of all patients in the EHR for health conditions.
	# The patient is informed that health concerns are indicated and requests consent from the user to scan other health care records. (This step was missing from the original.)		# The patient is informed that health concerns are indicated and requests consent from the user to scan other health care records. (This step was missing from the original.)
	# When indications from the scan show possible areas of concern, the EHR reaches out to all providers of care to the patient using the [[~~Medical Records~~ Locator Service]]		# When indications from the scan show possible areas of concern, the EHR reaches out to all providers of care to the patient using the Medical [[Record Locator Service]]
	# The patient is always informed when such a scan occurs and what the results were found. (This step was less informative in the original.)		# The patient is always informed when such a scan occurs and what the results were found. (This step was less informative in the original.)

	A different path using biometrics:		A different path using biometrics:

	#

	Failed Paths:		Failed Paths:
	#Patient not found in MRLS.		#Patient not found in MRLS.
	#Wrong record returned from MRLS		#Wrong record returned from MRLS
	#Data is not sufficient to allow doctor confidence in ~~perscribing~~.		#Data is not sufficient to allow doctor confidence in prescribing.

	==Results==		==Results==