event-service 0.2.0

Event Service - An event administration microservice that interoperates with the event-matcher crate
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40

//! Stub FHIR R5 handlers. Each handler returns 501 with an
//! [`OperationOutcome`]-shaped JSON body explaining that the
//! mapping isn't decided yet. See `mod.rs` for the rationale.

use axum::{http::StatusCode, response::IntoResponse, Json};
use serde_json::json;

fn not_implemented(reason: &str) -> impl IntoResponse {
    (
        StatusCode::NOT_IMPLEMENTED,
        Json(json!({
            "resourceType": "OperationOutcome",
            "issue": [{
                "severity": "error",
                "code": "not-supported",
                "diagnostics": reason,
            }],
        })),
    )
}

pub async fn get_event() -> impl IntoResponse {
    not_implemented("FHIR Event GET not implemented yet — see src/api/fhir/mod.rs")
}

pub async fn create_event() -> impl IntoResponse {
    not_implemented("FHIR Event POST not implemented yet — see src/api/fhir/mod.rs")
}

pub async fn update_event() -> impl IntoResponse {
    not_implemented("FHIR Event PUT not implemented yet — see src/api/fhir/mod.rs")
}

pub async fn delete_event() -> impl IntoResponse {
    not_implemented("FHIR Event DELETE not implemented yet — see src/api/fhir/mod.rs")
}

pub async fn search_events() -> impl IntoResponse {
    not_implemented("FHIR Event search not implemented yet — see src/api/fhir/mod.rs")
}