Release Notes

Release 2025.09.09

FHIR Features

• Apigee X Configurations for specific authorized users
• Infrustructure updates for improved On-Call support efficiency
• Updating and additional STMO configuration

Release 2025.09.04

DICOM Features

• Added DICOM data stores eligible for archival storage

FHIR Features

• Apigee X bug fixes
• Apigee X added application user exceptions
• Infrastructure updates and vulnerability management

Release 2025.08.19

FHIR Resources

Release 2025.07.22

FHIR Features

• Apigee X External LPR proxies are now available
• Apigee X bug fixes and IP allowlisting
• OnBase to LPR logging improvements

Release 2025.07.15

FHIR Features

• Dataflow and Pubsub alerts are configured for the Midia project
• API Product Descriptions are updated for Apigee X Internal
• Provide access to MCP team to perform deidentification of dicom store
• Apigee Prod Exceptions have been added for Guard and RLIMS applications

Release 2025.07.10

FHIR Features

• Appointment - Full backload completed

FHIR Resources

Release 2025.07.08

FHIR Features

• Apigee X Internal LPR proxies are now available
• Improved handling for CareEverywhere documents
• Fixes to FHIR Ingest Framework
• Improved performance of EAPIS STU3 MedicationStatement

Release 2025.06.23

FHIR Features

• DocumentReference-MDM - Full backload completed

FHIR Resources

Release 2025.05.13

FHIR Features

• DocumentReference-Care Everywhere - Maya-scoped release of PDF and expanded patient cohort

FHIR Resources

Release 2025.04.22

DICOM Features

• Removed legally restricted images from the LPR ImagingStore through April 3, 2025.

FHIR Features

• Removed ImagingStudy and Endpoint FHIR resources associated with legally restricted images from the LPR FHIR store through April 3, 2025.

Release 2025.03.27

FHIR Resources

Release 2025.03.25

FHIR Features

• Fixes legacy-only Patient merge issue
• Internal infrastructure updates

Release 2025.03.11

FHIR Features

• Adds log retention for LPR FHIR Apigee proxy auditing
• Improves support for internal vulnerability monitoring
• Add new entitlements and access for granular restrictive and sensitive data

Release 2025.03.05

FHIR Resources

Release 2025.03.04

FHIR Resources

Release 2025.02.25

FHIR Resources

Release 2025.01.28

FHIR Resources

FHIR Features

• Address malformed PDFs in pre-Epic on-demand rendering
• MIDIA data quality improvements
• OnBase operational improvements
• LPR data quality improvements

Release 2025.01.07

FHIR Resources

Release 2024.12.03

FHIR Resources

Release 2024.11.19

FHIR Resources

FHIR Features

• Data Quality configuration updates for MedicationRequest, DocumentReference-onbase
• Infrastructure updates and vulnerability management

Release 2024.11.12

FHIR Resources

Release 2024.09.24

FHIR Features

• HL7v2 notifications
  • A new topic for HL7v2 messages has been created
  • gcs-to-fhir now sends all HL7v2 messages to the newly created topic
• Legacy FHIR Store
  • All patients have been reloaded into Legacy FHIR Store after error replay process was fixed
• Daily FHIR Backup and Restore
  • Failures involving the daily FHIR backup and restore of ValueSet have been resolved

Release 2024.09.17

DICOM Features

• DICOM export
  • Option to bulk export has been removed. Sample code provided for alternative approach for obtaining large numbers of DICOM images.
  • Note: Usage restrictions still apply to use of DICOM images for direct patient care.

Release 2024.09.10

FHIR Features

• Improved data latency

Release 2024.09.03

FHIR Resources

FHIR Features

• Observation (Flowsheet) Fixes
  • Cleaned up duplicate Observation resources
• Observation (Lab) Fixes
  • Updated logic for 'note' field

Release 2024.08.30

FHIR Resources

FHIR Features

• Flag
  • Isolation Flag is now based on an encounter. Flag identifier.value migrates from {mrn}_{isolation type} to {mrn}_{csn}_{isolation type}.
  • Advance Directive and Isolation Status are processing nearly all ADT message event types. Previously a subset of message event types were used.
  • Fixed various bugs with deactivating and reactivating Flags

Release 2024.08.27

FHIR Resources

FHIR Features

• DiagnosticReport (Pathology) Fixes
  • Updated logic for 'status' field
• Observation (Pathology) Fixes
  • Updated logic for 'category' field

Release 2024.08.20

FHIR Resources

FHIR Features

• Appointment Fixes
  • Updated logic for 'start' field
• ValueSet Changes
  • Updated identifier due to change in data source

Release 2024.08.13

FHIR Resources

FHIR Features

• Coverage Fixes
  • Fixed error processing related person
• Patient Enhancements
  • Added originating MRN identifier to Patient

Release 2024.08.02

FHIR Features

• Patient: updated the Patient BigQuery flattened views to include columns that represent first name and middle name:
  • ‘given_name_1’
  • ‘given_name_2’

Release 2024.07.30

FHIR Features

• Appointment Fixes
  • Updated logic for 'serviceType' field

Release 2024.07.23

FHIR Resources

FHIR Features

• DiagnosticReport (Pathology)
  • Performed historical Load

Release 2024.07.16

FHIR Resources

FHIR Features

• Observation Fixes
  • Cleaned up duplicate Observation resources
• Observation (Microbiology)
  • Performed historical Load

Release 2024.07.09

FHIR Features

• Appointment Fixes
  • Fixed a bug where only the first Practitioner associated with the Appointment as added. Now additional participating Practitioners will be associated with Appointment resources with a participant type code of "http://terminology. hl7.org/CodeSystem/v3-ParticipationType|PART"

Release 2024.07.02

FHIR Resources

FHIR Features

• Coverage Enhancements
  • Bugfixes
    • Complete names provided for Coverage related person
• Observation (Microbiology) Enhancements
  • Improved resource identifier
    • identifier.value will be a 3 or 4 part - delimited string
    • orderId-orderCode-resultCode or orderId-orderCode-resultCode-subId

Release 2024.06.18

FHIR Features

• ValueSet Search – When querying the LPR FHIR Store via Apigee API, the code:in= parameter now supports searching ValueSets of any size.
  • This functionality overcomes a limitation from Google’s Healthcare API (queries with code:in= fail if the ValueSet exceeds roughly 600 items).
  • LPR consumers can now execute FHIR API queries with expected usage, more closely resembling the access patterns supported by EAPIS API
  • See FHIR Specs for additional details about standard code:in= functionality

Release 2024.05.30

FHIR Resources

FHIR Features

• Appointment Enhancements

  • Bugfixes
    • Start time not present for errored Appointments
    • Appointment type ConceptMap updates for accuracy
  • Expanded the Appointment.participants field to include more location details
    • Room Code (AIL-3.1)
    • Bed Code (AIL-3.2)
    • Care Department (AIL-3.4)
    • Surgical Room/Bed/Dept Code: (AIG-3.2)
  • Linked Location references for the following:
    • Surgical - Care Department (example care department 'ROMBOR')
    • Patient - Department (example department 'RST HPBS ROGO')
  • For Surgical Appointments, added two meta tags for the sending application (MSH-3.2) and receiving facility (MSH-6.1) for consumers needing specialized flag data
  • Enabled reference linking for Practitioners in Appointments. This enables a "by provider" search by using the standard _revinclude FHIR query pattern

• Concept Maps

  • Addition of a new concept maps to associate Locations with a primary regions (i.e. MCR, MCF, MCA, MCHS). This ConceptMap can be retrieved by using the following query: ConceptMap?url=http://terms.mayo.edu/mccfhir/conceptmap/epic.location.code.to.region.code

Release 2024.05.07

FHIR Resources

FHIR Features

• ImagingStudy Fixes and Enhancements

  The following address real-time processing only, historical patching is planned for future releases.

  • Bug fix for incorrect study and series dates (time zone handling)
  • Bug fix for rejected instances not being removed from studies
  • Bug fix for series.endpoint.type incorrect capitalization
  • Bug fix for series.instance.sopClass values being truncated
  • Bug fix for endpoint.type incorrect capitilization
  • Data change - subject.identifier and subject.name will no longer be populated (see subject.reference instead)
  • Improvements to error reporting and replay to improve data quality
  • Various performance enhancements

• Real-time data ingestion process fixes and enhancements

  • Patient:
    • Updated communication.language mapping for some previously undetermined languages
    • Updated telecom.use values to reflect the actual system and use values in the source HL7v2 messages
    • Updated us-core-race extension to represent race code and display values in the ombCategory and detailed subextentions

Release 2024.05.02

FHIR Resources

FHIR Features

• DiagnosticReport (Lab):
  • Change: LPR FHIR team will stop adding a header with patient details to the report text ('presentedForm.text' attribute) of DiagnosticReport (category = Laboratory) resources.
  • Reason for change: The patient details could change in a subsequent update from the EHR which renders the patient details in the DiagnosticReport text to be incorrect, leading to privacy and security issues.
  • Scope of change: These changes will be immediately applied to newly created or updated DiagnosticReport (Laboratory) resources. These details will also be removed from previous reports that had a chart correction event. All existing DiagnosticReport resources will remove these header details in a future release.
  • How to associate a report text to a patient after the change: Patient details associated with the DiagnosticReport's subject can be retrieved by querying the Patient resource directly.
  • As a reminder, DiagnosticReport (Radiology) reports initiated this change this past Tuesday, 4/29.
• Flag (all categories: Isolation Status, Infection Status, Advance Directive Code):
  • Change: For Flags, the LPR FHIR ingestion process will no longer filter out ADT messages that do not contain PV1-19 segments (encounter identifiers). Our FHIR mapping specifications have changed the encounter identifiers from "required" to "optional."
  • Reason for change: Encounter identifiers are not required for Flags, specifically. Regardless of the encounter details, these messages contain meaningful updates for the Flags and filtering out these messages result in incomplete, inaccurate Flag statuses.
  • Scope of change: These changes will be immediately applied to newly created or updated Flag resources. In a future release, the previously created Flags will be adjusted to comply with the latest logic for more accurate, complete representation of the clinical data.
• Coverage:
  • Change: The LPR FHIR ingestion process will now include a pre-process filter that skips Coverage messages that do not contain IN1-4 segments (Payor organization identifiers).
  • Reason for change: Payor organization identifiers (“payor” attributes) are required for Coverage resources, and messages missing this information cannot be used to create meaningful resources.
  • Scope of change: These changes are strictly internal to the LPR FHIR ingestion processing pipelines and have no impact to the data.

Release 2024.04.30

FHIR Resources

FHIR Features

• DiagnosticReport (Radiology): Newly created or updated DiagnosticReports with results in the presentedForm attribute will no longer include patient name, MRN, DOB, or practitioner name appended to the report text's header. Existing resources that were subject to chart correction events will also have these additional annotations removed from presentedForm. All existing resources will remove these annotations in a future release.
• Observation (Flowsheet): Enhanced pipeline performance for improved data freshness. No impact to the data.
• Condition: Operational updates for pre-processing filters. No impact to the data.

Release 2024.04.23

FHIR Resources

FHIR Features

• MedicationRequest: Remaining artifacts were removed from LPR
  • For more information please see Known Issues - MedicationRequest for a history of why this has been done.
• Observation (Flowsheet IO): For a subset of newly created or updated Observations that were previously missing details regarding I/O directionality (i.e. Intake vs Output), an enhancement has been applied to include the appropriate extension (extension.url="http://terms.mayo.edu/mccfhir/extensions/flowsheet_io_directionality").
• Flag: Updating common LPR libraries which allows inactive flags to be properly inactivated (i.e. the given Flag no longer applies to the patient and should not be considered by an application). A 60 replay of Flag messages will be done in conjunction with this resource release to ensure older data is accurate. This is expected to be completed within the release window.

Imaging Features

• All Family Medicine STMO created.

Release 2024.04.19

Legacy FHIR Store Resources

https://internal.mcc.api.mayo.edu/v2/mcc/fhir/r4/

header fhir_resource: legacy

Release 2024.04.16

FHIR Resources

FHIR Features

Real-time data ingestion process fixes and enhancements

• Patient: Fixed display text for Patient confidential codes.
• ServiceRequest: Fixes for requester field.

MedicationRequest

• As communicated previously, MedicationRequest resources are no longer available in the LPR FHIR API, PubSub event streaming, or BigQuery tables and views. BigQuery tables and views have been dropped, with the following exceptions, to be dropped at a future date:

  • ml-mps-adl-arestricted-p-a43b.phi_raw_fhir_v2_us_p.MedicationRequest
  • ml-mps-adl-arestricted-p-a43b.phi_raw_fhir_v2_us_p.MedicationRequestView

  For more information please see https://docs.mcc.mayo.edu/docs/data-analytics/longitudinal-patient-record/lpr-bugs/#medicationrequest

Release 2024.04.09

FHIR Resources

FHIR Features

• The following changes apply to DocumentReference
  • LPR FHIR /annotate https://internal.mcc.api.mayo.edu/v1/mcc/fhir/docstore/annotate endpoint is now generally available
  • LPR FHIR /metadata (FHIR Capability statement) endpoint is now generally available for both the v1 and v2 APIs: https://internal.mcc.api.mayo.edu/(v1|v2)/mcc/fhir/r4/metadata
• Observation (Lab/Micro): Real-time fix for “referenceRange. referenceRange.low” and “referenceRange.high” will only be populated if both a valid low and high value can be successfully parsed from “referenceRange.text”.
• The following changes apply to ServiceRequest:
  • A new field “reasonCode” will be added to newly created or updated ServiceRequest resources.
  • Logic for the “status” field has been updated to recognize more valid source values within the HL7v2 messages.

Release 2024.04.04

FHIR Features

Real-time data ingestion process fixes and enhancements

• ImagingStudy: Corrected issue where the ImagingStudy.series.started value was being populated from the series creation date rather than the acquisition time. The value for started will now be the acquisition time. Records prior to 2024-04-05 will be updated in a future release.

Release 2024.03.19

FHIR Resources

FHIR Features

Real-time data ingestion process fixes and enhancements

• Observation-Lab: code update to fix multiple Observations with same identifier
• ConceptMap: updates to include the most recent inactive mappings in addition to the active mappings
  • For example if the source data for a concept map has the following mappings:
    • A -> 1
    • B -> 2
    • C -> 3
  • Where A,B are active and C is inactive.
  • The map will now appear as show above
  • whereas before the change the map would look like:
    • A -> 1
    • B -> 2
  • All ConceptMaps with an identifier.system of http://terms.mayo.edu/systemid/terms/termsconceptmap/id are affected by this change

Release 2024.03.05

FHIR Resources

FHIR Features

• Observation (Lab): Realtime fix for referenceRanges field. Only affects newly created and updated resources.
• Procedure: Realtime fix for code field. Only affects newly created and updated resources.

Release 2024.02.27

FHIR Resources

FHIR Features

Real-time data ingestion process: Upgraded for faster performance and higher throughput

• Observation-Lab: add category information for microbiology message types
  • Another category code will be added
    • http://terms.mayo.edu/codesystem/EPIC_ORDER_TYPE_CODE|Microbiology
  • In addition to the lab categoy
    • http://terminology.hl7.org/CodeSystem/observation-category|laboratory
  • So a microbiology Observation resource will have two categories
• Procedure: realtime fix for missing CPT codes

Release 2024.02.20

FHIR Resources

FHIR Features

• Condition: Bug fix to ensure references to encounters are accounted for (when applicable). “note.text” changed to be one item concatenated by a new-line rather than separate items in the array.
• Observation (vital signs): Changed “code.coding.display” and “code.coding.text” to be the proper display value of “Vital Signs” instead of “vital-signs”
• Practitioner: Removing the “name.prefix” from newly created or updated resources due to data issues with the source data provided to LPR.
• Procedure: Changed processing logic to not reject data with empty Surgical Panels

Release 2024.01.30

FHIR Resources

FHIR Features

• Apigee Access: Updated the LPR documentation for requesting Apigee access:
  • “MCC Longitudinal Patient Record” for Dev/Test access in the Apigee NonProd Developer Portal.
  • “MCC Longitudinal Patient Record – Staging” for Stage access in the Apigee Production Developer Portal.
  • “MCC Longitudinal Patient Record” for Production access in the Apigee Production Developer Portal.
• Procedure: Updated the underlying logic for the identifier attributes to follow best practices when populating the two supported identifier types within the Procedure BigQuery view in the ml-mps-adl-intfhr-phi-p-3b6e.phi_flat_fhir_us_p dataset. No columns were deleted or added.
• Encounter: Improved the logic that updates resources with limited data attributes once an appropriate subsequent resource is identified with more complete data attributes Real-time data ingestion process: Upgraded for faster performance and higher throughput
• BigQuery updates: Improved operational pipeline that syncs the LPR FHIR Store with downstream streaming BigQuery tables and views
• Streamlined ingestion to increase data freshness

Release 2024.01.18

FHIR Resources

FHIR Features

• Appointment (Non-Surgical, Patient): Real-time data associated with non-surgical patient Appointments will now be represented in the LPR FHIR Store. In addition, appointments created or updated within the past 14 days will also be loaded into the FHIR Store. Older appointment data will be added to the LPR FHIR Store in separate future releases.
• Observation (Lab): updated a subset of ‘code.coding[].code’ values for additional mapping of internal Epic codes to standardized LOINC codes
• Procedure: updated ‘encounter.reference’ values to ensure relationships between Procedure and Encounter resources are properly maintained and updated
• DocumentReference: updated the DocumentReference BigQuery flattened views (‘DocumentReference’ and ‘DocumentReferenceView’ in the ‘ml-mps-adl-intfhr-phi-p-3b6e.phi_flat_fhir_us_p dataset’) to include columns that represent contentTypes and URLs for both RTF and PDF attachments:
  • ‘content_rtf_attachment_contentType’
  • ‘content_rtf_attachment_url’
  • ‘content_pdf_attachment_contentType’
  • ‘content_pdf_attachment_url’

Release 2024.01.09

FHIR Features

• Updates were made to the existing resource_code field within BigQuery Flattened Views in the ml-mps-adl-intfhr-phi-p-3b6e.phi_flat_fhir_us_p dataset so that the values are consistently populated with operational indicators (“CREATE”, “UPDATE”, or “DELETE”).
• Internal updates were made to enhance the Apigee proxy; these changes had no impact to API consumers.

Release 2024.01.02

FHIR Resources

FHIR Features

• Observation (Flowsheet): added the sub-attribute dataAbsentReason.text when the resource’s status element is equal to entered-in-error for newly created resources

Release 2023.12.21

FHIR Resources

FHIR Features

• Patient removed ‘generalPractitioner.display’ (Practitioner’s name) attribute for newly created resources
• Encounter added another value to ‘type[]’ to represent an encounter’s level of care for newly created resources
• DocumentReference added another value to ‘type.coding.code[]’ to include a LOINC code when there is an appropriate mapping from the internal Epic document type code for newly created resources
• Observation (LDA) replaced the value of ‘identifier[].system’ to be consistent with the other Observation ‘identifier[].system’ values for newly created resources
• Contact Move Additional operational updates were made to better support the LPR FHIR Store's handling of contact moves; these changes had no structural or data impacts to resources

Release 2023.12.05

FHIR Resources

FHIR Features

• FHIR Full Event Streaming service has been upgraded to improve performance and reliability.
  • metadata attributes have changed as follows (see the FHIR Full Event streaming page for additional details on these attributes):
    • fhirID has been removed in favor of the id attribute within the FHIR resource message payload.
    • lastUpdatedTime has been added
    • storeName has been added
    • versionId has been added

Release 2023.11.28

FHIR Resources

FHIR Features

The following changes apply to DiagnosticReport (Lab)

• Fixed a code mapping

The following changes apply to DiagnosticReport (Radiology)

• Fixed a status mapping

The following changes apply to DocumentReference

• Fixed a content mapping
• Support large documents (greater than 8MB)
• Provide content from Epic Clinical Notes in both RTF and PDF formats
• Represent RTF and PDF content as external files instead of inline

Release 2023.11.21

FHIR Resources

FHIR Features

• DiagnosticReport (Radiology) fixed a status mapping
• Practitioner fixed a telecom communication mapping
• Encounter removed practitioner reference display (person's name) from participant.individual.reference.display
• Observation-LDA removed a trailing space in display text

Release 2023.11.14

FHIR Resources

FHIR Features

• Updated handling of concept mappings for Patient contact relationships (see field contact[].relationship[].coding[].system)

Release 2023.11.07

FHIR Resources

FHIR Features

The following changes apply to the Condition resource. New data only is affected (Historic data will be backloaded at a later date.)

• note[].text is an array with one element containing the note. Previously each note line was represented with an array element.

Release 2023.10.31

FHIR Resources

FHIR Features

The following changes apply to the DiagnosticReport (Radiology) resource. New data only is affected (Historic data will be backloaded at a later date.)

• Add basedOn field
• Fix service request identifier system
• Remove practitioner display
• Moved modality from code to category

The following changes apply to the DiagnosticReport (Pathology) and DiagnosticReport (Lab) resource. New data only is affected (Historic data will be backloaded at a later date.)

• Add presentedForm field

Release 2023.10.17

FHIR Resources

FHIR Features

• Add "location_status" column to the EncounterLocation flattened materialized view
• Add NDC codes to Medication resource

Release 2023.10.03

FHIR Features

The following changes apply to the Encounter resource:

• Update "location" field to support planned and complete locations

Release 2023.08.29

FHIR Resources

• Added photo/video consent pipeline to auto-replay configuration

FHIR Features

• None

Release 2023.08.17

FHIR Resources

FHIR Features

• BigQuery flattened materialized views of FHIR store migrated to Analytics V2 schema

Release 2023.08.15

FHIR Resources

• None

FHIR Features

• Changed HL7 Phillips Device Data Storage Bucket retention policy

Release 2023.08.01

FHIR Resources

FHIR Features

The following changes apply to the Observation-Lab resource:

• Add "specimen.display" field
• Add identifier resource-type system and coding
• Add support for external labs
• Change "Unknown" ORU lab code, display, and system to null
• Change backup fields for display and system

Release 2023.07.18

FHIR Features

• Changes to avoid duplicate AllergyIntolerance records and improve handling of deleted records
• IAM updates to provide necessary access for non-LPR teams

Release 2023.07.11

FHIR Features

Notification of chart correction events (patient merge, patient unmerge, encounter contact move) now available.

Release 2023.05.26

Content

This is a release of Location, Medication, MedicationRequest, Organization, Practitioner, PractitionerIdentifier, PractitionerRole, Procedure, ValueSet BigQuery optimized tables and ServiceRequest views

Features

Known Limitations / Future Enhancements

Release 2023.05.15

Content

This is a release of EncounterLocation, EncounterReasonCode, Endpoint, ImagingStudy, ImagingStudySeries, ImagingStudySeriesInstance BigQuery optimized tables.

Features

Known Limitations / Future Enhancements

Release 2023.04.21

FHIR Resources

FHIR Features

None

Known Bugs / Future Enhancements

Missing final message

There are a class of orders in Radiology that are procedural where there is no result and the order is resulted in EPIC but there is no updated HL7 message where ORC-2.1=final.

Only child order in HL7

There is a heirerarchical relationship with orders where only the child order is available in HL7, but all of the parent/child orders are stored in clarity, which makes it difficult to measure total mismatched orders in any category.

Release 2023.04.03

Content

This is a release of AllergyIntolerance, AllergyIntoleranceNote, AllergyIntoleranceReaction, CodeSystem, ConceptMap, Coverage BigQuery optimized tables.

Features

Known Limitations / Future Enhancements

Release 2023.03.27

Content

This is a release of Diagnostic Report BigQuery optimized tables.

Features

Known Limitations / Future Enhancements

Release 2023.03.10

Content

This is a release of Big Query optimized tables.

Features

Known Limitations / Future Enhancements

Release 2023.02.07

Content

This is a release of Big Query views for PractitionerIdentifier Resource.

Features

Known Limitations / Future Enhancements

Release 2023.01.24

Content

This is a release of Big Query views for PractitionerRole Resource.

Features

Known Limitations / Future Enhancements

Release 2022.12.20

Content

This is a release of Big Query views for AllergyIntoleranceNote, AllergyIntoleranceReaction, EncounterLocation and EncounterReasonCode.

Features

Known Limitations / Future Enhancements

Release 2022.10.28

Content

This is a release of Big Query views for ImagingStudy.

Features

Known Limitations / Future Enhancements

Release 2022.10.04

Content

This is a release of Big Query views based on LPR FHIR data.

Features

Known Limitations / Future Enhancements

Release 2022.09.19

Content

This is a release of Big Query views based on LPR FHIR data.

Features

Known Limitations / Future Enhancements

Release 2022.09.01

Content

This is a release of an update to the Observation view.

Features

Known Limitations / Future Enhancements

Release 2022.08.23

Content

This is a release of Big Query views based on LPR FHIR data.

Features

Known Limitations / Future Enhancements

Release 2022.07.12

FHIR Resources

FHIR Features

None

Known Bugs / Future Enhancements

Release 2022.07.12

Private Preview

This is a private preview release for datasets and views within AIDE. The views and datasets will be available to users who have been provisioned with the right entitlements. Learn more about how to get access.

Features

Known Limitations / Future Enhancements

Release 2022.06.28

FHIR Resources

FHIR Features

None

Known Bugs / Future Enhancements

Medication codes are different for ORM and RDE. It's being worked on to map both of them to a common code like RxNorm

Map the medications to the Medication resource

Release 2022.06.23

FHIR Resources

FHIR Features

None

Known Bugs / Future Enhancements

Release 2022.06.21

FHIR Resources

FHIR Features

None

Known Bugs / Future Enhancements

Release 2022.06.14

FHIR Resources

FHIR Features

None

Known Bugs / Future Enhancements (Check Status of Bugs Here)

Large documents (greater than 8MB) are not supported

Release 2022.06.02

FHIR Resources

FHIR Features

None

Known Bugs / Future Enhancements

Large messages are being rejected in FHIR Store

Release 2022.05.17

FHIR Resources

FHIR Features

None

Known Bugs / Future Enhancements

The sensitive diagnosis flag, that identifies problems as sensitive to be suppressed from the patient portal, is being slated for future development

Release 2022.05.26

FHIR Features

• FHIR Streaming Documentation

Release 2022.03.29

FHIR Resources

FHIR Features

None

Known Bugs / Future Enhancements

Large messages are being rejected in FHIR Store for Concept Maps and Code Systems

Release 2022.03.15

FHIR Resources

FHIR Features

None

Known Bugs / Future Enhancements

Release 2022.03.09

FHIR Resources

FHIR Features

None

Known Bugs / Future Enhancements

DiagnosticReport (Lab), Observation (Lab)

Some DiagnosticReports and Observations not created for inbound real-time messages (less than 0.5%) due to the following bugs to be addressed in future releases:

1. Bug 1365180 ORU Lab: Lab results not supported for HL7 with multiple OBX with same OBX-3.1 value (RESOLVED)
2. Bug 1374839 ORU Lab: Result Cancellations not currently supported (RESOLVED)

Release 2022.02.22

FHIR Resources

FHIR Features

Known Bugs / Future Enhancements

DiagnosticReport (Radiology)

1. DiagnosticReport (Radiology) content is based on the existing EAPIS STU3. However, it does not include practitioner pager numbers, because those changes do not trigger resending of the reports.
2. DiagnosticReport/Observation (Labs) - There is a bug in the real-time processing of DiagnosticReport and Observation for Labs. A fix and live feed of Labs will be available in the next release. Right now there is Lab data from Epic Epoch through 2022-02-22.

Encounter (Break the Glass)

1. Story 1339326 Sensitive encounter types are not currently receiving the meta.security tag during real-time processing.
2. Story 1339503 AODA Department encounters are not currently receiving the meta.security tag during real-time processing.
3. Bug 1335822 PR1 segment may be missing in some messages, causing the real-time to miss tagging based on AODA Visit Type criteria.

Special Note - Encounter security meta tag

For each Encounter FHIR resource that has been deemed sensitive (subject to the known issues described above), an element has been added to the meta.security attribute with the following values:

• security.system: "http://terminology.hl7.org/CodeSystem/v3-Confidentiality"
• security.code: "R"
• security.display: "restricted"

For example, an encounter that has been deemed as sensitive would have a structure similar to the following:

{
  "resourceType": "Encounter",
  "id": "...",

  "meta": {
    "security": [
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-Confidentiality",
        "code": "R",
        "display": "restricted"
      }
    ]
  }
}

Release 2021.11.16

FHIR Resources

FHIR Features

None

Known Bugs / Future Enhancements

General

• Bug 1139614 - In rare occurrences (< 1%), internal errors may lead to outdated or missing data (RESOLVED)
• Bug 1141214 Beam SDK Version needs to be updated to 2.34 (RESOLVED)

Medication

• Bug 1137503 - Redundant display in text.div. Example: Medication 6040, display is copper copper (RESOLVED)

• Bug 1142669 - Two missing Medications due to parsing bug (RESOLVED)

  • Med IDs 40840042 and 40801900242

PractitionerRole

• Bug 1141018 - Incorrect System URIs (RESOLVED)
• Bug 1142695 - Not US Core Compliant - Missing Standard ConceptMaps for Speciality and Code (REMOVED)

Release 1.0.0 - Initial Release

Please note this is the initial release of the Longitudinal Patient Record. The Longitudinal Patient Record is available for data consumers who have obtained authorization from MCC Executive Leadership. Read the release notes below for special notes on the data and functionality of this initial release.

This means:

• 24/7 support is available for break/fix of severe production issues.
  • SLA: KB0119373
• 8-5 CT weekday support is available for all other questions and issues.
• Data structure (fields, case, etc) and history may change. Notice to consumers will be given.
• Reporting Errors in operation (API calls) or Data are encouraged! However, bug resolution may be triaged without definite resolution dates.
• Use of data should be specific to a business use case. GDPR and VIP data should be protected and used appropriately.

FHIR Resources

FHIR Features

See the section below for how to request access.

Special Note - Patient FYI meta tag

There is a lower percentage of patients that have more than one patient confidential flag set in Epic and are being triggered from real time EPIC ADT HL7 outbound with both confidential flag display values in NTE segments. In those scenarios, the patient FHIR resource meta.security tag display and code is being set to one of the values from NTEs and the system is being always set to "http://terms.mayo.edu/mccfhir/systemid/epic/patient_confidential"

For example: There are the cases of 2 NTEs coming out of single EPIC ADT message for a patient that has values like

NTE|1||Confidential-Medium|...
NTE|2||Confidential PSN|...

Based on NTE confidential messages sequence order, Patient FHIR resource meta.security[x].system is being set as either:

[{"system":"http://terms.mayo.edu/mccfhir/systemid/epic/patient_confidential","code":Confidential PSN","display":"Confidential PSN"}]

OR

[{"system":"http://terms.mayo.edu/mccfhir/systemid/epic/patient_confidential","code":Confidential PSN","display":"Confidential-Medium"}]

However the functionality of setting Patient confidential meta security tag is not getting affected and patient confidential BTG process should always check if the patient has meta.security[x] has the system = "http://terms.mayo.edu/mccfhir/systemid/epic/patient_confidential"

Known Bugs / Future Enhancements

AllergyIntolerance

1. Bug 1504020 & Bug 1231121 AllergyIntolerance resource unsuitable for patient care related activities which rely upon RxNorm or Snomed coding to be present. Current version of resource does not support these mappings, but future versions will. (Resolved in Release 2022.07.12)

Patient

1. Story 1097238 Patient.contact[] may contain objects without a name or use. In these cases the contact is typically an employer or self. (RESOLVED)