Profiles & Operations Index > Profiles & Operations
Profiles & Operations
Profiles
Resources are the building blocks of the FHIR standard. These resources convey the content of clinical records, identify patients or providers, or otherwise support information exchange between systems. These resources have been developed by numerous working groups at HL7, based on members' experience and subject expertise. The elements defined within FHIR resources are intended to capture and support those elements that 80% of implementers of a given resource are expected to support. Less frequently implemented elements are supported through FHIR's extensibility mechanisms. The list of all available resources in the R4 FHIR standard can be found here.
The base FHIR resources profiled/used in MI CDR are:
- DiagnosticReport (R4, hl7.org)
- ServiceRequest (R4, hl7.org)
- ImagingStudy (R4, hl7.org)
- DocumentReference (R4, hl7.org)
- Patient (R4, hl7.org)
- Practitioner (R4, hl7.org)
- PractitionerRole (R4, hl7.org)
- Organization (R4, hl7.org)
- Location (R4, hl7.org)
- Observation (R4, hl7.org)
- Encounter (R4, hl7.org)
- Bundle (R4, hl7.org)
- OperationOutcome (R4, hl7.org)
To see the MI CDR Profiles of FHIR Resources and extensions, please see the individual pages listed below:
Profiles
- DiagnosticReport
- ServiceRequest
- ImagingStudy
- DocumentReference
- Patient
- PractitionerRole
- Practitioner
- Organization
- Location
- Encounter
- Observation
Summary of Operations
Operations | Resource | HTTP Verb |
---|---|---|
Fetch DocumentReference | DocumentReference | GET, POST |
Search MI Report | DiagnosticReport | GET, POST |
Search MI Order | ServiceRequest | GET, POST |
Search Imaging Study | ImagingStudy | GET, POST |
Retrieve MI Report | DiagnosticReport | GET |
Retrieve MI Order | ServiceRequest | GET |
Retrieve Imaging Study | ImagingStudy | GET |
Submit MI Report | Bundle / DiagnosticReport | POST |
Submit MI Order | Bundle / ServiceRequest | POST |
Submit Imaging Study | Bundle / ImagingStudy | POST |
Extensions
- MI Category Type
- Supports slicing of ServiceRequest category into the procedure code, modality, specialty, body site, laterality or contrast
- MI Code Type
- Supports slicing of a .coding element into SNOMED CT, LOINC, DICOM, Provincial MI / OMID, or local code (while coding.system is normally suffient for slicing discriminator of known code systems, the local code systems are not known in advance)
- CopiedToPractitioner
- Identify practitioners who are to be copied on this order/report. It is important to identify all cc’d practitioners so that each practitioner is aware who is copied, and to ensure that the report is available to each practitioner
- PerformerFunction
- Distinguishes the type of involvement of the performer in the event. For example, 'author', 'verifier' or 'responsible party'
- HealthCardVersionCode
- An assigned sequence code, uniquely identifying a Health Card issued (or potentially issued) to a Registered Person