Difference between revisions of "FHIR Resources for MMM"

From IHE Wiki
Jump to: navigation, search
Line 14: Line 14:
 
## Later: Delivery and not administration (supplyDelivery? Dispense?)
 
## Later: Delivery and not administration (supplyDelivery? Dispense?)
 
## Later: consume 2 items to administer only 1.
 
## Later: consume 2 items to administer only 1.
''' '''
+
 
 +
 
 
== Technical transport: How to get information from server to client ==
 
== Technical transport: How to get information from server to client ==
 
# Option 1: REST PULL
 
# Option 1: REST PULL
Line 20: Line 21:
 
## Search parameters in medicationRequest , search criteria same as above:
 
## Search parameters in medicationRequest , search criteria same as above:
 
## GET, https://www.hl7.org/fhir/medicationorder.html#search
 
## GET, https://www.hl7.org/fhir/medicationorder.html#search
#: ''' '''
+
##: 
 
#: Possible gap: '''how can we search for only this nurse?'''  
 
#: Possible gap: '''how can we search for only this nurse?'''  
 
#: It is not in the search criteria. So..
 
#: It is not in the search criteria. So..
Line 27: Line 28:
 
## Core: medicationrequest.Performer would be the best (not DispenseRequest.Performer).
 
## Core: medicationrequest.Performer would be the best (not DispenseRequest.Performer).
 
##:: IHE can add search parameters, but we will align with HL7 first.
 
##:: IHE can add search parameters, but we will align with HL7 first.
##:: ''' '''
+
#: 
##:: ''' '''
+
#: Gap: '''Query on date of planned administration – should be part of the search criteria.'''  
##: Gap: '''Query on date of planned administration – should be part of the search criteria.'''  
+
#: IHE extension or FHIR Core. Will propose and align.
##: IHE extension or FHIR Core. Will propose and align.
+
#: 
##: ''' '''
+
 
# Option 2: Subscription
 
# Option 2: Subscription
 
#: Search criteria are the same above
 
#: Search criteria are the same above
 
## Use http://build.fhir.org/subscription.html  
 
## Use http://build.fhir.org/subscription.html  
##: ''' '''
+
##: 
##: PUSH mechanism: Messaging or email.  
+
#: PUSH mechanism: Messaging or email.  
##: For messaging, we add messageheader.
+
#: For messaging, we add messageheader.
##: https://www.hl7.org/fhir/messageheader.html
+
#: https://www.hl7.org/fhir/messageheader.html
##: ''' '''
+
##: 
  
 
Question: how to handle these transport mechanisms? Jose will ask how ITI is handling it so far.
 
Question: how to handle these transport mechanisms? Jose will ask how ITI is handling it so far.

Revision as of 01:27, 25 November 2016

FHIR resources for MMA

Functional resources – transaction content

  1. Get medications for a patient: medicationRequest http://build.fhir.org/medicationrequest.html
    1. Must have a specific parameter (medicationRequest.intent or other) to select only the lists of administrations planned, not the prescriptions and encoded orders, etc.
    2. Search criteria:
      1. Date of administration
      2. Patient
      3. Nurse
  2. Send report of administration: medicationAdministration http://build.fhir.org/medicationadministration.html
    1. Must include non-administrations, as well as other information
    2. Do we include perfusion administration?
    3. Do we need to differentiate already-dispensed medication with to-be-dispensed medication? Suggestion: perhaps we later have to append a “dispense” resource.
    4. Later: Delivery and not administration (supplyDelivery? Dispense?)
    5. Later: consume 2 items to administer only 1.

   

Technical transport: How to get information from server to client

  1. Option 1: REST PULL
    1. Nurse app must retrieve the medication administrations planned for the treatment.
    2. Search parameters in medicationRequest , search criteria same as above:
    3. GET, https://www.hl7.org/fhir/medicationorder.html#search
       
    Possible gap: how can we search for only this nurse?
    It is not in the search criteria. So..
    1. Client filtering from getting all records from all nurses
    2. IHE search extension
    3. Core: medicationrequest.Performer would be the best (not DispenseRequest.Performer).
      IHE can add search parameters, but we will align with HL7 first.
     
    Gap: Query on date of planned administration – should be part of the search criteria.
    IHE extension or FHIR Core. Will propose and align.
     
  2. Option 2: Subscription
    Search criteria are the same above
    1. Use http://build.fhir.org/subscription.html
       
    PUSH mechanism: Messaging or email.
    For messaging, we add messageheader.
    https://www.hl7.org/fhir/messageheader.html
    1.  

Question: how to handle these transport mechanisms? Jose will ask how ITI is handling it so far.